Warmer – Cache Warmer and Cache Preload Crawler

Cache warming means proactively visiting selected URLs so your cache layer can generate cached pages before real visitors request them.

No. Warmer is not a page caching plugin. It works alongside your existing cache plugin, server cache, reverse proxy cache, or CDN cache by visiting URLs that should be cached.

Many caching systems build cache only after a page is visited. After cache expires or gets purged, the first visitor may experience a slower uncached request. Warmer helps prebuild those cached pages in the background.

Warmer is cache-plugin agnostic and works with caching systems that generate cache when a URL is visited. This includes common setups such as LiteSpeed Cache, WP Rocket, W3 Total Cache, WP Super Cache, NGINX FastCGI cache, Varnish, and compatible CDN/page cache layers.

Warmer can warm public, cacheable WooCommerce pages such as product pages and product category pages when custom post type support is enabled. Dynamic pages such as cart, checkout, and account pages should usually stay excluded from full-page cache and should not be warmed.

Yes. You can choose the URL sources that Warmer should include, such as posts, pages, category archives, tag archives, media attachment pages, archives, and supported custom post types.

Choose a schedule that matches your cache expiration, publishing frequency, and hosting capacity. For many sites, a daily or twice-daily schedule is a safe starting point. High-change sites may need more frequent warming.

Warmer is designed to run in the background with configurable request delays and timeouts. Start with conservative settings, monitor server load, then adjust based on your hosting environment.

Yes. Warmer includes manual controls so you can start or stop cache warming from the WordPress admin.

Yes. Warmer includes WP-CLI and webhook support for developer workflows, deployment pipelines, and maintenance routines.

Warmer includes crawl status, success and failure statistics, downloadable logs, clear log history, source testing, schedule status, and diagnostics.

Check the logs and diagnostics first. Failed URLs may be blocked, redirected, protected, timing out, returning errors, or excluded from caching by your cache plugin or hosting configuration.

Not always. Start with important public pages such as the home page, landing pages, posts, pages, product pages, and category archives. Avoid private, dynamic, or non-cacheable pages.

Warmer can help reduce cold-cache delays by making sure cached pages exist before visitors arrive. It does not replace good hosting, clean code, image optimization, script optimization, or a proper caching setup.

For free plugin support, use the WordPress.org support forum. For premium support, use the support channel provided with your premium license.