The RunCache dashboard and wp runcache stats command report three cache statistics:

  1. Cached Pages
  2. Cache Size
  3. Compression Ratio

How RunCache calculates these values depends on the active cache type. These statistics do not include cache hits, misses, or hit rates.

Key Points

  • Dashboard statistics may not update immediately. Depending on the cache type, reported values can lag behind the current cache state by up to two minutes.
  • For file-based cache types, Cache Size reports the size of cached HTML files only. Compressed files and metadata files are not included, so the value may be lower than the cache’s total disk space usage.
  • For NGINX FastCGI, Redis, and LiteSpeed, some statistics are calculated differently from the file-based cache types. In such cases, the Compression Ratio reports 0.0% because RunCache does not measure compression for those providers.

The sections below explain how RunCache calculates each statistic for the supported cache types.

PHP, NGINX Page Cache, and Apache Page Cache

For these file-based cache types, RunCache scans the cache directory and counts cached .html files.

  • Cached Pages is the number of cached .html files RunCache finds.
  • Cache Size is the combined size of the cached .html files. RunCache does not include related .gz or .meta files, so the reported value may be lower than the cache’s total disk space usage.
  • Compression Ratio shows the percentage reduction achieved by gzip compression. For example, if a 100 KB page is compressed to 20 KB, the compression ratio is 80%.
RunCache dashboard stat cards reading Cache Status Enabled with PHP Cache, Pages Cached 0, Cache Size 0 B and Compression Ratio 0.0%, above the cache type tabs and the Choose a Cache Type cards

A RunCache dashboard with no cached pages yet. Cached Pages and Cache Size are zero, and Compression Ratio shows 0.0%.

A tight crop of the four RunCache stat cards in a single row. Cache Status reads Enabled with PHP Cache under it and a pink toggle switched on. Pages Cached reads 0, Cache Size reads 0 B and Compression Ratio reads 0.0 percent, each with a small pink outline icon on its right.

RunCache records compression data when it creates the compressed copy of a cached page. If gzip compression is disabled, the Compression Ratio displays 0.0%.

NGINX FastCGI Cache

NGINX FastCGI Cache stores cached entries differently from the file-based HTML cache types, so RunCache calculates its statistics separately.

Cached Pages counts the FastCGI cache entries, while Cache Size reports their combined size.

A single cache type card. A grey off toggle sits beside the heading Nginx FastCGI Cache, above the description: Caches pages directly in NGINX FastCGI Cache for optimal performance, bypassing PHP and WordPress for cached requests.

Cache Size can include NGINX cache metadata as well as cached response data. RunCache does not calculate Compression Ratio for NGINX FastCGI Cache, so the dashboard displays 0.0%.

Redis Page Cache

Redis Page Cache stores cached pages in Redis rather than on disk. RunCache calculates its statistics from the matching Redis cache entries.

  • Cached Pages is the number of cached Redis entries RunCache finds.
  • Cache Size is the combined size of the stored cache values. It does not represent total Redis memory usage and may not match values reported by Redis memory statistics.
  • Compression Ratio displays 0.0% because RunCache does not measure compression for Redis Page Cache.
A single cache type card. A grey off toggle sits beside the heading Redis Page Cache, above the description: Stores cached pages in Redis and serves them through PHP, providing fast in-memory page caching with minimal server configuration.

If all Redis cache statistics unexpectedly show zero, check whether the cache is empty and review the RunCache logs for Redis connection errors.

LiteSpeed Cache

LiteSpeed manages the cached content directly. RunCache therefore tracks cache statistics separately rather than reading LiteSpeed’s cache files.

  • Cached Pages is based on the cache entries RunCache has tracked within the configured expiration period.
  • Cache Size is an estimate based on the cached page sizes recorded by RunCache. It does not represent LiteSpeed’s actual cache storage usage.
  • Compression Ratio displays 0.0% because RunCache does not measure compression for LiteSpeed Cache.

Because LiteSpeed controls whether a response is ultimately stored, the Cached Pages value should be treated as an estimate rather than an exact count of LiteSpeed cache entries.

Cache Hits, Misses, and Hit Rates

RunCache does not currently report cache hits, misses, or hit rates in the dashboard or through wp runcache stats.

If you need to measure cache hits, you can track the X-RunCache-Status response header.

Why Dashboard Statistics Can Be Delayed

RunCache temporarily caches dashboard statistics to avoid recalculating them on every request. Depending on the active cache type, the displayed values can remain cached for up to about two minutes.

Purging or preloading the cache, or saving page cache settings, can refresh the dashboard statistics. Some provider-specific values may still take a short time to update.

View Cache Statistics with WP-CLI

To view the same cache statistics from the command line, run the following command from your WordPress installation:

wp runcache stats

For WordPress Multisite, use --url to specify the site.

Without an additional option, the command displays all three statistics:

WP cache stats

You can also return an individual statistic:

wp runcache stats --pages
wp runcache stats --size
wp runcache stats --ratio

If you see zero values, then you don’t need to be concerned, as building the cache takes some time and zero values are not always a sign of a problem.

Immediately after a purge, Cached Pages and Cache Size can correctly show 0 and 0 B. For NGINX FastCGI, Redis, and LiteSpeed, Compression Ratio displays 0.0% because RunCache does not measure compression for those cache types.