Sitehealth error: There was 1 client caching response header detected: etag.

  • My Site Health Status constantly shows a critical error:

    Page cache was detected but the server response time is still slow.

    Median server response time was 888 milliseconds. It should be less than the recommended 600 milliseconds threshold.

    There was 1 client caching response header detected: etag.

    I have LiteSpeed Cache installed on my site and I am not sure why this message appears and how to fix it. I would be very grateful for some help, as I am not a techy person at all.

    Thank you very much for your help!

    Carmen

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator bcworkz

    (@bcworkz)

    The etag header is likely from LiteSpeed. If you want to be certain, I suggest asking in their dedicated support forum. Its presence is not the problem though, the problem is a rather slow server response. However, it’s little more than a quarter of a second more than what’s considered acceptable. If your overall page load speed is reasonable, then you could choose to ignore the error. It’s not really “critical” as claimed.

    Server response time is dependent on your server configuration and hosting plan. Generally speaking, low cost shared hosting plans can be a bit pokey. If you still want to improve server response time, I recommend contacting your host for suggestions about what could be done.

    Hi Carmen,

    To fix the slow server response time issue despite having LiteSpeed Cache installed, try the following steps:

    1. Optimize LiteSpeed Cache Settings:
    • Go to LiteSpeed Cache > Cache > Settings.
    • Ensure settings like Cache Logged-in Users and Cache Mobile are properly configured.
    • Enable Object Cache if available.
    1. Update Plugins and Themes: Make sure all your plugins and themes are up-to-date to avoid compatibility issues.
    2. Use a CDN: Consider using a Content Delivery Network (CDN) to speed up content delivery.
    3. Database Optimization:
    • Optimize your database by accessing the Database section in LiteSpeed Cache.
    1. Check Server Resources: Ensure your hosting plan provides sufficient resources (CPU, RAM).

    If these steps don’t resolve the issue, let me know.

    Best,

    Thread Starter tfndnwmy

    (@tfndnwmy)

    @bcworkz and @melodipace.

    Thank you very much for your responses.

    I am with BigScoots so I figured my host is good, but I will definitely look into both of your suggestions.

    I really appreciate your help, thank you again!

    All the best,

    Carmen

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Sitehealth error: There was 1 client caching response header detected: etag.’ is closed to new replies.