Your site is optimised. But when the cache misses, the server builds the page from scratch — and that is the version Google measures. CacheCrawler walks every single URL and shows you where it happens.
Nothing to install. We never touch your code.
Type your address. We find some of your pages, fetch each of them twice and show you what your CDN answered. It takes about half a minute.
We only fetch pages anyone can see. No access to your server, nothing to install.
CacheCrawler fetches your pages exactly the way a visitor does, reads the answer from your CDN and tells you what actually happened.
HIT, MISS, BYPASS, EXPIRED — we show the raw answer from your CDN for every single URL, so you can see which pages cache and which do not.
The crawl is not only a measurement. When we fetch a cold page it goes into the cache — so it is warm by the time your next customer arrives.
We go through your whole site — product pages, categories and blog posts. Not the three pages a speed test happens to hit.
We find the images in your sitemaps and in the page markup itself, including WebP and AVIF in every size. They are often the heaviest thing on the page.
You hear from us when a page stops caching — not every day about what you already know. To your inbox or to your own system.
Along the way we check the external links you point at. The broken ones are collected in one list you can work from.
Sitemap, XML, your own list — or Smart, which finds the sitemap itself and pulls it all together. No hand-maintained URL list.
If your server comes under load, the crawl slows itself down and speeds back up. You can turn that off if you would rather set it yourself.
Pages that were warm last time can be skipped, so the crawl spends its time on the ones that are actually cold. The numbers still cover the whole site.
No error, no alarm. The page is simply slow for whoever got there first — and you typically never find out.
You check the front page and it is fast. But product pages, categories and blog posts get hit less often, so they sit cold and have to be rebuilt from scratch every time someone finds them through Google.
A plugin, a cookie or a single header can take whole sections out of the cache. Everything looks right in the settings — only the answer from the server gives it away.
When the cache is cold, the first visitor waits for the whole page to be built. On a shop that is often the customer who just clicked your ad.
A cache plugin reports what it has been set up to do. That is not the same as what your CDN did with the individual page.
The settings were right. The page still was not cached — a cookie in the response turned it off.
It measured one page, once, from one place. That is not where the problem is.
| Speed test | Cache plugin | CacheCrawler | |
|---|---|---|---|
| Checks every single page | One at a time | — | Yes |
| Shows the answer from your CDN | — | Settings only | Yes |
| Finds pages that never cache | — | — | Yes |
| Warms the cache | — | — | Yes |
| Runs by itself every day | — | — | Yes |
| Counts images too | — | — | Yes |
Start with a free month on one site. Everything is included on every plan — the only thing you choose is how often your pages get checked.
For one site you want to keep in check.
For shops where something changes every day.
For looking after other people's sites.
We do not hide features behind a more expensive plan.
All prices exclude VAT. No lock-in, no setup fee.
You always begin with the free month. To move up a plan, you do that inside the product. Support lives in the same place, once you are logged in.
If the answer is not here, you can write to us inside the product once you have signed up.
A plugin tells you what it intends to do. It does not tell you what your CDN actually did with that particular page. That is the difference: we read the answer from the server for every URL, not the settings.
No. We fetch pages at a calm pace, and if the server comes under load the crawl slows itself down. You can turn that automation off and set a fixed limit if you would rather decide yourself.
No. We fetch your pages from the outside, exactly the way a visitor does. No plugins, no code on your site and no access to your control panel.
Yes, and that is where we see the most. Shops have many product pages that rarely get hit, and those are exactly the ones sitting cold. Cart and checkout must not be cached, and we leave them alone.
They count. We find them in your sitemaps and in the page markup, including WebP and AVIF in several sizes. Images are often the heaviest thing on the page, so they need to be warm too.
You decide. Daily is enough for most. If you run a shop that changes a lot, we can run several times a day or continuously.
Yes. You hear from us when something changes — when a page stops caching, or a link breaks. Not a daily reminder of what you already know. The alert can go to your inbox or to your own system.
