Super Preloader for Cloudflare

01 / SOURCE DETAILS

About this tool

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 What is Cloudflare Edge? Why you should set up Super Page Cache first Why a Cloudflare Worker is needed to preload cache Deploy Cloudflare Worker using API Token How to register and use Webshare Proxies Usage Notes and Key Considerations

02 / SOURCE DETAILS

Getting started

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.

03 / SOURCE DETAILS

Frequently asked questions

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.

Explore related topics