• Seems like it optimized all the images well, especially heavy PNGs, one of them for example went from 1000KB (almost 1MB) to 68KB. However, it stayed as a PNG, and it didn’t change to WEBP.

    Browsers and Google will not still think it’s a PNG file. Ideally it should convert & replace the path in posts and pages to the new WEBP extension.

    • This topic was modified 3 years, 8 months ago by uworlddav. Reason: changed rating to 5 after getting an explanation
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Mateusz Gbiorczyk

    (@mateuszgbiorczyk)

    Hello @uworlddav,

    Thanks for your opinion.

    Let me explain this to you. If the URLs were changed it would be a big problem for the cache. This means that a page once saved in the cache would always load WebP files – instead of deciding whether to load WebP for a given browser or not.

    Browsers do not consider the file extension in the URL. Many image URLs do not even have a .jpg or .png ending. When an image is loaded, the Content-Type header is also sent. It is this header that is important to the browser. By default, for .jpg files it will be “Content-Type: image/jpeg”. By redirecting files to the WebP format, my plugin changes this type to a new one – “Content-Type: image/webp”.

    Here you can compare how it looks in Dev Tools before using the plugin and after converting the images to AVIF format:

    Hope you now understand how it works and will be able to change your opinion. I’ll be very grateful for that as I really made sure the plugin was working properly.

    Best,
    Mateusz

    Thread Starter uworlddav

    (@uworlddav)

    Thank you for your prompt response. Makes sense to me now. I’ve changed my rating to 5, you deserve it 🙂 Blessings

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Optimizes but does not changes file extensions’ is closed to new replies.