Convert images to webp even if they are not smaller than the original

Yes, there is an option for that, but it should only be used if you have off-loaded storage where you won’t be able to implement a check to see that the .webp file exists before delivering it.
It’s called “Force WebP” and is right on the WebP settings.

Again, this option should never be used unless you have off-loaded your media, otherwise you’re making your site slower just to use WebP, which would be foolish at best.

Hi, thank you for the answer.

I’m trying to do this because lighthouse is giving me a slow score because I’m not using webp for some images, which are those images not converted.

And also seeing that the option “Force Web” seems to use javascript and most of the pages are done in AMP so this javascript will not have effect. I could check the option just to create the webp images and after that uncheck it ??

I’m going to try with a couple of images and I’ll let you know.

Thank you!!

Please don’t do anything just because lighthouse says so, do it because it makes your site faster and your customers happier ??

Ok, thank you so much for the advise, I’ll really consider it ??

And it will work with .htaccess also, but that’s not the intended use. But I do have an idea that might get you WebP images that are even smaller, but I need to double-check something on that. Stay tuned!

Ok, great. I’ll be connected and checking the post.

Thank you ??

And also, I’m using OpenLiteSpeed, just in case a weird .htaccess rule does not work, which I don’t think so, most of them are working fine.

To make a webp image a bit smaller or even same size would be great so it is work for any image. Actually, as far as I’m concerned webp should be always smaller than jpg keeping the same quality.

Yes, one would think WebP always *ought* to be smaller than JPG, but sometimes it isn’t. Just the nature of lossy-style compression algorithms.

At any rate, I checked on my idea, and what you can do is lower the JPG quality on the advanced settings, which will then also be applied to WebP conversion. Default is 82, so I would try with 80, then 75 or 70 and see what that does for you.

Hi,

I have tried to low down the quality value as you have said, I have even tried with 20 but the WebP image does not get converted and also the size of the jpg is still the same one.

The only way to convert the WebP image is to check the option “Force WebP” and once is create I have unchecked it. The result is a 66K jpg image and 106k WebP image, so it does not make any sense to have a WebP image bigger than a jpg. I have also tried to convert the same jpg in other online platforms and I get even worse conversion result.

The only thing that comes to my mind is to upload an smaller jpg image. This is the site where I’m doing all mentioned before by the way https://www.tudestinopirineos.com/ and here it is where we can see the lighthouse warnings https://www.tudestinopirineos.com/actividades/aventura/

Thank you so much for your help, always learning about how to optimize websites.

Have a good weekend.

That’s strange, when I run lighthouse (in the Chrome dev tools), I get a pass for “nextgen formats” on https://www.tudestinopirineos.com/actividades/aventura/
I checked both desktop and mobile, are you perhaps using a cloud proxy like Sucuri, Cloudflare, or Stackpath?

Or maybe you haven’t cleared out the “too large” WebP images yet?

That could be the cache of the LiteSpeed server. I have been doing some testing so anything can happen when caches are around ??

Lighthouse did not tell me that I had to use nextgen formats for images, it was me that I believe having WebP format I would avoid some warnings.

And, yes, I have cleared out the large WebP images

Ah, okay, that makes more sense. You did have some image-related warnings if I remember right, but nothing on nextgen formats (which is WebP), and I think it was only on the mobile version of the test (but I could be wrong).

Thank you so much nosilver4u,

you are great, just let me know if any day you need some help