Skip to content

Cache Warming

Automatically warm your cache after purge events so visitors always hit a warm cache.

How It Works

When a cache purge occurs (via Varnish HTTP Purge or similar), Cacheability Pro detects the event and queues affected URLs for warming. A background cron job processes the queue, making requests to each URL so the cache is populated before real visitors arrive.

URL Prioritization

URLs are warmed in priority order:

  1. Homepage - highest traffic, warm first
  2. Category/archive pages - high traffic landing pages
  3. Recent posts - fresh content visitors are likely to visit

Configuration

Settings are available under Cacheability Pro > Cache Warming:

  • Warming Delay - Milliseconds between warming requests (100-5000ms). Higher values reduce server load.
  • Batch Size - Number of URLs to warm per cron run (1-20).
  • Mobile Warming - Optionally warm mobile variants separately (useful if your cache varies by User-Agent).

Compression Variants

The warmer sends requests with both Accept-Encoding: gzip and Accept-Encoding: br headers to ensure both compressed variants are cached.

Integration with Varnish HTTP Purge

Cache warming works with the Varnish HTTP Purge plugin. When VHP purges URLs, Cacheability Pro automatically queues them for re-warming.