xSpeed Cache
Get Plugin
Features Pricing Reviews FAQ
Documentation Blog Support Community Free vs Pro Compare
Get Plugin

The Analytics Dashboard

4 min read

The Analytics module is a Pro reporting panel that brings your cache and speed data together in one view. It shows how often your cache is being used, which pages are slowest for real visitors, and what xSpeed Cache has been doing lately.

What this does

Analytics does not collect anything new. It reads data that xSpeed Cache already records and presents it as one dashboard:

  • Cache hit ratio over time — hourly buckets of cache hits and misses from the last 24 hours, drawn as a trend line.
  • 24-hour totals — total hits, total misses, and the hit ratio for the rolling 24-hour window.
  • Slowest URLs — the pages with the worst real-visitor timings, taken from Real User Monitoring.
  • Recent activity — the most recent entries from the xSpeed Cache activity log.

This module is read-only. It has no settings to configure and it does not change how your site is cached.

Why use it

A single number rarely tells you much. Seeing the hit ratio move hour by hour helps you spot when something started bypassing the cache, and the slowest-URL list points you at the specific pages worth fixing first.

Requirements

  • xSpeed Cache Pro must be active.
  • The Slowest URLs view needs Real User Monitoring data. If RUM has not collected any samples yet, this list will be empty.
  • Hit ratio and recent activity come from the free plugin’s own counters and activity log.

The views

Cache hit ratio over time

xSpeed Cache keeps a rolling 24-hour record of cache hits and misses, grouped by hour. Analytics reads those hourly buckets and charts them, so you can see the pattern rather than just a single average.

A hit means a visitor was served a cached page. A miss means the page had to be built again.

24-hour totals

A summary of the same rolling window: how many hits, how many misses, and the ratio between them. A higher ratio generally means more visitors are being served from cache.

Slowest URLs

This list comes from the Core Web Vitals samples collected by the Real User Monitoring module. For the chosen metric and time window, xSpeed Cache groups every sample by URL and reports:

  • the URL
  • its p75 value — the value that 75% of real visits came in under
  • the number of samples behind that figure

The list is sorted worst first. By default it looks at the LCP metric over the last 24 hours and shows the top 10 URLs.

The metrics available are the ones RUM collects: lcp, fcp, cls, inp, ttfb, and fid.

Note: p75 is used instead of an average because a few very slow visits would drag an average around. p75 reflects what most visitors actually experience.

Tip: A URL with only a handful of samples is not a reliable signal. Check the sample count before acting on a result.

Recent activity

Shows the latest entries from the xSpeed Cache activity log, so you can line up a change in the hit ratio with something that happened, like a cache purge. The overview shows up to 20 entries.

Best practices

  • Give Real User Monitoring time to gather samples before judging the slowest-URL list. Low sample counts are noisy.
  • When the hit ratio drops, check recent activity for a purge or a settings change around the same time.
  • Treat the slowest-URL list as a to-do list: fix the worst page first, then look again after real traffic has come through.

Troubleshooting

The slowest URLs list is empty. No Real User Monitoring samples matched the chosen metric and time window. Make sure RUM is enabled and collecting, and give it time to gather data from real visits.

The hit ratio and totals show zero. The 24-hour counters had nothing to report. This is normal on a quiet site or shortly after the cache was cleared.

FAQ

Can I change what the Analytics dashboard tracks? No. Analytics is a reporting view only. It has no settings of its own. What it can show depends on what the cache counters, the activity log, and Real User Monitoring have recorded.

Where does the data come from? From data xSpeed Cache already stores: the cache hit and miss counters, the activity log, and the Core Web Vitals samples collected by Real User Monitoring. Analytics adds no new storage.

How far back does the data go? The hit ratio trend and totals cover a rolling 24-hour window. The slowest-URL view defaults to the last 24 hours.

  • Real User Monitoring
  • Cache Health Dashboard
  • Performance Recommendations
  • PageSpeed Insights Integration