Caching explained

Caching is one of the most effective ways to speed up a website. It is also one of the most misunderstood. This guide explains exactly what it is, how it works, and when it can cause problems.

What caching is

Every time a visitor loads a page on your site, your server has to do work:

1. Look up the page in the database
2. Fetch all the content (text, images, settings)
3. Run any plugins or logic
4. Assemble the final HTML page
5. Send it to the visitor

This can take a fraction of a second — or several seconds, depending on how complex your site is.

Caching skips most of this work. The first time someone visits a page, the server builds it as normal — and then saves a "snapshot" of the finished result. The next time someone visits, the server just sends that saved snapshot. No database lookup, no assembly. Fast.

"A cached page can load ten times faster than an uncached one."

Types of caching

There are several layers where caching can happen. You do not need to manage all of them — but it helps to know they exist.

Browser caching

Your browser (Chrome, Safari, etc.) caches files from websites you visit — images, stylesheets, fonts. When you visit the same site again, your browser loads the cached copies from your own computer instead of downloading them again.

This is why sites feel faster on your second visit. It is mostly automatic.

Server-side caching (page caching)

This is the most impactful type for WordPress sites. A plugin or hosting tool saves a complete HTML copy of each page. When the next visitor arrives, they get the cached copy without any database work.

WordPress caching plugins include WP Rocket, LiteSpeed Cache, W3 Total Cache, and others. Many managed WordPress hosts (like Flywheel, WP Engine, and Kinsta) also include built-in server-side caching.

CDN caching

A CDN (Content Delivery Network) stores copies of your pages and files in data centers around the world. Visitors get content from the server closest to them, reducing travel time.

Object caching

Object caching (using tools like Redis or Memcached) stores the results of database queries so they do not need to be repeated. This is mostly handled by your hosting provider on managed plans.

The tradeoff: freshness vs. speed

Here is the honest part. Caching is powerful — but it comes with one important implication.

When you update your site, visitors may not see the change immediately. They might see the cached (old) version for a few minutes — or longer, depending on how the cache is configured.

This is rarely a big problem in practice, because:

• Most caching tools clear (or "purge") the cache automatically when you make an edit
• The window of inconsistency is usually short (minutes, not hours)
• Most visitors are not watching for the exact moment you publish

But if you notice that your changes are not showing up after saving, cached content is often the reason.

Caching and logged-in users

Most caching setups do not serve cached pages to logged-in users. If you are logged in to WordPress, you are usually seeing the live, uncached version of your site — which is why you always see your changes right away, but a regular visitor might not.

If someone says "I can't see the update," the first question is: are they logged in?

Common questions

Related guides

• What slows websites down
• How a CDN speeds up your site
• How hosting affects speed
• My changes aren't showing up
• Caching on WP Engine

Learn more

• The HTTP cache — web.dev
• Caching best practices — web.dev