A site that stays slow despite installing a caching plugin often disappoints its owner, who thought the problem was solved with one click. The most common reason is simple to understand once explained: several types of cache exist, each solving a different performance problem, and a plugin handling one of them has no effect on the other two.

Page cache, the best known one

Page cache stores the final rendered HTML of a page for anonymous visitors, avoiding rebuilding that page on every visit by querying the database and running the corresponding PHP code. On WordPress, plugins such as WP Rocket, LiteSpeed Cache or WP Super Cache handle this type of cache. Its effect is dramatic on a showcase site or a blog, where most traffic comes from logged out visitors all seeing the same version of a page. Its limitation is just as clear: it has no effect on logged in visitors, the admin area, or REST API calls, since this content is by nature dynamically generated and specific to each user.

Object cache, often overlooked

WordPress commonly runs anywhere from a few dozen to several hundred database queries on every page load, most of them repeatedly looking up the same information, such as site settings or a user's metadata. Object cache stores the results of these queries in memory, through a system such as Redis or Memcached installed at the server level, to avoid recalculating them every time. This type of cache becomes decisive for a site with many logged in visitors, a client area, or a WooCommerce shop, since these are precisely the situations where page cache can do nothing. Unlike page cache, object cache requires server level installation, which explains why many shared hosting providers do not offer it by default, while most WordPress oriented managed hosts include it in their plans.

Browser cache, the simplest to set up

Browser cache works differently from the two above: it tells the visitor's browser to keep certain files, such as images, stylesheets or JavaScript scripts, stored locally for a defined period, avoiding re-downloading them on every new page viewed on the same site. This is configured through HTTP headers called Cache-Control, usually set at the web server level or through a performance plugin. Its benefit is felt mainly when a single visitor navigates between several pages of the site, rather than on a very first visit.

The complementary role of a CDN

A content delivery network, or CDN, distributes a copy of the site's static files across geographically spread servers, to reduce the distance data travels between the origin server and the visitor. For a small business whose customer base stays mostly local, this benefit remains modest. For a site with an audience spread across France, Italy and other countries, as is often the case for a multilingual site targeting Nice, Cannes and Monaco, a CDN such as Cloudflare, available with a free tier suited to most sites, noticeably reduces loading times for visitors farthest from the server.

How to know which one your site is actually missing

A site made up mostly of pages viewed by anonymous visitors, such as a blog or showcase site, benefits primarily from a properly configured page cache. A site with a client area, a booking system, or an active online shop, benefits more from object cache, often invisible in standard page speed measurement tools since its effect concerns content that is not cacheable by nature. An admin dashboard that loads slowly while the public site seems fast is a fairly reliable sign that object cache would make a noticeable difference.

Avoiding plugins that step on each other

Installing several page caching plugins at the same time can create conflicts, each trying to manage the same caching mechanism its own way. Good practice is to choose a single page caching plugin, enable object cache separately if hosting allows it, and check after each configuration change that the site keeps reflecting content updates without excessive delay, a common issue when cache is not properly cleared after a change.

Points to verify before publishing: confirm that the page caching plugin examples mentioned (WP Rocket, LiteSpeed Cache, WP Super Cache) remain commonly used references at the time of publication, and check that the description of how Redis and Memcached work for object caching still matches standard WordPress hosting practices.