描述
A WordPress cache preloader warms your server. warmup.rocks warms the CDN edges between your server and visitors around the world.
A visitor in Zurich and a visitor in Singapore do not use the same CDN cache. One location may return a fast cache hit while another still has to contact your origin.
warmup.rocks connects WordPress to a managed cache warmer. After you publish or update public content, the plugin asks the service to request your sitemap URLs from distributed locations. The run records which CDN edge answered and whether it returned a HIT, MISS, BYPASS, or another cache status.
It works with Cloudflare, Amazon CloudFront, Fastly, Akamai, bunny.net, and CDN77. Detection uses the response headers each CDN already sends. Other CDNs can still be warmed, but their provider and edge location may appear as unknown when they do not expose recognizable headers.
You do not need to install a proxy list, run a crawler inside WordPress, or deploy your own Cloudflare Worker. warmup.rocks handles the remote requests. The WordPress plugin stays small and only sends a trigger when the site changes.
Use it after WordPress updates, CDN cache purges, deploys, or TTL expiry. The dashboard shows whether each request produced a HIT, MISS, EXPIRED, BYPASS, or DYNAMIC response, so a completed crawl is not mistaken for a warm edge cache.
The plugin:
- groups quick edits for 90 seconds before requesting a run;
- reacts to published posts, pages, products, taxonomies, themes, and plugins;
- adds a manual Warm now action;
- shows project and latest-run status in WordPress;
- detects and securely syncs same-site WordPress core or Yoast sitemap URLs;
- sends no post content, customer data, WordPress credentials, or visitor cookies;
- includes a complete German translation source for WordPress.org language packs.
A warmup.rocks account and project are required. The remote service performs the cache-warming requests and may require a paid plan. See how the global cache warmer works, including supported CDNs, edge reporting, and current plans. The plugin does not make private pages public, change cache headers, or weaken WooCommerce safety rules.
External service
This plugin connects to https://warmup.rocks when an administrator checks status, starts a manual run, or when a scheduled automatic warming request is due.
Data sent: plugin version, the public site URL, detected same-site sitemap URLs, a short change reason such as content or site, and the secret Deploy Hook token when a run is triggered. During one-click setup, WordPress sends the HTTPS site URL, its same-origin admin callback URL, a random state value, and a short-lived exchange code. The hook secret never appears in the browser address. No post content, customer data, WordPress credentials, or visitor cookies are sent.
Service terms: https://warmup.rocks/terms
Privacy policy: https://warmup.rocks/privacy
屏幕截图
安装
- Upload the
warmup-rocksdirectory to/wp-content/plugins/, or install the ZIP in Plugins > Add New. - Activate the plugin.
- In WordPress, open Settings > warmup.rocks and select Connect to warmup.rocks.
- Sign in, then choose an owned project whose HTTPS origin matches the WordPress site.
- Return to WordPress and use Warm now to test the connection. Manual Deploy Hook entry remains under Advanced.
常见问题
-
Which CDNs does it support?
-
warmup.rocks recognizes cache and edge headers from Cloudflare, Amazon CloudFront, Fastly, Akamai, bunny.net, and CDN77. It can send warming requests to other CDNs too, but detailed provider or edge reporting depends on the headers returned by that CDN.
-
Is this only a Cloudflare cache warmer?
-
No. Cloudflare is supported, but it is not required. The same WordPress trigger works with CloudFront, Fastly, Akamai, bunny.net, CDN77, and other CDN setups that cache your public pages.
-
Do I need a Cloudflare Worker or my own proxies?
-
No. The warming run happens on warmup.rocks, outside WordPress. You do not have to deploy a Worker, buy a proxy plan, or keep a long crawler process running on your web server.
-
Does this plugin cache pages inside WordPress?
-
No. It asks warmup.rocks to visit public URLs from your sitemap through distributed locations. Your CDN decides whether a response can be cached. If the CDN returns BYPASS or DYNAMIC, the dashboard reports that instead of claiming the page was warmed.
-
Does it replace WP Rocket, LiteSpeed Cache or W3 Total Cache?
-
No. Those WordPress cache plugins preload the page cache on your origin server. warmup.rocks warms the separate CDN edge cache used by Cloudflare, CloudFront, Fastly, Akamai, bunny.net and other CDNs. Keep your page-cache plugin enabled and use both layers.
-
Does the CDN cache warmer work with Cloudflare APO?
-
Yes. Cloudflare APO makes public WordPress HTML cacheable at the edge. warmup.rocks requests those pages from distributed locations and reports whether Cloudflare returned HIT, MISS, EXPIRED, BYPASS or DYNAMIC. It does not replace APO or change your Cloudflare cache rules.
-
What happens after a CDN cache purge or TTL expiry?
-
A purge removes cached copies, while each CDN edge can also expire or evict a page independently. Publish-triggered and scheduled runs request the public URLs again. Adaptive warming uses observed cache headers and HIT/MISS history to avoid blindly warming every URL on every run.
-
Which WordPress sitemaps are supported?
-
The plugin detects WordPress core sitemaps plus common Yoast SEO and Rank Math sitemap indexes on the same HTTPS site. warmup.rocks resolves nested indexes before runs, so newly published public pages can be discovered without maintaining a URL list by hand.
-
Is CDN cache warming safe for WooCommerce?
-
Yes, when the CDN already excludes carts, checkout, accounts, logged-in sessions, and private responses. The plugin does not weaken those rules. It warms public product and category pages, while your CDN remains responsible for deciding what may be cached.
-
What happens after several quick edits?
-
The plugin groups changes for 90 seconds. warmup.rocks also enforces a server-side cooldown, so repeated edits do not create a run for every save.
-
How does one-click connection protect the Deploy Hook?
-
WordPress starts the flow from an authenticated administrator action with a nonce and random state. The dashboard only lists owned projects with the exact same HTTPS origin. It returns a single-use code that expires after 10 minutes. WordPress exchanges that code directly with warmup.rocks, so the Deploy Hook secret never appears in the browser address. Manual hook entry remains available under Advanced.
-
When does the plugin ask for a review?
-
The plugin waits at least seven days and at least three completed runs for the connected project. It does not require cache hits or a positive result. You can leave an honest review, postpone the notice for 30 days, or dismiss it permanently.
评价
此插件暂无评价。
贡献者及开发者
「warmup.rocks – WordPress CDN Cache Warmer & Edge Monitor」是开源软件。 以下人员对此插件做出了贡献。
贡献者
更新日志
1.1.0
- Add secure browser-based WordPress connection with exact-origin project matching and single-use exchange codes.
- Keep manual Deploy Hook entry as an advanced fallback.
- Add a neutral review notice after seven days and three completed runs, with later and permanent-dismiss choices.
1.0.1
- Explain the difference between WordPress page-cache preloaders and global CDN edge warming.
- Expand Cloudflare APO, cache purge, TTL, sitemap, WooCommerce, and troubleshooting documentation.
- Update the WordPress.org product screenshot to show the measured global edge network.
1.0.0
- First stable release: managed global CDN cache warming, change triggers, sitemap sync, manual runs, and project status.