Litespeed Server not loading Webp

  • Hello

    I had W3TC well configured on my last Apache server. Now I’ve changed to a Litespeed server and it seems that some configurations doesn’t get to work. I couldn’t find out if everything is ok, I appreciate any help.

    I’ve enabled Webp conversion, all images of website were already converted. I’ve checked in library and FTP to confirm all images are there. I’ve checked that Imagick has support for Webp.

    Checking in Console Network I can see images are loading as JPG or PNG.

    I noticed that no rules were written in htaccess. But there is rules in litespeed.conf with # BEGIN W3TC WEBP and # BEGIN W3TC Browser Cache. I don’t know if that is enough or it needed to write in htaccess too.

    I also tried: Purge cache. Unninstall and reinstall W3TC plugin. Run Setup Guide again.

    What else can I troubleshoot to find out why Webp isn’t loading? Or troubleshoot if rules for the cache are written correctly.

    Thank you!

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @rafaelzrt

    Thank you for reaching out and I am happy to help!
    I’ve checked the webstie and I can see tha the images are actually converted but not served as webp, that is correct.

    https://aquabureau.com.br/wp-content/uploads/2024/01/AquaBureau-Background-02.webp
    https://aquabureau.com.br/wp-content/uploads/2024/01/AquaBureau.webp

    Are you using OpenLitespeed or an enterprise? Can you please also purge the Cloudflare cache and any server-side cache, and move the webp # BEGIN W3TC WEBP rules to the top of the litespeed.conf and also purge the W3TC cache.

    Thanks!

    Thread Starter rafaelzrt

    (@rafaelzrt)

    Thank you for your quick reply.

    All right, I purged Cloudflare cache, Emptied all W3TC caches, deleted folders of cache on server and the # BEGIN W3TC WEBP was already at the top of litespeed.conf

    About Litespeed, server support answered me it is an Lite Speed?Web?Server Enterprise.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @rafaelzrt

    Thank you for your feedback.

    Can you also please sahre how you are setting the cache control for media? Is it via Cloudflare or are you allowing origin headers?

    Also, pelase let me nknow if you are using any other image optimization plugin.

    Thanks!

    Thread Starter rafaelzrt

    (@rafaelzrt)

    Hello!

    I’m not using any other plugin for image optimization or cache.

    Sorry, can you give me more detail of what settings for cache control of media you need?

    In W3TC > Browser Cache > Media and Other files i have enabled:
    – Set Last-Modified header
    – Set expires header
    – Expires header lifetime “31536000”
    – Set cache control header?
    – Cache Control policy “cache with max-age (“public, max-age=EXPIRES_SECONDS”)”
    – Set entity tag (ETag)
    – Enable?HTTP?(gzip) compression
    – Disable cookies for static files?

    In Cloudflare > Caching > Configuration I have:
    – Caching level “Standard”
    – Browser Cache TTL “respect existing headers”
    – No cache rules
    – Tiered Cache Topology “Smart Tiered Caching Topology”

    Let me know if it was these configurations you needed or if you need more information.

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello

    For the images I can see

    Cache-Control:public, max-age=604800

    All other static files like JS and CSS have max-age=31536000, public except the https://aquabureau.com.br/wp-content/plugins/w3-total-cache/pub/js/lazyload.min.js and the CSS files from Divi in /et-cache/ folder which also have Cache-Control: public, max-age=604800.

    This means that something else, besides the W3 Total Cache and Cloudflare is handling the expiration for those files. So either some other plugin, theme or some rules in the upper level of the folder structure is setting this.

    You can check this for yourself and see that all image files and the other files I mentioned have different cache control values.
    So for example, for minified files from the W3TC, both JS and CSS have the cache control header that reflects the settings in the W3TC browser Cache max-age=31536000, public

    Can you please check the config file for any additional rules that may be handling the cache expirey for images and other files and also check any plugin or theme that may have some “Performance” optimization included.

    Thanks!

    Thread Starter rafaelzrt

    (@rafaelzrt)

    Hello Marko,

    unfortunately I still couldn’t find any other place that could be setting cache control. I’ve checked wp-config, wp-settings and /wp-content/advanced-cache.php (but that is generated by W3TC and it has the same configurations I saw in my last server). I couldn’t find other places to look for. Any suggestions please?

    I also don’t have any other plugin or theme with performance options.

    I tried turning on the “Set W3 Total Cache header” option in “W3 Total Cache > General Settings > Browser Cache” if that helps to debug as I followed the instructions here https://www.boldgrid.com/support/w3-total-cache/configuring-browser-caching-in-w3-total-cache/

    I can see that some CSS and JS has the header. As the main document. Images doesn’t, as you pointed the difference of their max-age.

    Any suggestions how I can debug this to find out what could be messing with headers?

    Would that be the reason to not loading WEBP?

    Thank you.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Litespeed Server not loading Webp’ is closed to new replies.