WP Rocket, LiteSpeed and W3TC preload your server's page cache — great, keep them. But if your CDN caches HTML, there's a second cache in 300+ locations worldwide that no plugin can fill. That one is ours.
A WordPress page travels through two caches before it reaches a visitor. Plugins handle the first. The second empties itself constantly — per location.
WP Rocket's preload, LiteSpeed's crawler and W3TC keep rendered HTML on your server so PHP and MySQL stay out of the hot path. This works, and we tell everyone to keep it — our guide says a plugin preload is all a single-region site needs.
With Cloudflare APO, a cache-everything rule or any CDN caching HTML, every edge location keeps its own copy. Your plugin fills exactly zero of them — it runs on your server, so its requests never even leave the building.
Publish a post, update WooCommerce stock, clear the plugin cache — most setups purge the CDN too. Until someone in each region visits each page again, your global visitors get origin-speed WordPress, TTFB and Core Web Vitals included.
wp-sitemap.xml, Yoast, Rank Math — nested sitemap indexes are resolved
automatically and re-read before every run, so new posts are picked up without any
configuration.
Requests from 42 countries fill 90+ CDN locations per pass. If your stack caches a separate mobile version (LiteSpeed and WP Rocket setups often do), an optional second pass with a mobile user agent warms that variant too.
Identifiable user agent, optional custom header — filter us in one rule. Client-side analytics (GA4, Plausible, Matomo tag) never sees warming at all, since no JavaScript is executed. Filter recipes here.
No — it complements them. Plugin preloads warm your server's page cache; we warm the CDN edge cache in 90+ locations. Run both: the plugin keeps your origin fast for cache misses, we make sure most visitors never cause one.
Yes. APO makes WordPress HTML cacheable at the edge — which is exactly the layer we warm. APO decides that HTML may be cached; warming decides where and when it actually is, instead of waiting for the first visitor per colo.
Cart, checkout and account pages send no-cache headers and are excluded from caching by every sane setup — we simply never warm what isn't cacheable. Product and category pages are where warming pays off, especially with large catalogs where the long tail is almost always cold.
Client-side analytics never counts us (we don't execute JavaScript). Server-side stats can exclude the documented WarmupRocks user agent or a custom header with one filter rule — step-by-step guide.
Free for 7 days, plans from $15/month. No plugin to install, nothing to break.