cache Issue [Page cache is not detected but the server response time is OK]

#1
my all wordpress site show this problem: Page cache is not detected but the server response time is OK
Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.
Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:
cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status.
  • Median server response time was 297 milliseconds. This is less than the recommended 600 milliseconds threshold.
  • No client caching response headers were detected.
  • A page cache plugin was not detected.
 

Cold-Egg

Administrator
#3
Saw a similar ticket/issue from other places, reply here too,

Our header x-litespeed-cache is not included in the health tools check for http response header, that's why it complains. If you check the site from https://check.lscache.io/, it should shows LiteSpeed cache is a hit.
 
#4
Im having the same issue as this. I get the Wordpress error as above but also getting a error on https://check.lscache.io/

timswebworx.co.za
LSCache is not supported
HTTP Header
HTTP/1.1 200 OK
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
x-powered-by: PHP/8.1.12
content-security-policy: upgrade-insecure-requests;
x-xss-protection: 0
referrer-policy: strict-origin-when-cross-origin
x-frame-options: SAMEORIGIN
x-dns-prefetch-control: on
x-litespeed-tag: f52_HTTP.200
content-type: text/html; charset=UTF-8
x-litespeed-cache-control: no-cache
vary: Accept-Encoding,User-Agent
transfer-encoding: chunked
content-encoding: gzip
date: Mon, 02 Jan 2023 09:56:13 GMT
server: LiteSpeed
x-qc-pop: NA-US-LGA-33
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"
 

Cold-Egg

Administrator
#5
HI @Tman1816c
no-cache is different, it means the page is set to no-cache for some reason. To check the reason, please turn on the debug log from the plugin and you should get the information from there.
 

Cold-Egg

Administrator
#8
Checked again, it's cache now, maybe you have changed something and fixed the issue?
Code:
HTTP/1.1 200 OK
Connection: Keep-Alive
Keep-Alive: timeout=5, max=100
x-powered-by: PHP/8.1.12
content-type: text/html; charset=UTF-8
etag: "739-1672790863;gz"
vary: Accept-Encoding,User-Agent
x-qc-cache: hit
content-encoding: gzip
content-length: 35804
date: Wed, 04 Jan 2023 00:55:16 GMT
server: LiteSpeed
x-qc-pop: NA-US-LGA-33
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"
 
Top