What Is My Page Cached? measures
The test requests your page and reads the response headers that describe caching: whether a CDN or server cache answered, how long the answer is allowed to be reused, and whether a cache layer reported a hit or a miss.
How to read your result
A hit means the page was served from cache and never touched your application. A miss on the first request is normal, so run it twice; a miss on the second request means caching is not working. Watch for headers that tell browsers not to store anything, which some plugins and login systems add to every page by accident.
What to change first
If you keep getting misses, check whether something is setting a cookie on every visit, because most caching layers skip any request that carries a session cookie. Analytics and consent banners are frequent culprits when they are set server side.
Common questions
- Why does my page show a cache miss every time?
- Usually a cookie is being set on every request, or a caching rule excludes the page. Logged in sessions are excluded on purpose and will always miss.
- Should every page be cached?
- No. Carts, checkouts, account pages and anything personalised must not be cached. Normal content pages should be.
Related tests
Run this alongside every other test in Website Speed Tests, or start from the full list of website testing tools.