CDNs cache per edge location — a visitor from Tokyo doesn't benefit from a cache filled in Frankfurt. warmup.rocks requests your pages from every corner of the world, so every first visitor gets the same instant response as your millionth.
Most cache warmers hit your site from a single server — warming exactly one edge location out of hundreds. Our requests travel through proxies in 42 countries on 6 continents, so the cache is warm where your visitors actually are. Works with any CDN that caches at the edge:
Cloudflare runs 300+ data centers, Fastly and Akamai hundreds more — and each keeps its own cache. A page cached in Paris is still ice cold in Sydney, São Paulo and Singapore.
Cache entries get evicted after their TTL — or earlier, when they're not requested often. Low-traffic pages are almost always served cold.
Every deploy or purge resets your edge cache worldwide. Until real visitors slowly refill it, everyone gets the slow origin experience.
Paste your sitemap URL — nested sitemap indexes are resolved automatically. New pages are discovered on every run. No plugin, no code, no snippet.
Each URL is requested through geo-distributed proxies in 42 countries — landing in CDN edge locations across six continents. On a schedule you control.
The dashboard tracks cache status, hit ratio, response times and colo coverage for every run — so you can prove the speedup, not just feel it.
Drop in one sitemap URL. We crawl sitemap indexes recursively, pick up new pages automatically and stop warming pages you remove. Your warming list is never stale.
HIT, MISS, EXPIRED — per URL, per colo, per run. See exactly where your cache is warm and where it needs work.
Send a custom secret header with every warming request, so your bot protection lets us through — and only us.
x-warm-secret: ••••••••
Warm every hour, every 6 hours, or right after a deploy. Trigger runs manually from the dashboard when you need them.
Cloudflare, Fastly, Akamai, CloudFront, bunny.net — we recognize the CDN from its response headers and report hit ratio and edge location per provider. Nothing to install.
TTFB is the floor under every other metric — LCP can't be fast if the first byte is slow. Warming your long-tail pages is the cheapest CWV win there is: no code changes, no redesign, just a cache that's always ready.
Preload plugins fill the cache on your server — the page cache, object cache or OPcache. That helps, but your CDN edge cache stays cold everywhere except where a request happens to originate. warmup.rocks warms the CDN layer itself, from many geographic locations, so the copy closest to each visitor is the one that's warm.
Yes — that's where it shines. Workers Cache (like the classic CDN cache) is per-colo, and it can't be filled from a single warming server. Because our requests genuinely enter Cloudflare's network in different regions, each one warms the colo it lands in.
Any CDN that caches at the edge. We auto-detect Cloudflare, Fastly, Amazon CloudFront, Akamai, bunny.net and CDN77 from their response headers and report hit ratio and edge location per provider — no configuration needed.
Warming requests come with an identifiable user agent and can carry a custom header, so you can filter them in your analytics or WAF rules. Server-side analytics can exclude them by header; client-side analytics never sees them at all, since no JavaScript is executed.
Requests are paced and rate-limited, and once the cache is warm most requests are served by the edge — never reaching your origin at all. A typical warming run touches your origin roughly once per URL, then the edge takes over.
Nothing. No plugin, no script tag, no DNS change. If your pages are publicly reachable and send cache headers, you're ready. Add your sitemap in the dashboard and start the first run.
Your next visitor deserves a warm cache — wherever they are.
Open the dashboard