KakapoWP KakapoWP
Log in Get Lifetime
Kakapo Performance

Cache warming

The server makes the first request itself.

The kakapo collects the URLs from your sitemap or from the most recently changed content and fetches them in the background until the cache is filled. A preview shows beforehand how many URLs are left and what gets skipped; nothing is changed in the process. The run works through the list in steps of 5 URLs each and can be aborted at any time. Whether your server reaches itself over HTTP is checked before the start.

Get lifetime — €149All Performance features
All nine plugins included in the lifetime deal — every future one too.

Cache warming

URLs from the sitemap or recently changed content · 5 per step, stop any time

RunningCancel

What cache warming offers

The preview counts up front without changing anything
Source: sitemap or most recently changed content
1 to 20 addresses per step, stop after 20 seconds
Success is verified against the cache file, not the HTTP code
Log of the last 40 requests with code and duration
Optionally after clearing the cache or on a schedule

Here's how it works

1

Test the self-call

2

Check the queue

3

Start the run and watch the count

FAQ about cache warming

Does this make my site faster?
Building a page takes exactly as long as before — it is merely moved forward in time. The server does this work in advance, and the visitor then only reads the finished file. For pages that are already sitting fresh in the cache, a run brings nothing; the preview shows them to you beforehand as skipped.
My server can't reach itself — what then?
Then cache warming is not possible here, and it says so plainly. Typical reasons are an upstream access barrier such as basic auth or a firewall, a DNS name that points somewhere else from the inside, or just a single PHP worker. The self-call test fetches the front page and reports status code and response time; if it fails, you cannot trigger a run.
Does cache warming keep running if I close the tab?
As long as the admin page is open, the browser drives the steps. After that WP-Cron takes over: the next visitor triggers the next step in a separate request and does not wait for it. If DISABLE_WP_CRON is set, things only continue when a real cron on the server calls wp-cron.php.

More Performance features

Page cache →Cron & Heartbeat →Browser cache →
Ready?

Performance — pay once, use forever.

All nine plugins for €149 once instead of €13 a month. Secure payment via Stripe. For the first 14 days: problem fixed or money back.

Get lifetime — €149