Page Cache Not Detected

  • Resolved Blue

    (@learningtreemarketing)


    1 year, 10 months ago

    Hi,

    I’m experiencing multiple issues. Please see below information:

    Report Number: SJKAKWNT

    Browser: Chrome

    Server Info:

    • LiteSpeed Web Cache Manager cache status: Enabled
    • PHP Version: 8.1

    **WordPress Site Health Notifications:

    •  Median server response time was 1,621 milliseconds. It should be less than the recommended 600 milliseconds threshold.
    •  No client caching response headers were detected.
    •  A page cache plugin was not detected.
    • You should use persistent object cache

    **Other issues

    • I regularly encounter 503 errors when editing posts and am oftentimes unable to save changes. Is this related?
    • Generally, the post-editing experience is extremely slow when it does work. Could be unrelated, but I wanted to mention it just in case.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support qtwrk

    (@qtwrk)

    1 year, 10 months ago

    I can clearly see x-litespeed-cache: hit , not sure why it doesn’t detect, but cache is working

    for 503 , it might be PHP concurrency error , as if you have some traffic at the moment you edit it

    but server should have the log for reason why 503 error , I can not speculate it further from surface.

    Thread Starter Blue

    (@learningtreemarketing)

    1 year, 10 months ago

    Got it. 

    Yes, I’ve been looking over logs and see over 863 errors related to Astra, so I’m checking with them on that. I’ll post it below just for context:

    • …public_html/wp-content/plugins/astra-addon/classes/library/image-processing-queue/includes/class-ipq-process.php on line 75PHP
      • Fatal error:  Uncaught Error: Call to undefined method WP_Image_Editor_Imagick::get_error_message()

    Additionally, I saw a PHP extension enabled (mysqli), so I enabled nd_mysqli instead, based on information I’ve been reviewing. I’m unsure if that’s related; I’m honestly over my head. For some reason, though, that seems to have reduced the 503 errors considerably and I can actually make updates to posts and pages again.

    Also, Site Health now displays this: 

    •  Median server response time was 897 milliseconds. It should be less than the recommended 600 milliseconds threshold. (improvement vs. my last message)
    • There was 1 client caching response header detected: x-litespeed-cache.

    —

    Just sharing these updates here in case it’s helpful. Looks like LiteSpeed is working fine!

    • This reply was modified 1 year, 10 months ago by Blue.
    Plugin Support qtwrk

    (@qtwrk)

    1 year, 10 months ago

    the first error is not complete , not sure what exactly was it , but 2nd error would cause 500 error instead of 503 error

    the response time is kind of high for a cached page , I would suggest to contact the hosting provider , I can not check anything further from my side since I can only tell the cache is working.

    Thread Starter Blue

    (@learningtreemarketing)

    1 year, 10 months ago

    Thank you for your help on this! I had to have a web developer take a look and they were able to find the root cause of the issues. It was due to a security plugin’s tables not reading properly, causing the 503s.

    I’m reaching out to the plugin author (Wordfence) to get more info.

    • This reply was modified 1 year, 10 months ago by Blue.
Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Page Cache Not Detected’ is closed to new replies.