Note from 13 December 2022
⚠️ Be carefull if you use SVGO or SVGOMG to optimize #SVG images using <symbol>s.
There's a bug that might remove them when it shouldn't:
https://github.com/svg/svgo/issues/1726
Related contents with similar topics
-
JPEG XL isn't useless; it is genuinely compelling technology for use cases beyond the Web. I'm just not personally convinced we need it in browsers…
-
The present and potential future of progressive image rendering
So if the browser manages to download 6 kB then stalls, then AVIF can produce a better result. But since the AVIF rendering is only two-pass, if the…
-
kliksphilip
JPEG VS AVIF - The Battle of Compression
In this super thorough study I test one single HD image and come to vast sweeping conclusions about JPEG XL and AVIF. But that's still one image comparison…
-
Should I please Lighthouse with modern image formats, or my visitors with progressive rendering of large images in my photography site? 🤔
Of course, this would be much easier with genaralized JPEG XL support, both modern and allowing progressive… 🤷♂️
-
Most mentions of the magical CSS
object-fit: cover;in development tutorials should be accompanied by a warning: in most situations, it means the browser will download an image that is larger than required (at least in one direction), and optimization on the server side could be a better option.
Gianni Rosato
Jake Archibald