Site Health Status

  • Resolved capturecreativeconvey

    (@capturecreativeconvey)


    1 year, 5 months ago

    Page cache is detected but the server response time is still slow
    Performance
    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 2,743 milliseconds. It should be less than the recommended 600 milliseconds threshold.
    No client caching response headers were detected.
    A page cache plugin was detected.

    Report-me-this-error-what-can-it-depend-on?

    Thanks

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    1 year, 5 months ago

    Hello @capturecreativeconvey

    Thank you for reaching out and I am happy to assist you with this.
    First of all, I can see that you are using the Disk: Enhanced caching method for Page Caching, and by default, Disk: Enhanced does not cache pages with query strings. This is why the homepage is not cached. ?v=cd32106bcb6d
    I am not sure what is adding the query string, so you should either remove it or if you need the query string for geotargeting, for example, use Disk: Basic caching method or better yet, Redis or Memcached.
    As for the Cache-Control and expires header, you can enable those in Performance>Browser Cache for all files.
    I can also see the header wpo-cache-status: not cached which means that you may be using another layer for caching (another plugin), and this is not recommended.
    Let me know if you have any other questions.
    Thanks!

    Known Universe

    (@nonuniverse)

    1 year, 3 months ago

    I had the same warning. I was using WP Super Cache and Redis Object Cache. I exempted the HOME page from caching because I have a separate header and menu for users who are guests and for those who are logged in. If the page is cached, the logged in users’ header and menus do not display.

    Is this why I might still get the caching warning? If so, is there a way to work around this?

    Thanks, NoN Universe Administrator

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Site Health Status’ is closed to new replies.