WordPress Page Caching: The Cache Hit Rate Diagnostic

Page caching is supposed to serve cached responses to most visitors. The cache hit rate measures how well it's working. Low hit rates mean caching isn't producing its intended benefit.

The diagnostic that reveals issues is straightforward but rarely done. Sites assume caching is working without measuring.

What the hit rate means

Each request either hits the cache (cached response served) or misses (full page generation runs). The hit rate is the percentage of requests that hit.

Target: above 70% for content sites. Higher is better.

Low hit rates (below 50%) indicate caching isn't working as expected.

The measurement

Caching plugins display hit rate statistics. WP Rocket, LiteSpeed Cache, W3 Total Cache all show this.

The dashboard shows: total requests, cache hits, cache misses, hit rate percentage.

For sites without plugin visibility, server log analysis can derive the hit rate from response patterns.

The common causes of low hit rates

Cache duration too short. Pages expire before being re-hit by another visitor. For low-traffic sites, longer expiration helps.

Cache invalidation too aggressive. Content updates trigger purges that affect many pages. Tune invalidation to be more targeted.

Many uncacheable URLs. Pages with dynamic content (cart, account, search results) can't cache. If many requests hit these pages, the hit rate naturally drops.

Cookie-bearing visitors. Logged-in users and visitors with specific cookies often bypass cache. If most visitors are logged in, cache hit rate is naturally lower.

The diagnostic steps

Step 1: confirm caching is enabled. Sometimes the plugin is installed but not actively caching.

Step 2: check what URLs are missing. The plugin may log cache misses by URL. Pattern in misses reveals causes.

Step 3: review cache exclusion rules. Excessive exclusions reduce hit rate.

Step 4: check cache expiration. Short expiration affects hit rate for any given cache slot.

The fixes

Extend cache duration for content that doesn't change frequently. Pages cached for 7 days vs 1 hour produce dramatically different hit rates.

Reduce unnecessary cache exclusions. Each exclusion is content that can't cache; verify the exclusions are necessary.

Cache logged-in users where safe. If users see the same content (not personalized cart or account), caching for logged-in users is possible. (Covered in earlier post in detail.)

The CDN cache contribution

If CDN caching is also configured, the CDN hit rate is separate from the origin cache hit rate. Both contribute to overall performance.

For sites using both, monitor both rates. A CDN with high hit rate provides edge-served content without hitting origin.

The honest framing

Cache hit rate is a quiet metric but a meaningful one. Sites with high hit rates serve most users from cache; sites with low hit rates run full page generation for too many requests.

The diagnostic and optimization produces measurable improvement in server resource usage and response time.