Someone told you to install a caching plugin. You did. You have no idea whether it is working, and you are slightly afraid to touch the settings in case something breaks.
Here is what caching actually is, without the vocabulary.
What WordPress does without a cache
Every time someone visits a page, WordPress builds that page from scratch. It runs PHP code, asks the database for your content, loads the theme, runs every active plugin, assembles the HTML and sends it over. That whole process happens again for the next visitor, and the one after that, even though the page has not changed.
It is like a restaurant where the chef starts from raw ingredients every time someone orders the same dish, even when there is an identical plate already made.
Caching saves the finished page. The next visitor gets the saved copy instantly, and the database and PHP never get involved. On a typical site that is the difference between a page taking two seconds and taking a couple of hundred milliseconds.
The four kinds of caching, in order of impact
Page caching. The big one. Saves the complete HTML of a page and serves it to the next visitor. This is what a caching plugin like WP Rocket, WP Fastest Cache, W3 Total Cache or LiteSpeed Cache primarily does, and it produces the biggest gain of anything on this list.
Browser caching. Tells a visitor's browser to keep your logo, CSS and fonts on their own device for a while, so their second page view does not re-download things that have not changed. Costs you nothing and helps everyone who visits more than one page.
Object caching. Stores the results of database queries in memory so WordPress does not ask the same question repeatedly. Matters most for sites that cannot use full page caching, like busy shops and membership sites. Usually needs support from your host.
CDN caching. Copies of your files stored on servers around the world, so a visitor in another country loads from somewhere nearby rather than from your one server.
Why your cache might be installed and doing nothing
This is more common than you would think. A caching plugin can sit there active, in the plugin list, achieving essentially nothing. A few reasons:
- You are logged in. Caching plugins deliberately skip the cache for logged-in users, so the admin sees live content. Which means the site you are testing is the uncached version. Check in a private window.
- Two caching plugins are fighting. Your host may already run server-level caching, and a plugin doing the same job on top of it can cause conflicts and strange behaviour.
- Something clears it constantly. If the cache is purged every time any content changes anywhere, a busy site can end up rebuilding pages endlessly.
- Pages are excluded. Carts, checkouts, account pages and anything personalised cannot be cached, and that is correct. But over-broad exclusion rules sometimes take half the site with them.
The fix: load a page in a private window, then load it again, and see whether the second load is noticeably faster. Most caching plugins also add a comment at the bottom of the HTML source confirming the page was served from cache.
Stale cache, the other failure mode
The opposite problem. You update a price, publish the change, look at the page and see the old price. Panic, then confusion, because it looks fine when you are logged in.
That is a stale cache serving the previous version to the public. It usually clears itself eventually, but "eventually" is not much comfort when the wrong price is live.
The fix: purge the cache after any meaningful content change. If your host runs its own caching layer as well as your plugin, you may have to purge both. This is exactly the kind of small chore that gets forgotten, which is why cache purging is part of routine maintenance on every Up Speed plan.
What caching will not fix
Worth being clear about this, because caching gets treated as a cure for everything.
It does not shrink your images. A cached page with a 4MB hero image is still a 4MB download. It does not remove third-party scripts, so your chat widget and tracking pixels still load. It does not help logged-in users, which matters a lot if you run a membership site or a shop. And it does not fix a bloated database, it just hides the symptom on pages that happen to be cached.
Caching is a genuine, large improvement layered on top of a site that is otherwise in reasonable shape. It is not a substitute for the shape.
Keeping it working, not just installed
Caching is set-and-forget until a plugin update, a theme change or a host migration quietly breaks it. Then it stays broken until someone thinks to check, which on most sites is never.
Cache purging and database maintenance are included on every Up Speed plan, starting at Starter, along with tested updates and monitoring. No dashboard, no settings screen to be nervous about. It is checked because checking it is the job.