![]() Today they are optimized using imageoptim at a lossless compression. In terms of resolution, these are the largest PNGs used on my sites. I took 260 sample PNG images at their largest size of 1024×1024 pixels. Will I be switching to WEBP for my icon gallery sites? I don’t have a definitive answer yet. ![]() ![]() It’s pretty damn good though, especially with images composed of modern “flat” aesthetics-solid or gradient fill colors, silhouette shapes, etc. Like most technology, WEBP is not a cure all.I found it intriguing to see lossless WEBP images come in at a collectively larger file size than lossless PNGs (which I use today)!.Tldr I picked a random sample of sixty iOS icons and converted them to WEBP to see where the biggest changes (both visually but also in file size) would show up between PNG and WEBP formats. Given the above, I devised a few ways to test whether WEBP would be sufficient to my needs. That is why I serve lossless PNGs today.īut maybe WEBP could meet the same standard of quality I have from today’s PNGs and still save me some bytes? That’s my hope. People come to these sites to admire the design of the icons and it would be difficult to admire and appreciate the quality of something that’s been altered and degraded from its original form. So I’ve been thinking: if I could cut image sizes, say, in half, that would cut my bandwidth usage in half! However, given that the primary focus of these sites is the icons themselves, I need to continue providing high quality icons. The past few months, according to Netlify, I’ve been burning through 150GB or more of traffic per month for these sites-the majority of that being serving images. It does a pretty damn good job of doing lossless minification for the original icon designs. Today I’m serving PNGs which I optimize via the ImageOptim API. Now that WEBP is supported across popular modern browsers-looking at you Safari for being late to the party-I’ve been considering serving images in WEBP format across my icon gallery sites.
0 Comments
Leave a Reply. |