Description
Super Preloader for Cloudflare helps you warm your site’s edge cache across multiple Cloudflare nodes using proxies and a Worker URL. Perfect for globally distributed cache coverage.
Getting Started
This plugin helps warm up Cloudflare edge caches by preloading your public URLs using a Worker script and optional rotating proxies. It helps reduce time-to-first-byte (TTFB) and improve real user performance metrics by ensuring content is already cached near your visitors.
Normally, Cloudflare only populates its edge cache in a specific location when a visitor from that region requests the page. This means content may be slow for first-time visitors in other geographic regions. By sending preload requests from various IP locations, the plugin helps increase Cloudflare cache hit rates across multiple edges.
It works best when used together with a caching plugin like Super Page Cache, since Cloudflare does not cache HTML responses by default—only static assets like images, CSS, and JS. This can lead to better scores in Core Web Vitals—especially the Largest Contentful Paint (LCP)—which is a key factor in SEO and user experience.
To get started, follow the detailed instructions in our How to Use section below.
Recommended steps:
- Deploy Cloudflare Worker using API Token
- Get your Webshare proxies download link
- Create your sitemap using Yoast SEO, RankMath SEO, or a similar plugin
- Start preloading
How to Use
Installation
- Upload the plugin folder to
/wp-content/plugins/ - Activate via the Plugins menu in WordPress
- Go to Settings → Super Preloader to configure your Worker, Proxy list, and Sitemap.
FAQ
What do I need to use this plugin?
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.
Do I need a caching plugin?
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.
How does this improve my site performance?
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.
What is Full Proxy Pass mode?
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.
How many proxies do I need?
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.
Will this slow down my server?
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.
What happens if the preloader is already running when the cron fires again?
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.
How often should I run the preloader?
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.
Why do some URLs show different edge locations each run?
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.
Does this plugin work without proxies?
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.
Why does the Worker Status say “Not Responding”?
Your server sent a test request to the Worker and did not get a successful reply. The preloader will not run until this is fixed. The Worker Status card shows a short reason, and “View full error” opens the Logs tab with the technical details. After fixing the problem, click “Check again” in the card to re-check right away. Common causes:
- Secret mismatch (HTTP 401): the Worker’s secret no longer matches the one saved in the plugin, for example because another site on the same domain deployed over it. Disconnect and use Connect & Deploy again, or for a manual setup, copy the same secret into both the plugin and the Worker.
- Address could not be found, or URL not found (HTTP 404): the Worker URL is wrong, the Worker was deleted, its workers.dev route was turned off, or your workers.dev subdomain was renamed. Deploy the Worker again to get a fresh URL. If this is your account’s first Worker, the workers.dev subdomain can take several minutes to go live.
- Timed out: the Worker fetches your homepage before replying. If an uncached homepage takes longer than 10 seconds to load, the check gives up. Speed up the page or check your server.
- Could not connect or secure connection failed: your host is blocking outgoing requests to workers.dev, or its SSL libraries are outdated. Ask your host to allow outgoing HTTPS requests to *.workers.dev.
- Cloudflare error 1101: the Worker could not fetch your site, for example because of a redirect loop or an SSL error on your origin server.
- Cloudflare error 1027: your Cloudflare account has used up its daily Workers request limit. It resets daily, or you can upgrade your Workers plan.
Screenshots











Changelog
1.3.3 – 01.11.2026
- Improved: When the Worker is not responding, the Worker Status card now shows the reason (for example a secret mismatch, a timeout or a Cloudflare error code) with a link to the full error in the Logs tab
- Improved: The log now records the full technical error when the Worker check fails, including when the preloader stops because the Worker is not accessible, and logs when the Worker is responding again
- Added: “Check again” link in the Worker Status card to re-check a Worker that is not responding without waiting or reloading the page
1.3.2 – 26.10.2026
- Fixed: Worker reported URLs as “Already cached” after a cache purge without actually warming the edge cache. The log now shows the real edge cache status (HIT, MISS, etc.) for every URL
- Improved: Automatically deployed Workers are updated automatically. Manually deployed Workers show a notice when the Worker script needs to be updated
- Removed: Worst Coverage card from the Coverage tab. It ranked countries by number of misses, so it usually showed the busiest country rather than the one with the poorest coverage
1.3.1 – 13.09.2026
- Fixed: Exclusions tab pagination links pointed to admin-ajax.php on a fresh page visit instead of the settings page, so clicking to page 2 or beyond failed
1.3.0 – 11.09.2026
- Added: Cache Coverage report. See real visitor cache hit/miss rates by country from Cloudflare Analytics, with suggested Webshare proxy countries to improve coverage
- Improved: Exclusions tab now loads instantly instead of waiting on a live sitemap re-fetch every time
- Improved: Visual improvements on all tabs
1.2.0 – 16.08.2026
- Added: Optional automated Cloudflare Worker deployment.
- Improved: Admin bar shortcut
1.1.2 – 31.07.2026
- Fixed: Proxy count in the sidebar could get stuck showing “None” after saving a new proxy list URL because of a stale 24-hour cache; the count now updates immediately when the URL is saved and after each preload run
- Fixed: Last run duration always showed “minutes” (plural) even for a single minute, e.g. “1 minutes”
- Improved: Minor wording and clarity improvements to Settings and Exclusions tab descriptions
1.1.1 – 29.06.2026
- Fixed: Manually excluded URLs on the Exclusions tab were matched as substrings, causing similar URLs to be excluded unintentionally; manual exclusions now require an exact URL match
1.1.0 – 27.06.2026
- Added: New “Exclusions” tab that allows manual and keyword-based URL exclusions
- Added: Optional “Start Preload” shortcut in the WordPress admin bar to trigger a manual preload from any page
- Added: Auto-dismissing toast notifications confirm when the preload starts and completes
- Added: Live remaining URL count shown in the sidebar and next to the admin bar shortcut while a run is in progress
- Improved: Admin bar shortcut reflects the real running state immediately, whether the preload was started manually or via the scheduled cron
- Tested: Compatibility with WordPress 7.0
1.0.8 – 12.05.2026
- Updated: Screenshots, how to use guide, and donate plugin link. Thanks for feedback @masvil https://wordpress.org/support/users/masvil/
1.0.7 – 16.04.2026
- Fixed: Sitemap download timeout increased to 30 seconds to prevent cURL error 28 on slow servers
- Refactor: Code internals for better bompatibility with WordPress coding standards
1.0.6 – 11.03.2026
- Refactor: Converted plugin internals to class-based architecture for improved maintainability
- Improved: Overlapping run protection. If a cron event fires while a run is already in progress, it is automatically skipped
- Improved: Auto-refresh logs are now enabled by default on the Logs tab
- Added: Full proxy pass mode that sends every URL through every proxy for maximum Cloudflare edge coverage
- Added: New sidebar on the Settings page shows current mode, running or idle status, last run times, URL count and proxy count
1.0.5 – 16.02.2026
- Added: Extra intervals 3hrs, 6hrs, 12 hrs, and custom
- Added: Next scheduled run date/time display
1.0.4 – 25.12.2025
- Improved: HTTP request helper function to always send a clear User-Agent. Thanks for feedback @gregywordpress https://wordpress.org/support/users/gregywordpress/
- Improved: Preloader by increasing cursor time out to 24 hours to avoid incomplete batches
- Added: Delay between URLs setting to adjust wait time in seconds between each URL preload
- Added: Auto-refresh to log viewer
- Added: Stop preloader button to cancel the running preloading process
1.0.3 – 30.11.2025
- Improved: Log file security by migrating logs to super-preloader-for-cloudflare-log.php
- Added: Prefixes to global variables
- Tested: Compatibility with WordPress 6.9
1.0.2 – 20.10.2025
- Added: Manual setting of cron start time
1.0.1 – 27.07.2025
- Fixed: Removed deprecated load_plugin_textdomain() call
- Improved: Stats table styling and hover effects
- Added: Color coded tooltips for displaying edge locations on hover
- Added: Comprehensive statistics summary with cumulative and latest run metrics
1.0.0
- Initial release
