Page caching means we keep a finished copy of your page and hand it straight to the next visitor, without waking up PHP or the database at all. It is the single biggest speed win a website can get, and it is on for every plan.
Who gets the cached page
Anonymous visitors. Someone reading your blog or browsing your products who is not logged in and has nothing in their cart gets the cached copy, which is served in a few milliseconds.
Logged-in users, people with a cart, and anyone at checkout do not. Their page is built fresh, because it is personal to them. That is correct, and it is why the Redis object cache matters as well. See Redis object cache explained.
What is not cached
- The WordPress admin
- Checkout, cart and account pages
- Anything with a session
- Form submissions and other POST requests
You do not need to configure any of that. It is handled.
When you publish something new
The cache is cleared automatically for the pages affected when you publish or update content. If you have made a change outside the normal publishing flow, for example editing a theme file or changing a plugin setting, clear the cache manually.
Clearing the cache
Open the site in your panel and choose Clear cache. It takes seconds and it is completely safe. The worst that happens is the next few visitors get a freshly built page.
Caching plugins
You do not need one. Page caching happens before your site is even reached, which is faster than any plugin can be. If you already have a caching plugin and pages are behaving strangely, disable it and clear our cache.
"I cleared the cache and still see the old page"
Check in a private browsing window. Browsers cache too, and so does the network in between. If it is right in a private window, your own browser is holding the old copy.
The assistant in your control panel can see your actual account and answer about your sites, your plan and your usage. For anything else, email [email protected] and a person will answer.