Seite nicht gefunden

What preloading 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

Test the self-call

Check the queue

Start the run and watch the count

FAQ about preloading

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 preloading 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 preloading 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.

Preloading

Preloading

What preloading offers

Here's how it works

FAQ about preloading

More performance features

Try Performance free for 24 hours.