Understanding your Web Accelerator Cache reports
| Cache is now in limited release. Visit our Help Centre guide for details on how to join. |
The Web Accelerator Cache reports provide insight into how your website traffic is being handled. By monitoring these metrics, you can see how much “work” the Cache is doing to speed up your website and reduce the load on your hosting server.
Here is a guide to the terminology used in your reports and to how it is calculated.
1. Traffic
This measures the actual amount of data transferred to your visitors, regardless of whether the content was cached or fetched from the server.
It helps you understand the “weight” of the traffic your site is experiencing.
2. Requests
This is the total number of times visitors (or bots) asked your website for a file or page. This number represents the total volume of activity, regardless of whether the content was cached or fetched from the server.
3. Cache Hit %
The percentage of requests that hit (Hit and Hit Grace responses) the Cache vs the total number of requests received.
4. Responses
To understand your report, you need to know how the Web Accelerator Cache categorises every request:
| Response type | What it means | Impact on performance |
| Hit | The content was already in the Cache and served immediately without being requested from the origin server. | Fastest load time, zero server load. |
| Hit Grace | The system served an old version while fetching a fresh copy in the background. | Fast load time for the user; ensures content stays fresh. |
| Miss | Content could be cached, but it had not yet been stored in the Cache. The system fetched it from your hosting server. | Common for new content. Future visits will become “Hits.” |
| Pass | Traffic that is intentionally skipped by the Cache (e.g. the shopping cart checkout page, a logged-in dashboard, or an admin area) based on a pre-defined caching template. | Necessary for dynamic/private user data. |
| Hit-for-Miss | The Cache received an uncachable response from the origin hosting server. The server told the Cache not to store the item generally due to:
|
May indicate configuration issues or oversized files. |
Once you have your data, follow this guide to interpret your results and improve your website performance.
