Wordpress LScache Plugin: Issues with Cloudflare and LiteSpeed
Last Updated on: Wed, 15 Apr 2026 00:00:02 Dear developers off LiteSpeed WordPress plugin, I apperiacte a lot about the LiteSpeed plugin. But there is one thing that have been consistently not working and thats LiteSpeed + Cloudflare and .webp images. Some older browser like Internet explorer and Safari does not support .webp. And it becomes a problem when litespeed creates a cache containg .webp images only and not offering .jpg as a fallback for those older browser. Why cant you either 1, add a option to offer client both webp and jpg 2, offer it as a special feature / option for website using services like cloudflare My current work around is to disable .webp from LiteSpeed, then cloudflare offer that feature in there pro plan for 20 dollar a month per site? The page I need help with: https://malardalenvvs.se/ Hi, when LSCWP optimize images , it will do : image.jpg -> renamed to image.bk.jpg image.jpg -> optimized version image.jpg.webp -> webp version. every images will have its non-webp version and webp is only sent to browser that supports with accept: image/webp header Best regards, Yes I understand that, however the problem for me is that if a visitor uses an old browser, LiteSpeed will generate HTML containing only .jpg version srcset of images and Cloudflare will cache that response from LiteSpeed and serve it. Hi, Yes, but thats Cloudflares issue. if you use cloudflare to cache your dynamic page , as CloudFlare can not vary based on users browser (it does actually , but only on Enterprise plan) , then you can not have 2 different sets for different users. Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference