Welcome to our guide on debugging Site Speed notifications using the Ezoic Chrome Extension. Ensuring your web pages are properly cached is crucial for optimal performance, and our Chrome Extension assists by providing detailed performance analysis through the Site Speed tab. In this article, we will delve into the various reasons why a page might not be caching as expected and offer practical troubleshooting steps to resolve these issues. Whether it's cookies, cache control headers, or other factors, you'll find the information you need to address caching problems and enhance your site's speed. Let's get started on optimizing your site's performance!

Users might encounter various symptoms indicating that the page is not being cached properly when using the Ezoic Chrome Extension. If there is an alert, you will see the following in the Site Speed tab of the extension:

These alerts might include:

• Notification of Uncached Page: A message stating "This page was not cached because:" followed by a specific reason.
• Presence of Cookies: The notification mentions that cookies are preventing the request from being cached.
• Disallowed Cache Control Header Values: The headers preventing caching appear in the notification.
• Content Size Too Large: The alert indicates that the page content exceeds the maximum allowed size.
• Low Max-Age: The current max-age value is too low and needs adjustment.
• Unreadable Content: The content is malformed, making it unreadable.
• Disallowed Status Code from Origin: The server responded with a disallowed status code, such as 404.
• Presence of www-Authorization Header: Indicates that the header is preventing caching.
• Low Traffic Rate: The page has a traffic rate below the threshold for caching.
• Subsequent Calls Will Be Cached: The initial call is not cached, but subsequent ones will be.

1. Cookies are present:
   • Issue: The page is not being cached because certain cookies are preventing it.
   • Solution: Visit the Ezoic Caching App in the dashboard and enable caching for cookies if possible.
2. Disallowed cache control header values are present:
   • Issue: Certain header values are preventing caching.
   • Solution: Cease using the disallowed headers. If not possible, visit the Ezoic Caching App in the dashboard and change "Override Cache Control Headers" to true.
3. Content is too large:
   • Issue: The page content exceeds the maximum allowed size.
   • Solution: Break the page contents into smaller pages that can be linked from the main page.
4. Max-age is too low:
   • Issue: The current max-age is below the required threshold.
   • Solution: Ensure the 'maximum cache age' headers on the origin server are set higher than the recommended value. If not sent by the origin server, adjust the 'Default Cache Age(s)' value in the Ezoic Caching App in the dashboard.
5. Content is unreadable:
   • Issue: The content is malformed.
   • Solution: Resolve the issue on the site's server to make the content readable.
6. Origin responded with a disallowed status code:
   • Issue: The origin server responded with a disallowed status code (e.g., 404).
   • Solution: Investigate and fix issues with redirects, authorization, or backend server code on the site's server.
7. WWW-Authorization header is present:
   • Issue: The page uses the WWW-Authorization header, which prevents caching.
   • Solution: Modify the page to discontinue the use of this header if possible.
8. Traffic rate is below the threshold:
   • Issue: The page has a low traffic rate.
   • Solution: As the traffic rate increases, the Caching App will begin to cache the page.
9. Subsequent calls will be cached:
   • Issue: The page is not currently cached, but subsequent calls will be cached.
   • Solution: No action required; the page will be cached after this notification.

For additional debugging support, refer to our guide on improving your cache hit rate here.

To maintain optimal performance and prevent common issues with the Chrome Extension and Ezoic Caching App, consider the following tips:

1. Manage Cache Control Headers: Avoid using disallowed cache control header values. If necessary, set "Override Cache Control Headers" to true in the Ezoic Caching App.
2. Optimize Page Size: Ensure that your content is within the allowable size limit. Consider breaking larger pages into smaller, linked pages.
3. Fix Malformed Content: Ensure that the content on your server is readable and not malformed.
4. Resolve Disallowed Status Codes: Address any backend server issues, redirects, or authorization problems to prevent disallowed status codes like 404.

By following these best practices, you can ensure that your web pages are cached effectively, leading to better performance and fewer issues.

If you need further assistance debugging site speed notifications with the Ezoic Chrome Extension, please log in via https://support.ezoic.com/ to make use of our dedicated resources for support. We're here to help!