What Page Caching Is

Every time someone visits a WordPress page, the server normally runs PHP code and asks the database for the content, then builds the page from scratch. That takes time, and it gets slower as traffic grows.

Page caching saves a finished copy of each page the first time it’s built. The next visitor gets that ready-made copy straight away. Pages arrive faster, the server does less work, and your site copes better with busy periods.

Insight Bench for WordPress shows “No caching plugin is active” when it can’t find a caching plugin or a persistent object cache. That isn’t always a problem. Your host may already cache pages for you, so check that first.

Step 1: Check What Your Host Already Does

  • Managed WordPress hosts. Many managed hosts cache pages at the server level and add their own plugin or a “Purge cache” button in wp-admin. Some don’t allow other caching plugins at all. Search your host’s help pages for “caching” before you install anything.
  • Server-level caching. Hosts using LiteSpeed web servers, Nginx caching or Varnish can cache pages without a WordPress plugin. Your host’s control panel or support team can tell you whether it’s on.
  • Cloudflare and other CDNs. Cloudflare caches images, CSS and JavaScript by default, but not your HTML pages. Caching pages there needs Cloudflare’s Automatic Platform Optimization (APO) or a cache rule set up for it.

If your host already caches pages, you’re usually done. Skip to “Check It Works” to confirm.

Step 2: Choose One Caching Plugin

If nothing caches your pages yet, choose one plugin. Good, widely used options:

  • WP Super Cache (free). Simple and reliable. A good choice if you want few settings.
  • W3 Total Cache (free, with a paid version). Many settings. Powerful, but easier to misconfigure.
  • LiteSpeed Cache (free). Its page caching works only on LiteSpeed servers (or with the QUIC.cloud service). Use it if your host runs LiteSpeed.
  • WP Rocket (paid). Turns on page caching as soon as it’s activated, with sensible defaults.

Install it from Plugins → Add New Plugin, search for the name, click Install Now, then Activate.

Never run two page caches at once. That includes a plugin on top of your host’s caching. Deactivate and delete any old caching plugin before you add a new one.

Step 3: Turn On Page Caching

Take a backup first, or try it on a staging copy of your site if your host offers one. Then:

  • WP Super Cache: go to Settings → WP Super Cache, choose Caching On on the Easy tab, and click Update Status.
  • W3 Total Cache: go to Performance → General Settings, tick Enable under Page Cache, and save. Leave the other features off until page caching works well.
  • LiteSpeed Cache: go to LiteSpeed Cache → Cache and make sure Enable Cache is on.
  • WP Rocket: page caching starts when you activate it. Settings are under Settings → WP Rocket.

Start with page caching only. Extra features such as combining or delaying scripts can break menus, sliders and forms. Turn them on one at a time later, and test after each change.

Step 4: Exclude Pages That Must Stay Personal

Pages that show different content to each visitor must never be cached. On a shop, that means the cart, checkout and “My account” pages. On a membership or course site, it means members’ dashboards and account pages.

WooCommerce tells most caching plugins to skip its cart, checkout and account pages automatically, and the main plugins handle this well. Still, check your plugin’s “Never cache” or “Exclusions” setting and add the addresses of any custom account, booking or login pages.

Object Caching in Brief

Object caching (Redis or Memcached) is different from page caching. It keeps the results of database lookups in memory, which helps pages that can’t be cached, such as checkout pages and logged-in dashboards. It needs software on the server, so it’s usually something your host turns on, and then you connect it with a plugin such as Redis Object Cache. Small brochure sites rarely need it.

Check It Works

  1. Open your site in a private browser window (caching tools skip logged-in users).
  2. Load a page, then load it again. The second load should feel faster.
  3. Look at the response headers: right-click the page, choose Inspect, open the Network tab, reload, and click the first item (the page itself). Look for a header such as cf-cache-status: HIT, x-litespeed-cache: hit or an x-cache header showing a hit. Header names vary by host and plugin.
  4. Some plugins add a note at the bottom of the page source instead. Right-click, choose View page source and scroll to the end.

Then press Re-scan now in Insight Bench (or in the plugin) to confirm caching is detected.

Clear the Cache After Changes

A cached page doesn’t change until the cache is cleared. Most plugins clear a page when you update it, but changes to menus, widgets, theme settings or CSS often need a full clear. Look for Purge all, Delete cache or Clear cache in the admin bar or the plugin’s settings. If you also use a CDN, clear it there too.

Common Pitfalls

  • Testing while logged in and thinking caching doesn’t work.
  • Stacking caches, such as two plugins, or a plugin on a host that forbids them.
  • Turning on every option at once, then not knowing which one broke the site.
  • Caching the cart or checkout, so shoppers see someone else’s basket. Test an order after setup.