Caching on Kinsta

Kinsta includes a powerful server-level caching system that makes your WordPress site load fast for every visitor. It's built in, requires no plugins, and can be cleared with one click when needed.

How Kinsta caching works

Kinsta uses a full-page cache built into its server infrastructure using Nginx and Redis (a fast in-memory data store). When a visitor loads a page:

1. Kinsta checks if a cached version exists.
2. If yes, it serves the cached page instantly — no PHP or database processing needed.
3. If no, it builds the page, serves it to the visitor, and caches it for next time.

This means the first visitor to a page after a cache clear triggers a fresh build; every visitor after that gets the fast cached version.

What Kinsta caches

Kinsta's cache applies to:

• Standard public-facing pages and posts
• Archives (like blog post lists and category pages)

Kinsta's caching is intelligent — it automatically bypasses the cache for:

• Logged-in users
• WooCommerce cart and checkout pages
• Pages with active form sessions
• Any page with certain cookies set

This means your experience as a logged-in site editor may differ from what a visitor sees. Always check your site in a private/incognito browser window to see the cached visitor experience.

Checking your cache performance

MyKinsta's Analytics section includes a Cache hit ratio — the percentage of requests served from cache. A higher ratio means better performance. A ratio above 80% is generally healthy for a business site.

Clearing the cache in MyKinsta

When you make significant changes to your site and want visitors to see them immediately:

Clearing the cache from WordPress

Kinsta's WordPress plugin (usually called "Kinsta MU Plugin" or accessible via the admin bar) provides a cache-clear button directly in WordPress:

Common questions

Related guides

• The MyKinsta dashboard explained
• Caching on WP Engine
• What is a CDN?
• My changes aren't showing up
• Hosting & speed

Learn more

• Kinsta: caching documentation