Cache Warmer
A fast cache only helps when the page is already in it. After a cache expires or is cleared, the next visitor may have to wait while WordPress builds the page again. Cache Warmer visits your pages ahead of time, giving your existing caching system the opportunity to prepare a cached response before
A fast cache only helps when the page is already in it.
After a cache expires or is cleared, the next visitor may have to wait while WordPress builds the page again. Cache Warmer visits your pages ahead of time, giving your existing caching system the opportunity to prepare a cached response before a customer, reader or campaign visitor arrives.
Choose the pages that matter, control the pace and see what happened. Start a warm-up when you need it, run it on a schedule, or queue published content after an edit.
Cache Warmer complements your caching setup. It does not create a page-cache engine or change which pages your cache considers eligible. It works by making HTTP requests that can populate a properly configured plugin, server or CDN cache.
New in 1.5: faster warming queues, clearer progress
Spend less time managing the queue and more time warming pages. Version 1.5 brings a substantial queue-processing performance improvement for large warm-up configurations. It avoids repeatedly sorting large configuration payloads and handles excluded URLs in bounded batches, while preserving queued work, recovery and configured HTTP visit limits.
In one production observation on a large WooCommerce store, warming worker executions dropped from roughly 100 seconds to 1–3 seconds after the update. This measures individual background-worker executions, not page-load speed or total crawl duration. Results vary with the queue, hosting, page response times and scheduler availability.
Progress reporting now shows completion timestamps, elapsed time that includes pauses, clearly labelled average visit speed and skipped totals on every log page.
Prepare important pages before the next visit
Warm your homepage, landing pages, articles and public product pages without manually opening them one by one. After a deployment or cache purge, start a run to help rebuild the cache for the pages you have selected.
This is especially useful when important pages receive too little regular traffic to stay warm on their own.
Warm the pages you choose
Build a focused crawl or cover more of your public site:
- Start from one or more URLs.
- Include public posts, pages, custom post types and taxonomy archives.
- Discover URLs through entry-point sitemaps.
