Cache Analytics
Learn how to measure CDN cache performance and analyze HIT/MISS trends using the Cache Analytics dashboard.
The Cache Analytics dashboard helps you understand how efficiently your CDN serves cached content. It allows you to identify patterns in HIT and MISS responses, determine which content types consume the most bandwidth, and analyze caching behavior by device or referrer. By optimizing your caching strategy based on these insights, you can improve response times, reduce origin load, and control delivery costs.
Cache Status Overview
Visualize cache performance over time and understand how your CDN serves cached or uncached requests.
Cache Status (time series): Displays cache responses such as HIT, MISS, or EXPIRED over time.
Cache Status Pie (pie chart): Shows proportional distribution of cache statuses for a quick visual summary.
Content Type and Client Analysis
Understand cache efficiency across different content types and user devices.
Content Types (table): Displays traffic distribution by file type (e.g., images, HTML, video).
Device Types (table): Shows cache behavior per device category (desktop, mobile, tablet).
OS (table): Lists cache performance by client operating system.
Filters
You can refine cache analysis using the following filters:
Domain
Select a specific CDN resource or domain.
Path
Focus on specific content by filtering URL path.
HTTP Referer
View caching behavior for traffic coming from specific sources.
Cache Status
Filter by cache response type (HIT, MISS, EXPIRED, etc.).
Metric
Choose between Requests, Data Transferred, or Bandwidth.
Items
Adjust the number of top entries displayed in tables or charts.
FAQ
Q1: Why is my HIT ratio lower than expected? A low HIT ratio may indicate frequent purging, short TTL values, or dynamic content that bypasses caching. Check your cache-control headers and Page Rules Settings.
Q2: What does the “EXPIRED” cache status mean? It means the content existed in cache but exceeded its TTL and required revalidation from the origin before being served.
Q3: How can I increase overall cache efficiency? Extend cache TTL for static assets, avoid unnecessary query parameters, and enable compression to reduce revalidation frequency.
Last updated
Was this helpful?