4 ms·
With todays phones and network connections, downloading and rendering images actually constitutes only a small proportion of the total loading time. Of that sm
by londons_explore 5y ago
With todays phones and network connections, downloading and rendering images actually constitutes only a small proportion of the total loading time.
Of that small proportion, the cpu time of rendering the images, relayout of the page for changed image dimensions, and re-rendering the image and all overlapping text and layers each time a bit more of it partially loads, is more substantial than the network delay of loading the data.
The TL;DR: is that optimising images isn't the place to start to make most websites load faster, especially on mobile.
Obviously if CPU speeds increase faster than network speeds, image size may matter again in the future. But today the size is mostly irrelevant as long as you aren't serving your photographs as multi-megapixel images or gifs.
- imaginariet 5y agoFor something like Instagram, where most images (and videos) are viewed only once, size is very important. And way more images are viewed on Instagram than on mobile websites.
- nyx-aiur 5y agoWhat an idiotic attitude from a guy who thinks the world is connected to 5G and everyone has an M1 Macbook.
- cryptonym 5y agoA new format might come with improved decoding performance/memory usage with hardware support or improved algorithm. More than layout, the real issue around web performance usually is JavaScript / Third Parties. Browser is only a tiny part of potential benefits. What if your business relies heavily on images and can save 30% of your bills on image storage and bandwidth? On your camera, maybe you will take more pictures without switching SD-Card...