Issue WebP on the fly with Cache Everything rule

  • Resolved fedlab

    (@fedlab)


    2 years, 5 months ago

    Hi,

    I use Litespeed to serve WebP images. It replaces the image url in the CSS on the fly from what I understood. If there is no cache, the first time the page will load, webP images will be served. But with Cache Everything rule, it will start to serve the png/jpeg files. Is there a way not to cache parts of the html code (where the images are replaced on the fly)?

    This is the only (free, server side) way I can serve WebP images. I am using Elementor, embedding CSS internally in order for Litespeed to find it and replace it. I could not use Optimole for the bugs it was creating and for performance reasons…

    If I set standard cache, webp will be always served, but i increase a lot the server response time…

    I also had to disable fallback cache to serve constantly webP…

Viewing 1 replies (of 1 total)
  • Plugin Contributor iSaumya

    (@isaumya)

    In this particular case you cannot cache your pages on CDN as in that case lightspeed won’t be able to change your images to WebP. If you want CDN level page caching you need to look for some other way of image optimization like Cloudflare Polish, Optimole or Imagekit.io where you can receive webp even if the pages are served from CDN.

Viewing 1 replies (of 1 total)
  • The topic ‘Issue WebP on the fly with Cache Everything rule’ is closed to new replies.