Maybe this should come with a warning. The purpose of WebP is to quickly serve images to the user without grabbing the entire image data. Without WebP all images will be fully loaded, in the right conditions a page could load real slow.
I love webp, but your explanation is a bit confused. Webp is typically lossy, just as jpeg — only, it’s more efficiently compressed, meaning smaller size for the same image quality. So there’s no ‘entire image data’, there are only different approximations of the original image and different compressed files. Full-blown lossless images in PNG or other formats take several times more data.
Disabling webp in favor of jpeg would use like 20-40% more data, in comparison. Which still sucks, but not as much.
I wasn’t going to get into the whole lossyness of the formats and just simplified to full image instead of compressed formatted.
That is interesting that it is only saving 20%-40%. I was under the impression that the page only rendered the image size necessary to fit the layout and not the full resolution image. Forcing it to less lossy or lossless would mean that the larger image would always be available to be served to be rendered without any web request.
Feel free to use floppy disks. Btw if you are online, you use WebP and PNG all the time 🤣
Sir, don’t you dare encroach on those Lynx and W3M users. They don’t need no stinking images!
Lynx is the best browser.
I prefer offpunk.
Not if they use wget to only download the HTML!
AVIF started heavily creeping in, too.
I’ve yet to see any AVIF in the wild. I think support for it is not quite there yet, everybody is still relying on WEBP.
I’ve seen a lot of avifs masquerading as jpegs lol (I know because KDE Dolphin for some reason isn’t showing a preview for those until I rename them)
If you are using Firefox:
Maybe this should come with a warning. The purpose of WebP is to quickly serve images to the user without grabbing the entire image data. Without WebP all images will be fully loaded, in the right conditions a page could load real slow.
I love webp, but your explanation is a bit confused. Webp is typically lossy, just as jpeg — only, it’s more efficiently compressed, meaning smaller size for the same image quality. So there’s no ‘entire image data’, there are only different approximations of the original image and different compressed files. Full-blown lossless images in PNG or other formats take several times more data.
Disabling webp in favor of jpeg would use like 20-40% more data, in comparison. Which still sucks, but not as much.
I wasn’t going to get into the whole lossyness of the formats and just simplified to full image instead of compressed formatted. That is interesting that it is only saving 20%-40%. I was under the impression that the page only rendered the image size necessary to fit the layout and not the full resolution image. Forcing it to less lossy or lossless would mean that the larger image would always be available to be served to be rendered without any web request.
No, I have WebP blocked in my about:config. And I use Pale Moon, which actually blocks the things unlike modern FF. And I don’t load PNG either.
lmao
Do you also hit yourself in the nuts every morning to show the world how tough you are?
I find this interesting there an advantage to the older formats or is this just for compatibility with custom photo editing tools?
Compatibility is an advantage.