A page that falls out of cache is built from scratch for the next visitor. On a WooCommerce store that visitor waits seconds instead of milliseconds.<\/p>\n\n
Uruz Cache Warmer reads your sitemap, builds a queue of public URLs and visits them in the background, so pages are already cached by the time somebody asks for them.<\/p>\n\n
Every request goes to your own site. A URL on any other host is dropped before it is fetched, and the plugin contacts no third-party service.<\/p>\n\n
The mobile bucket<\/strong><\/p>\n\n LiteSpeed, and most CDNs, keep a separate cache copy for mobile devices: the response carries This plugin warms both and reports them in separate columns, so a bucket that is not being filled is visible at a glance.<\/p>\n\n What it does<\/strong><\/p>\n\n No paid tier<\/strong><\/p>\n\n Every feature listed above is in this plugin. There is no URL limit, no locked screen and no upsell.<\/p>\n\n\n No. A small batch per run, a delay between requests, a 45-second ceiling per run, and adaptive pacing that backs off when the site slows down or the machine is under load. All of these are settings.<\/p><\/dd>\n WP-Cron only fires when somebody visits, which a quiet site rarely has at night. Add a real cron entry at your host calling Yes, if your cache serves separate mobile copies, which LiteSpeed and most CDNs do. It doubles the requests per cycle, and the first cycle after you enable it is slow, because every mobile page is built from scratch.<\/p><\/dd>\n Your site is serving one PHP request at a time. The warm requests queue up behind the admin request that started them, and neither can finish. It shows up on dev servers and on a php-fpm pool sized to a single worker.<\/p>\n\n Let the background worker do the warming instead, or raise the number of PHP workers. On normal hosting this does not happen.<\/p><\/dd>\n Only a real MISS. Bypass and no-cache are decisions your stack made on purpose, and unknown means no cache header could be read, so neither counts as cold.<\/p><\/dd>\n It runs one batch and nothing else, and only when the request carries the random key generated on your site. A wrong key gets a 403, and you can replace the key from Settings at any time. A cron entry cannot send a login or a nonce, so the key is the credential.<\/p><\/dd>\n Yes, and the plugin reads vary: User-Agent<\/code> and the classification rules live in .htaccess<\/code> or in the CDN. A warmer that sends only a desktop user agent leaves the mobile copy cold, and that is where most store traffic lands.<\/p>\n\n\n
urlset<\/code>. With no readable sitemap it walks your published content instead.<\/li>\nwp brl-scw run<\/code>, rebuild<\/code>, warm <url><\/code>, status<\/code>, reset<\/code>.<\/li>\nDNT: 1<\/code>, so the traffic can be filtered out of logs and server-side analytics.<\/li>\n<\/ul>\n\n\n
wp-content\/plugins\/<\/code>, or install the ZIP from Plugins > Add New.<\/li>\n\n
Does it hammer my server?<\/h3><\/dt>\n
Why are URLs never warmed on my low-traffic site?<\/h3><\/dt>\n
wp brl-scw run<\/code>, or hitting wp-cron.php<\/code>.<\/p><\/dd>\nShould I turn on the mobile pass?<\/h3><\/dt>\n
The admin page hangs when I press \"Run one batch now\"<\/h3><\/dt>\n
What counts as \"cold\"?<\/h3><\/dt>\n
Is the cron URL safe to leave on the site?<\/h3><\/dt>\n
Can I use it with Cloudflare HTML caching?<\/h3><\/dt>\n
cf-cache-status<\/code>. If you also run LiteSpeed, keep one purge strategy rather than two.<\/p><\/dd>\n\n<\/dl>\n\n\n1.2.4<\/h4>\n\n
\n
uruz-cache-warmer<\/code>.<\/li>\n<\/ul>\n\n1.2.3<\/h4>\n\n
\n
admin.php?page=brl-scw-cache-warmer<\/code>, and the WP-CLI command is now wp brl-scw<\/code>. The old command name still works.<\/li>\n1.2.2<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n