Litespeed Disappointing vs. WP Rocket

Hi,

on the GTMetrix report , from the HTTP response header, I can see the litespeed cache is not caching the page

this needs to show as “x-litespeed-cache: hit” to indicate the caching is working , otherwise you were literally compare cached page vs uncached page.

about CSS minify , well, each plugin has different way to handle it , so maybe our way for handling it requires some tweak the tune

since you didn’t explain in detail how “buggy” it is , I assumed it’s like page breaks or not render correctly , if that so , please check this page

Best regards,

Welp, in that case, your plugin is quite broken. If the plugin is showing activated, lets you change its options, and even benchmarks differently than no caching – and it’s not even active – you’ve got some bugs, to say the least.

We conducted 30 benchmarks, measuring WP Rocket vs. Litespeed Cache vs. no caching on 10 separate websites, in random order. In every single case, Litespeed was clearly much better than no caching, but had noticeably lower metrics across the board than WP Rocket. Had Litespeed not been caching the page, it would have shown much worse numbers.

So we know it was certainly active when it said it was.

Regarding the other bugs – there’s a lot. From the CSS breakage to the lazy loading script unnecessarily loading a blank gray image for logos in the header – it’s not at WP Rocket’s level with that stuff. Or the caching, it seems.

Anyway, I just wanted to make sure it wasn’t some strange setting or oddity.

Hi,

well , as you may already know , LSCWP requires LiteSpeed WebServer to do the caching

basically , the plugin itself doesn’t save cache for any page , but it is instruct the webserver to cache what/which page , cache for how long time , or purge the cache …etc

and in your case, the server doesn’t cache the page by setting , at least that’s what it shows from the HTTP response header

and of course , PHP application can not change the server-level setting which requires your sys admin to enabling it for you

Best regards,

That’s my problem with this plugin. I know that it checks to make sure it’s on the proper server before it will activate. Once activated, do you not consider it to be a MAJOR flaw that the plugin fails to notify the user that the server’s cache is deactivated (if that’s what you’re saying)? So if that’s the case, you have a situation where the caching appears to work since performance is much better than the plugin being deactivated, but in fact is not working at all, from what you say, without producing any error or anomaly in back end operation.