Some of you may already be aware that if images are not inlined, they can be cached individually so future page requests do not need to refetch them. But if we consider:
Each image was originally about 1.5kb on the network they were not compressed SVGs, with about 350 bytes of headers on top, for a total of about 5.5kb transferred. Overall, we reduced the amount of content on the network.
This also means that it takes more than 20 page views to benefit from caching.
Summary of key points
Takeaway: Consider where there are opportunities to use portugal mobile database SVG instead of PNG.
Takeaway: Make sure you use my free tool when optimizing your SVG images.
Takeaway: Inlining small images makes sense and can give huge performance gains.
Note: You can also inline PNGs - see this guide .
Stop, JavaScript! HTML can handle this...
Today, due to the popularity of JavaScript libraries that provide ready-made solutions, I find that JavaScript is being used for functions that can be achieved without it. More JS libraries means more files to download, perhaps more files to fetch from the server, and then the execution time and cost of JavaScript will also increase.
I sympathize with you getting to this point. Developers often get bad briefsspecs that don't specify anything about performance, only functionality. They usually don't have time, so they just cram everything in.
However, a lot of progress has been made in terms of what can be achieved with HTML andor CSS. Let’s look at some examples.