LSCache is not supported

You have an additional cache layer running. Using more than 1 cache layer running doesn’t multiply page speed.

Where I can see that? Can I manipulate it via plugin settings? Problems with the speed only apply to the desktop sizes on mobile it works fine.

Check response headers. There is a x-cache header what means that there is an additional cache. And no, you can’t disable another cache with LScache plugin.

X-Cacheable: yes

Is this it?

Where does this additional cache come from? How to check what adds it?

Is additional cache visible here as well?
https://check.lscache.io/?host=https%3A%2F%2Fmobiusdesk.pl%2Fsklep%2Fbiurko-elektryczne-debowe-140-cm-67-cm-mobiusdesk-pro-master-dab-naturalny-czarne%2F

Is this it?

Yes.

Where does this additional cache come from?

Check all other installed plugins.

Is additional cache visible here as well?

No.

But there is

X-Cacheable: yes

on mobiusdesk lscache check and I’m pretty sure hosting adds it. I have several shops on this hosting and this header is visible on all of them (closte.com). It must be something else.

The most visible difference between the two checks is that at mobius this header is visible

X-LiteSpeed-Cache: hit

and at muuv is not and I can only see this

X-LiteSpeed-Cache-Control: public,max-age=-1668876025

To my knowledge if X-LiteSpeed-Cache header hit or miss is absent there is something wrong with the host provider settings.

Now I need to verify whether this is something on the application level or hosting. Can you help me?

• This reply was modified 2 years ago by Adam.
• This reply was modified 2 years ago by Adam.
• This reply was modified 2 years ago by Adam.

it looks like your server does not have cacheroot set up , that will end up your have x-litespeed-cache: miss/hit absent

I would suggest to check with your provider first

For me, it looks like there is a proxy in front that uses Varnish.

nah , if you check again , you can see the other x-cache header is goner

also , from what I know , even you have cache layer in front of LSCache , the x-litespeed-cache header should still show , either hit or miss , unless the proxy deliberately removes the header

Found x-litespeed-cache header:
https://muuv.pl/kostiumy-kapielowe/

the link on OP’s URL still doesn’t have it , now this makes thing even weirder

need to wait for OP to clarify a bit how/what is his site setup

need to wait for OP to clarify a bit how/what is his site setup

Will it clarify by itself (cron)?

Will it clarify by itself (cron)?

A cron should do what?

Anyway, if you didn’t install any other cache plugin, the one who is responsible for this issue doesn’t know what he is doing!

x-litespeed-cache-control: public,max-age=-1669019800

just noticed tis, what’s your TTL setting ? this number looks so weird

Public Cache TTL is set to 604800 (Default).