| 开发者 | wpfixfast |
|---|---|
| 更新时间 | 2026年3月11日 17:13 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/You need a Cloudflare Worker URL (required) and optionally Webshare.io proxies for better global coverage. The plugin provides the Worker script code to deploy to your Cloudflare account. A sitemap is also required — any SEO plugin like Yoast or RankMath will generate one automatically.
Yes, strongly recommended. Cloudflare only caches static files by default — not HTML pages. Without a full-page caching plugin like Super Page Cache, preloading your URLs will have no effect on page load times. Always set up full-page caching before running the preloader.
It pre-warms Cloudflare's edge caches globally, reducing Time to First Byte (TTFB) and improving Core Web Vitals scores — especially Largest Contentful Paint (LCP). Instead of the first visitor in a region triggering a slow cache miss, content is already cached near them before they arrive.
Full Proxy Pass sends every URL through every proxy in your list, maximizing the number of Cloudflare edge locations warmed in a single run. It significantly increases run time and request volume, so it's best used occasionally rather than as your regular scheduled interval. Per-URL stats are not recorded in this mode.
There is no fixed requirement. More proxies from diverse geographic locations means more Cloudflare edge locations get warmed. Webshare.io's rotating residential proxies work well. Even a small list of 10 proxies from different regions can make a meaningful difference.
No. The plugin runs via WordPress cron in the background and processes URLs in small batches with a configurable delay between requests. It does not affect your site's frontend performance or normal traffic.
The new cron event is automatically skipped. The plugin uses overlapping run protection to ensure only one preload run is active at a time, preventing duplicate requests and server overload.
It depends on how frequently your content changes and how aggressively Cloudflare expires cached content. For most sites, once or twice daily is sufficient. If you update content frequently, hourly may be more appropriate.
Cloudflare routes requests to the nearest available edge based on the proxy's geographic location. As proxies rotate and network conditions change, different edges may serve the same URL across runs. This is normal and expected.
Yes. Without proxies, requests go directly from your server and only warm the nearest Cloudflare edge location to your server. Adding proxies from multiple regions is what enables global cache warming.