Rumi

Hi,
Have you resolved the issue? Please try updating to v4.4.4 or higher.
Can you confirm the files are being Minified? You may look at your /wp-content/litespeed directory. If so, you would see the files generated there.

Regards

Hi,
Perhaps you just need to update Litespeed Cache plugin. Try updating to V4.4.4 or higher. You can do so by going to Toolbox > Beta Testing > Use latest GitHub Dev commit. Then upgrade. If the issue persists, you can reply to this thread.

Regards

Hi,
Ideally you should search for the footer cookie created by Woocommerce, and likewise exclude it. Perhaps by going to Cache > Woocommerce > Product Update Interval, and selecting “Always purge both product and categories on changes to the quantity or stock status.” might solve your problem.
What is the domain in question? We can take a look for you.

Regards

Hi,

Keep in mind that when Image Optimization creates a WebP file, if it is larger in size than the JPEG, the WebP file is discarded, since there is no benefit to serving a larger WebP file over a smaller JPEG. This is particularly true for mobile images. In other words, the WebP won’t be used, as the JPEG or PNG image is actually more optimal. I don’t believe there is any problem with your Image optimization

Regards,
Rumi

Hi Gerry,
there is no need to change to a different URL. Your CDN is working.
I have checked with different browsers and IP, and I still receive a header confirmation that is it still working.

Regards

Hi,
The use of private cache is to deliver cached pages to individual users. Basically, if a page can be served as a static page to a particular user multiple times, then it can be privately cached. Litespeed plugin intelligently knows whether to provide private, public, or ESI cache to the visitor.

“How to make it so that for the next visitors the pages are already issued from the cache?”
You may use a crawler to ‘warm up’ your cache for visitors, this way they are served cache without them having to get the first visit without cache.
You can learn more here.

Hi,
Have you tried updating to our latest dev branch? Toolbox > Beta Test > Use the latest GitHub dev commit. It’s possible this has been fixed in newer versions. Also, is ESI enabled? Does it re-appear after being disabled?
Otherwise, open a ticket here
and provide us with your report number, this way we can better diagnose the issue.

Regards

Hi Gerry,
If your QUIC.Cloud dashboard has an Ok for CDN, and your DNS is also verified, that means you are using CDN! There are no additional steps you need to take to activate CDN.You may also confirm your CDN is working by checking your sites Header. You will see:
x-qc-pop: NA-US-LGA-33.

NA-US-LGA-33 is the CDN PoP your content was served from.

Regards

Hi,
It is possible your balance is not updated in LWSCP Plugin yet. Try to sync your QUIC Credit on your plugin dashboard.
https://pasteboard.co/BNkrvbBgxIio.png