The Chrome Extension provides web page performance analysis to publishers through the Site Speed tab. Currently the primary aspect of analysis is whether or not the page is cached. Once the Ezoic Caching App is enabled, the Chrome Extension will report if there is a reason why a particular page is not being cached, and the current load time.
If an alert is present, it will look like the following:
The message "This page was not cached because:" is followed by the reason why the page at the URL listed is not caching. Here are the possible reasons the page is not being cached, and some suggestions you may choose to make that will help this page to be cached in the future if applicable.
cookies are present - This reason is followed by the cookies that are preventing this request from being cached in parenthesis. To allow the page to be cached, visit the Ezoic Caching App in the publisher dashboard, and Enable Caching for Cookies if possible.
disallowed cache control header values are present - This reason is followed by the header value that is preventing the caching to occur in parenthesis. To allow this page to be cached, the publisher should ideally cease using the headers listed. If that is not an option, the publisher can visit the Ezoic Caching App in the publisher dashboard, and change "Override Cache Control Headers" to true.
the content is too large - This reason is followed by the maximum allowed size in parenthesis. This is not currently a configurable value. To allow this page to be cached, consider breaking the page contents into smaller pages that can be linked from the main page.
the max-age is too low - This reason is followed by the current max age and the value that it will need to be adjusted to be greater than. To allow this page to be cached, check to make sure the 'maximum cache age' headers you have set up on the origin server end are greater than the value recommended. If this is not being sent by the origin server, you may need to adjust the 'Default Cache Age(s)' value in the Ezoic Caching App in the publisher dashboard.
the content is unreadable - The message indicates that the content is malformed in some way. This problem likely needs to be resolved on the publisher's server in order for the page to be.
the origin responded with a disallowed status code - The reason in this case is followed by the status code (e.g., 404). In the unlikely event that this occurs within the chrome extension notification, there may be an issue with redirects, authorization, or backend server code on the publisher's server that needs to be fixed in order for the page to the cached.
the www-authorization header is present - In order for this page to be cached, this page must be modified to discontinue the use of this header if possible.
the traffic rate is below the threshold - This code may occur for newly created pages or pages with fewer visitors than others. As the traffic rate increases on the page, the Caching App will begin to cache the page.
subsequent calls will be cached - The Caching App is not currently caching the page, but will following this message being displayed.
Additional debugging support for the Ezoic Caching App can be found here.
If you choose not to make changes, you may click the "Dismiss" checkbox to avoid seeing the notification while working in your current Chrome Extension session.