🚀 Performance Tool
CDN Cache Warmer
Pre-warm your CDN edge cache by fetching URLs from your sitemap. See cache status, response times, and warming progress — all from your browser.
How does CDN cache warming work?
When you deploy or purge a CDN, edge caches are empty. The first visitor to each page triggers a slow origin fetch. Cache warming pre-fetches your URLs so the edge has cached copies ready before real visitors arrive, eliminating cold-cache latency.
Does this tool upload my sitemap?
No. Your sitemap is fetched directly from your browser using fetch(). The XML is parsed locally and URLs are requested from your machine. No data is sent to any third-party server. Open DevTools → Network to verify.
What CDNs does this work with?
Any CDN that serves cache-status headers: Cloudflare (cf-cache-status), Fastly (x-cache), Akamai (x-cache), CloudFront (x-cache), bunny.net (bunnycdn-cache-status). The tool auto-detects the CDN from response headers and displays HIT/MISS/EXPIRED status per URL.
Why not just use a WordPress preload plugin?
Preload plugins fill your origin server cache, not the CDN edge cache. Edge caches are per-location — a page cached in Frankfurt is still cold in Tokyo. This tool warms the CDN layer itself by making real HTTP requests that populate edge caches.
Will this affect my analytics?
Client-side analytics (Umami, Plausible, GA) won't see these requests because no JavaScript executes during warming. Server-side logs will show the requests — they come from your IP with a standard browser user agent.