Cache Check
See whether a page is served from cache, with the response headers.
Demo tool - results are sample data, not a live lookup.
About the Cache Check
A cached page is served in milliseconds because the server (or a CDN like Cloudflare) hands back a stored copy instead of rebuilding it with PHP and the database. Whether a request was a cache HIT or MISS is reported in response headers such as x-cache, cf-cache-status, and age.
This tool reads those headers so you can confirm your caching is actually working, spot pages that never cache, and see how long cached copies stay fresh.
How to use it
- 1Enter the page URL you want to test.
- 2Run the check to see the cache status and the relevant caching headers.
- 3Reload once or twice. The first request often MISSes, then subsequent ones should HIT.
What it checks
- Cache status
- HIT means served from cache; MISS/DYNAMIC means it was built fresh.
- cache-control
- How long browsers and proxies may store the response (max-age).
- age
- How many seconds ago the cached copy was stored.
- cf-cache-status / x-cache
- The CDN or proxy's own verdict for this request.
Frequently asked questions
Why does my first request show MISS?
The cache was empty for that URL, so it was generated and stored. The next request for the same URL should HIT.
Should wp-admin be cached?
No. Logged-in and admin pages must bypass the cache so users always see live data. Only public pages should be cached.
How long should pages stay cached?
Longer for stable content (hours to days) and shorter for pages that change often. Always flush the cache after major updates.
Run WordPress on infrastructure built for it.
Performance, security, and the WordPress tooling you need - fully managed, so these checks stay green.