KakapoWP KakapoWP
Kakapo Performance

Page cache

Built once, then simply delivered.

On the first request WordPress assembles the page; after that it lies ready as a finished HTML file. For how long is up to you via the cache lifetime. Logged-in visitors and everything that does not come in via GET are left out.

All nine plugins included in the lifetime deal — every future one too.

Page cache

Static HTML file per page · cache lifetime (TTL) freely adjustable

ActiveSettings

What the page cache offers

One static HTML file per page
Cache lifetime (TTL) freely adjustable
Exclusion list for individual paths
Anonymous GET requests only

Here's how it works

1

The first visitor triggers the build

2

The result lands as an HTML file

3

The next visitors read the file

FAQ about the page cache

Do logged-in users see stale content?
No. Anyone logged in always gets the page fresh from WordPress. The cache only applies to anonymous GET requests.
What about cart, login or forms?
Anything that doesn't run via GET is never cached. Paths that should stay out anyway go into the exclusion list — checkout or customer account, for example.
How long does a page stay in the cache?
As long as you set the cache lifetime. Once it has expired, the next request rebuilds the page.

More Performance features

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