problem with x-litespeed-cache

If a URL isn’t cached then cacher header for the first request is always miss. Request URL again then it is hit.

Thanks for the reply.

Can you check if the problem is solved?

Already checked before your reply and it works as expected. You can do it by your own with browser dev console.

with x-litespeed-cache in hit mode it should help to lower the average response time of the page (in google search console)?

Yes, of course, but PageSpeed only checks TTFB, but not the loading time. It checks the “display time”. Display time is not loading time.

I am not referring to pagespeed but to google search console.
in crawl statistics there is a section “Average page response time”
Does this “hit” improve the average page response time?

In this case it doesn’t matter. A cached page is always good for whatever use, but don’t care about Google. The users who visits your page matter because if they have Chrome browser installed this browser sends data to Google and this data is the base for analyze the response time. Google doesn’t measure anything, he let users do this job.

why in the crawler/summary section I didn’t hit everyone?

please explain a bit what do you mean not hit everyone ?

Hi, it doesn’t work again.
I see again miss.
How can I fix?
Thank you

Report number:?BFGJEGXU

now after doing a refresh of the crawler it seems to work with hit. can you check why it works for days and then stops working?

You can check it by your own if you check the response header for x-litespeed-cache.

can you check why it works for days and then stops working?

You can check it by your own if you check the response header for x-litespeed-cache.