Why caching matters
Every WordPress page gets rebuilt from scratch. The server queries the database, runs PHP, and assembles the HTML on every single visit.
Caching skips all that. It saves a finished copy and serves it directly, which is faster for the visitor and lighter on the server.
The difference is not cosmetic. According to Google's analysis of 11 million mobile landing pages across 213 countries, the chance of a visitor bouncing rises 123% as load time goes from 1 second to 10 seconds.
Caching is one of the most direct ways to keep a WordPress site on the fast end of that range.
+123%
Increase in the probability a mobile visitor bounces as page load time goes from 1 second to 10 seconds, according to Google's analysis of 11 million landing pages. Caching is one of the most direct ways to stay off the slow end of that curve.
The four caches on a WordPress site
- Browser cache. A visitor's own browser stores static files locally, so it does not re-download your CSS, images, and JavaScript next visit. This affects that one visitor only.
- Plugin cache. A plugin like WP Rocket, LiteSpeed Cache, W3 Total Cache, or WP Super Cache saves a static copy of your pages, so WordPress does not rebuild them from the database each time. This is usually the one showing visitors an old version after you make a change.
- Server-side cache. Some hosts run their own layer. Varnish and LiteSpeed Server are common. It sits in front of WordPress and caches pages before your plugin even runs.
- CDN cache. If you use a content delivery network, copies of your pages sit on servers worldwide, so each visitor loads from whichever is closest.
A stale page after an edit is almost always one of these four holding the old version. It rarely means anything is broken.
When you actually need to clear it
Clear the cache after you publish or edit content, change theme files or settings, or install a plugin that changes how the site looks or behaves.
You do not need to clear it for routine traffic. That is the whole point of having it.
Clearing more than you need just sends the server back to work rebuilding pages it already had ready.
How to clear each one
Browser cache. A hard refresh makes the browser ignore its local copy. Ctrl + F5 on Windows, Cmd + Shift + R on Mac.
Plugin cache. In WP Rocket, hover the "WP Rocket" item in the admin bar and click "Clear and preload cache." The same button sits under Settings > WP Rocket > Dashboard. In LiteSpeed Cache, hover the LiteSpeed icon and click "Purge All." Other plugins vary, but look for "Clear Cache" or "Purge," usually in the admin bar or the plugin's settings.
Server-side cache. If your host runs Varnish or a server-level LiteSpeed cache, clearing the plugin cache will not touch it. Look for a cache-purge option in your hosting control panel, or ask support to do it.
CDN cache. Log into your CDN dashboard and purge or invalidate there. This one is separate from everything above, and the easiest to forget.
Common questions
Why does my site still show the old version after I made changes?
It's not broken, it's cached. One of four layers is holding a finished copy of the old page: the visitor's browser, a caching plugin like WP Rocket or LiteSpeed Cache, a server-side cache like Varnish, or your CDN. The plugin cache is usually the one showing visitors an old version.
When do I actually need to clear the cache?
After you publish or edit content, change theme files or settings, or install a plugin that changes how the site looks or behaves. Not for routine traffic, since that's the whole point of having it. Clearing more than you need just sends the server back to rebuilding pages it already had ready.
How do I clear the plugin cache in WordPress?
In WP Rocket, hover the WP Rocket item in the admin bar and click Clear and preload cache. In LiteSpeed Cache, hover the LiteSpeed icon and click Purge All. Other plugins vary, but look for Clear Cache or Purge. A server-side cache from your host is separate, so check your hosting control panel too.
Does caching really affect my business?
Yes, measurably. Google's analysis of 11 million mobile landing pages found the chance of a visitor bouncing rises 123% as load time goes from 1 second to 10 seconds. Caching is one of the most direct ways to keep a WordPress site on the fast end of that range.
Does your homepage pass the three second test?
A visitor decides in about three seconds whether your site is for them. Put your address in and I will send you what a stranger actually takes from it, and the specific things to fix.
Scan my site free →Where to start
Not sure which cache is showing visitors an old version of your site? gravityGone handles WordPress setup and maintenance for small businesses across Jacksonville and Northeast Florida.
Mike is the founder of gravityGone, where he helps small businesses in Northeast Florida grow through Web Development, SEO, and Marketing Automation.
