Amp cache error

  • Resolved onurkk

    (@onurkk)


    2 years, 7 months ago

    I am using Litespeed and I get the following error even though mobile cache is turned on.

    “The AMP plugin performs at its best when page caching is enabled. This is because the additional optimizations performed require additional server processing time, and page caching ensures that responses are served quickly.

    Page caching is detected by looking for an active page caching 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, x-proxy-cache, cf-cache-status, x-kinsta-cache, x-cache-enabled, x-cache-disabled, cf-apo-via, x-srcache-store-status, x-srcache-fetch-status, cf-edge-cache.

    Median server response time was 86 milliseconds. This is less than the 600 millisecond threshold.
    No client caching response headers were detected.
    A page caching plugin was not detected.”

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • qtwrk

    (@qtwrk)

    2 years, 7 months ago

    Hi,

    I am support staff of LiteSpeed Cache plugin , the issue here seems that AMP doesn’t detect our cache header x-litespeed-cache

    is there any filter we can use ? like site_status_page_cache_supported_cache_headers filter on wordpress ?

    Best regards,

    Thread Starter onurkk

    (@onurkk)

    2 years, 7 months ago

    I don’t understand, how can I check this?

    qtwrk

    (@qtwrk)

    2 years, 7 months ago

    that was a question to AMP support , let’s wait for their reply 🙂

    Plugin Support Milind More

    (@milindmore22)

    2 years, 7 months ago

    Hello @onurkk

    Thank you for contacting us, it is a warning and not error.

    If you are using the Cache plugin then you can ignore the warning, as mentioned in the notice it only checks those headers and serves the purpose of informing users that they need to use the cache plugin for better AMP performance.

    Hello @qtwrk

    This is a nice suggestion! I have created github issues for same

    We hope this helps!

    Plugin Author Weston Ruter

    (@westonruter)

    2 years, 7 months ago

    I think we can just remove the Site Health test for page caching from the AMP plugin. It actually served as the basis for what was merged into WordPress core. So now it is redundant.

    qtwrk

    (@qtwrk)

    2 years, 7 months ago

    thanks for the update 🙂

    Plugin Support Milind More

    (@milindmore22)

    2 years, 6 months ago

    @qtwrk and @onurkk We hope your query is answered, I will mark this topic as resolved.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Amp cache error’ is closed to new replies.

Tags