Free agency tools / Cache & CDN Checker
Is this page actually cached?
We read the cache headers of the page and its key assets and tell you what's cacheable, how long for, whether the CDN edge served aHIT or a MISS, and which CDN is in front of each file.
Results for
| Resource | Edge | Cacheable | TTL | CDN |
|---|
How it works
- 1Enter a URL — we fetch the page and a sample of its CSS, JS and images.
- 2For each resource we read Cache-Control, Expires, ETag and Last-Modified to work out if (and how long) it's cacheable.
- 3Edge headers (cf-cache-status, x-cache, cache-status, age) tell us whether the CDN served a HIT or a MISS, and which CDN it is.
Frequently asked
What's the difference between browser and edge caching?
Browser caching (Cache-Control/Expires) tells the visitor's browser to reuse a file. Edge caching is the CDN holding a copy near the visitor — a HIT means it answered without going back to your server.
Why is the page itself often a MISS or DYNAMIC?
HTML is frequently left uncached or marked dynamic so content stays fresh, while static assets (CSS/JS/images) get long cache lifetimes. Full-page caching changes that and is usually the biggest win.
Caches are regional — is this the whole picture?
A HIT here reflects the edge nearest our scanner. A resource can be a HIT in one region and a MISS in another until it's been requested there.