• Resolved nadirmor

    (@nadirmor)


    Screenshot to the related topic: https://prnt.sc/nGAFDrrg3gDV

    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 2.004 milliseconds. It should be less than 600 milliseconds.
    (!) No client caching response headers were detected.
    (!) A page caching plugin was not detected.
    Learn more about page caching (opens in a new tab)

    • This topic was modified 1 year, 5 months ago by nadirmor. Reason: Detailed Explanation Provided

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • earthtopomaps

    (@earthtopomaps2016)

    I have same problem!!!
    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 1 761 milliseconds. It should be less than 600 milliseconds.
    There was 1 client caching response header detected: cf-edge-cache.
    A page caching plugin was detected.
    Learn more about page caching (opens in a new tab)

    earthtopomaps

    (@earthtopomaps2016)

    On sites which have highly variable CSS and are not using a persistent object cache, the transient caching of parsed stylesheets may be automatically disabled in order to prevent a site from filling up its wp_options table with too many transients. Examples of highly variable CSS include dynamically-generated style rules with selectors referring to user IDs or elements being given randomized background colors. There are two filters which may be used to configure the CSS transient monitoring: amp_css_transient_monitoring_threshold and amp_css_transient_monitoring_sampling_range.

    Plugin Support Milind More

    (@milindmore22)

    Hello @nadirmor and @earthtopomaps2016

    Those are just warning and not errors, AMP plugin recommends using a Caching plugin which will help improve AMP page performance and benefit your site performance.

    As mentioned in the Notice, you can use Page caching on your site using cache plugins to AMP page performance.

    You can learn more about Page caching using our documentation, Also contact your hosting provider and check if they support Persistent Object cache and implement it on your site for better AMP performance.

    I hope this is helpful!

    Plugin Support Milind More

    (@milindmore22)

    @earthtopomaps2016 @nadirmor As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you require any further assistance.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Page caching is not detected and the server response time is slow’ is closed to new replies.