2 ms·
I have been thinking about images on the web. And I still unsure, undecided on what sort of file size should we really be aiming at. >1500x1750 and weighing in
by ksec 5y ago
I have been thinking about images on the web. And I still unsure, undecided on what sort of file size should we really be aiming at.
>1500x1750 and weighing in at 3MB! The webp version of the same size is ~79KB.
79KB is a very low 0.24 BPP ( bit per pixel ). for 1 BPP it would be 328KB.
AVIF is optimised for BPP below 1, while JPEP XL is optimised for BPP above 1. On a MacBook Pro, the first fold of the browser has 3456 x ~2200, an image filling up that screen with BPP 1 would equate to 950KB.
In a perfect would you would want JPEG XL to further optimise BPP below 1.0 and do progressive loading on all image.
We have also bumped out monitor resolution by at least 4x to Retina Standards.
Despite our broadband getting so much faster, file size reduction is still the most effective way to get a decent browser experience. At the same time we want higher quality images and beautiful layout ( CSS ) etc.
Balancing all of these is hard. I keep thinking if some of these are over optimising, when we can expect consumer internet speed to increase in the next 10 years.
- idoubtit 5y ago> At the same time we want higher quality images YMMV but 99% the images I see on the web, I don't care about their quality. A large part of them are annoying, and most of the others could be low-resolution and low-quality, I would not even notice it, except for the faster page load. Once in a while, a photo is artistic or interesting enough to gain from a high quality, but most web sites I visit have far too many heavy images.