4 ms·
That is actually the case today! But it is an opt-in feature, which is not supported in older browsers. In modern frontend development we are heavily optimizi
by dgb23 6y ago
That is actually the case today!
But it is an opt-in feature, which is not supported in older browsers.
In modern frontend development we are heavily optimizing images now. Lazy loading is one thing, the other is optimizing sizes (based on viewports) and optimizing formats (if possible).
This often means you generate (and cache) images on the fly or at build-time, including resizing, cropping, compressing and so on.
- Bnshsysjab 6y agoIs putting all assets into a single png/svg to reduce total requests a dead practice now?
- tbarbugli 6y agoI guess http/2 support on CDN made this a useless (and tedious) optimization
- Polylactic_acid 6y agoThere was also the issue on an ancient version of IE that it could only load a few requests at the same time.
- reaperducer 6y agoIs putting all assets into a single png/svg to reduce total requests a dead practice now? As someone who browses the source of a lot of commercial web sites, I can say it's still dead common. There's been a lot of static about new technologies coming that will make this unnecessary, but that don't help anyone today.
- gcpwnd 6y agoShould be done only if you have to load lots of small images. If you want to render above the fold fast reduceassets there and load them directly.
- j-krieger 6y agoIt is not supported by Safari, too.
- hnick 6y agoIs progressive image loading still a common thing? I'd guess for a lot of connections it actually hurts more than it helps - until you get to that fat image-heavy site.