stanley@litespeed

The issue has been solved on Slack. In the new version of Facet WP update, the Facet WP filter require HTML comment <!--fwp-loop--> to make it works. So our HTML minify function will conflict with it, if you are using Facet WP with LiteSpeed Cache please turn off HTML minify at this moment.

Hi @mejate, after you purged the cache at the end, please load the page once before the testing to warm up the cache.

Usually, then non-cached page score will be lower because the optimization progress require more PHP loading time.

Sorry to let you know that without an LS Server you only can use the General Feature.

Hi @aledias, our plugin is compatible with most of the content editor and it should also work with H5P plugin. You may test on it and if you find any compatible issue, please let us know, we will provide a patch on it.

Hi @aledias, could you explain more about how would you like to use LiteSpeed with React?

For the ESI function, it’s just punching a hole on the cached page, it could be a public or private cache. For more details, you may check on this blog post.

Hi @peeyooshk, have you turned ON Optimize > Exclude JQuery? If it’s still not working, please provide?your Report Number, found in?WP Admin > LiteSpeed Cache > Report.

Page cache is an important part of improving page speed, @aeterno96 please try to use our plugin with LiteSpeed Server to get the improvement.

Hi @jess69, could you send us the advance debug.log after the scheduled post published? Please put it on gist or pastebin.

Could you please join our Slack channel and find me(Stanley Cheung at Litespeed) or submit a ticket here for helping us to reproduce the bug, thanks.

Hi @aeterno96, have you tested all the optimization feature listing on this Wiki?

You also need to resize this image. Also, I find this image still has 66% reduction rate, please check on the media page to confirm has this image already optimized, if not please send image optimization again.

Hi @galbaras, the Exclude Settings is just for excluding cache, if you wish to check a non-optimized version, please add LSCWP_CTRL=before_optm query string at the end of the URL.

If you reset everything, the page should not be cached yet, could you please provide?Report Number for us to take a look?

It’s a common problem that sending a large number of images failed the optimization, please follow this thread to lower the number of the image to send each time for a temporary solution.

Also, sometimes our server might be on heavy load caused the optimization speed to slow down, “clean up unfinished data” and start optimization again is the only solution at this moment.

We’ve improved our optimization server and will be released in v3.0, please stay tuned.

The optimisation and minify function do not require WP-Cron. May I know when you calculate long loading time is that page not get cached yet?

If you turned ON optimisation and minify feature, it’s normal that the first loading time will be longer because these functions require some loading time on parsing the script.