HostCrafter ›Knowledge Base ›Performance & Caching ›WordPress Caching: How It Works Here, and Which Plugins to Use

WordPress Caching: How It Works Here, and Which Plugins to Use

Last updated September 10, 2026

A page cache is the single biggest thing you can do for how fast your WordPress site is and how much traffic it can take. This page covers what it does, which plugins are good on our servers, and how to get one running.

What it does
Serves pages without running WordPress
Good choices here
LiteSpeed Cache, W3 Total Cache, WP Rocket
Cost
Free, unless you want WP Rocket
The one rule
Run one page cache, not two

What a page cache actually does

Without one, every visitor makes WordPress start up, run your theme and plugins, ask the database for your posts, and build the page from scratch. Everyone gets the same page, and the server does the same work again for each of them.

A page cache keeps the finished page and hands the next visitor that copy instead. The page comes back sooner, and your site copes with far more visitors at once, because most of them never make WordPress run at all.

The best cache plugin is a well-configured one you are not fighting. The popular plugins are much closer together than the comparisons suggest, and the difference between “cached” and “not cached” is enormous next to the difference between any two of them. Get caching on, leave it on, and spend the time you saved on your images instead.

Which plugin to use

Any of these is a sound choice here. Pick one and stay with it.

Plugin Cost Notes
LiteSpeed Cache Free Built for the kind of server we run, so it takes the fastest route available here. This is the one offered when you add a website.
W3 Total Cache Free Very capable and highly configurable. More settings than most people need, which is a strength once you want them.
WP Rocket Paid The friendliest interface of the three, with sensible defaults out of the box. A good choice if you already own a licence.
WP Super Cache Free Simple and long-established. A fine option if you want something with very few settings.

Others work too. If a plugin you like is not on this list it is almost certainly fine here; open a ticket if you would like us to look at it with you.

Why the choice makes any difference

Our web server can serve a cached page itself, before WordPress is involved at all. Plugins written to use that get the fastest path available here. Plugins that keep their cache in their own folder still work perfectly well and are still a large improvement on no cache; they just do a little more of the work in PHP.

Both approaches are fully supported. Neither is blocked, throttled or discouraged.

Getting one on your site

When you add a website, the dialog offers to set LiteSpeed Cache up for you, already configured. Most people leave that ticked and never think about caching again. If you would rather choose your own, untick it and install whatever you like from Plugins in wp-admin, exactly as you would any other plugin.

Either way you can change your mind later. If a cache plugin is already on the site, one rule matters more than which one you pick:

Run one page cache plugin, never two. Two caches serving the same site is how a visitor gets a page that should not exist, and neither plugin can tell you which of them answered. Deactivate the one that is there before you activate the new one.
  1. Deactivate the cache plugin already on the site

    From Plugins in wp-admin, as you would any other.

  2. Install and activate the one you want

    Then go through its setup once. Most of them have a guided first run.

  3. Check a page while signed out

    Open your site in a private window and load a page twice. Most cache plugins will tell you in their own dashboard that the page was served from cache.

One thing to expect afterwards: our Clear cache button may report that there was nothing for it to clear. That is truthful rather than a fault. A plugin that stores its pages in your own site folder is cleared from inside that plugin, and it will have its own button for it.

What about an object cache?

Different job, and probably not the one you have. A page cache answers a visitor without starting WordPress; an object cache speeds WordPress up once it has started. On a blog or a brochure site nearly every visitor is served by the page cache, so the object cache has little left to do.

It earns its keep on carts, checkouts and logged-in visitors, which are exactly the pages a page cache must not serve. See Redis Object Cache: When to Turn It On.

Questions

Which one should I pick if I have no preference?

LiteSpeed Cache. It is free, it suits the server, and the Add Website dialog will set it up for you, so there is nothing to configure.

Can I use a different one, or none?

Of course. Untick the box when you add the website, or swap the plugin later from wp-admin like any other.

Can I run two cache plugins for extra speed?

No. Run one. Two page caches produce stale and mismatched pages.

Is a paid plugin faster than a free one?

Not in any way most sites would notice. You are usually paying for the interface, the support and the extras around the cache rather than for the cached page itself.

Why is my site still slow with caching on?

Usually because the slow pages are the ones a cache must skip: a cart, a checkout, a search, or anything a logged-in visitor sees. Large images and scripts loaded from other companies’ servers are the next most common cause.

Will you help me set up a different plugin?

Yes. Open a ticket with the plugin you want and we will make sure nothing else is caching alongside it.

Did this answer your question?

If not, send us the site and what you were doing and we will look at the server itself.

Open a ticket Back to the knowledge base