Cache Strategy Checklist
Use this page as a one-page checklist when you are validating a WordPress caching stack. The detailed implementation lives in the linked pages.
Rules
- One system owns full-page caching at the origin (LiteSpeed, Nginx FastCGI, or Varnish).
- One system owns JS optimization (minify/defer/delay).
- Purge caches between comparisons (origin + CDN).
Verification Commands
Homepage (page cache + CDN):
curl-homepage-headers.sh
curl -I https://example.com/
Static asset (browser cache):
curl-static-asset-headers.sh
curl -I https://example.com/wp-content/uploads/hero.webp
Checkout (must bypass cache):
curl-checkout-bypass.sh
curl -I https://example.com/checkout/
Redis stats (server-level):
redis-hit-miss.sh
redis-cli info stats | grep -E 'keyspace_hits|keyspace_misses'
What to Look For
| Layer | Typical Header Signal | What "Good" Looks Like |
|---|---|---|
| Page cache | x-litespeed-cache or x-fastcgi-cache | HIT on repeat guest requests |
| CDN | cf-cache-status (Cloudflare) or provider equivalent | HIT on public pages, BYPASS on checkout/account |
| Browser cache | cache-control | Long max-age for assets that are versioned |
| Redis | keyspace hits/misses | Hit rate improves over time on dynamic traffic |
Common Mistakes
- Cart/checkout/account cached
- Logged-in cookies not bypassed
- Long asset TTL without versioning
- Multiple tools rewriting cache headers
- Redis without
maxmemory/ eviction policy