A CDN isn't one cache — it's hundreds of independent ones, and most are cold. Cloudflare alone runs 300+ data centers, each with its own memory. Your page can be blazing fast in Frankfurt and ice cold in Tokyo, where the first visitor pays the full origin round trip. Across 408,000 measured CDN requests, a cache miss was 3.5× slower than a hit.

warmup.rocks solves the cold-cache problem at the edge. On a schedule, it requests your pages from 42 countries across 6 continents — each request enters the CDN in a different region and fills the edge it lands in. 90+ edge locations warmed per pass. Every visitor, every region, a warm cache hit.

Warming without verification is just hoping. So we verify everything: every response's cache status (cf-cache-status, x-cache and equivalents) is recorded, and you see the real cache hit ratio — per edge location, per run.

Built for the modern stack:

• 🗺️ Sitemap auto-discovery — nested sitemap indexes resolved before every run

• 🔍 CDN auto-detection — Cloudflare, Fastly, CloudFront, Akamai, bunny.net, CDN77

• 🚀 Deploy hooks + official GitHub Action — re-warm the second your CI purges the cache

• 📱 Mobile cache variant — a second pass with a mobile user agent

• 🔔 Email alerts when a WAF rule blocks warming runs

Nothing to install. No plugin, no DNS change.

Free tools, no signup: multi-location cache checker and website speed test.

A CDN isn't one cache — it's hundreds of independent ones, and most are cold. Cloudflare alone runs 300+ data centers, each with its own memory. Your page can be blazing fast in Frankfurt and ice cold in Tokyo, where the first visitor pays the full origin round trip. Across 408,000 measured CDN requests, a cache miss was 3.5× slower than a hit.

warmup.rocks solves the cold-cache problem at the edge. On a schedule, it requests your pages from 42 countries across 6 continents — each request enters the CDN in a different region and fills the edge it lands in. 90+ edge locations warmed per pass. Every visitor, every region, a warm cache hit.

Warming without verification is just hoping. So we verify everything: every response's cache status (cf-cache-status, x-cache and equivalents) is recorded, and you see the real cache hit ratio — per edge location, per run.

Built for the modern stack:

• 🗺️ Sitemap auto-discovery — nested sitemap indexes resolved before every run

• 🔍 CDN auto-detection — Cloudflare, Fastly, CloudFront, Akamai, bunny.net, CDN77

• 🚀 Deploy hooks + official GitHub Action — re-warm the second your CI purges the cache

• 📱 Mobile cache variant — a second pass with a mobile user agent

• 🔔 Email alerts when a WAF rule blocks warming runs

Nothing to install. No plugin, no DNS change.

Free tools, no signup: multi-location cache checker and website speed test.