Understanding Caching on WordPress: A Beginner's Guide

WordPress is a powerful platform, but it builds every page from scratch on each visit by default - caching changes that, making your site faster and your server more efficient.

What caching is and why WordPress needs it

When a visitor loads a WordPress page, the server runs PHP code, queries the database, and assembles the HTML before sending it to the browser. On a quiet site this happens quickly, but under any real load it adds up fast.

Caching saves a ready-made copy of a page - or parts of it - so the server can hand that copy straight to the next visitor without repeating all that work. The result is faster page loads, lower server resource use, and a better experience for your visitors.

The main types of caching

A WordPress site can benefit from several layers of caching, each working at a different level.

Page caching (full-page caching) This is the most impactful type for most sites. The server saves a complete HTML copy of each page and serves it directly to visitors, bypassing PHP and the database entirely. Most caching plugins focus here first, and the gains are usually immediate and significant.

Browser caching Browser caching instructs your visitors' browsers to store static assets - images, CSS files, JavaScript - locally for a set period. On repeat visits, the browser loads those files from its own cache rather than downloading them again, which speeds up the experience noticeably.

Object caching WordPress makes a lot of database queries, and many of them return the same results on every request. Object caching stores those query results in memory so they can be reused without hitting the database again. Redis is the most common solution for this. On Kualo hosting, Redis object caching is available through the LiteSpeed Cache plugin, so you do not need a separate plugin to enable it. See how to integrate Redis into WordPress for the full setup steps.

OPcache (opcode caching) PHP has to compile your site's code into machine-readable instructions every time it runs. OPcache stores those compiled instructions so the server can skip the compilation step on subsequent requests. This happens entirely at the server level - you do not configure it yourself on shared hosting, and we manage it for you. For more context on how OPcache works, see What is OpCache and how can it be controlled?

Caching plugins: the landscape

Several well-regarded caching plugins exist for WordPress, and you may have come across names such as W3 Total Cache, WP Super Cache, WP Rocket, and Cache Enabler. Each takes a broadly similar approach: intercepting requests and serving cached output instead of running the full WordPress stack.

They all work, and some have large user bases. The important thing to know before you choose one is this: do not run more than one caching plugin at the same time. Stacking caching plugins causes conflicts, unpredictable behaviour, and can break your site. Pick one and stick with it.

Why LiteSpeed Cache is the best fit on Kualo

Almost every Kualo server runs the LiteSpeed web server. This matters because the LiteSpeed Cache plugin for WordPress is not just a PHP-level plugin - it communicates directly with the LiteSpeed web server itself.

That direct communication unlocks server-level full-page caching, which is faster and more efficient than anything a PHP-only plugin can achieve. Other plugins intercept requests after PHP has already started running; LiteSpeed Cache can serve cached pages before PHP is involved at all.

Public and private caching - and why it matters for complex sites

One area where many caching solutions fall short is handling sites where different visitors should see different content. A WooCommerce store is the clearest example: a visitor browsing your shop can be served a cached page just like anyone else, but the moment they add something to their cart, the experience becomes personal - their cart contents, their checkout, their account details. Serving a cached version of that to another visitor would be wrong.

LiteSpeed Cache handles this through a distinction between public cache and private cache. Public cache is used for pages that are the same for every visitor - your homepage, product listings, blog posts. Private cache is used for pages that are specific to a logged-in or active-session user, such as the cart, checkout, and account pages. LiteSpeed Cache manages this automatically, switching between the two as needed.

Many PHP-only caching plugins struggle here. They either cache everything and risk serving one visitor's cart to another, or they exclude logged-in users and active sessions from caching entirely - which means your busiest, most conversion-critical pages get no caching benefit at all. LiteSpeed Cache avoids both problems because the caching logic runs at the server level, where it has full visibility of what should and should not be cached for each request.

This makes LiteSpeed Cache a particularly strong fit for WooCommerce stores, membership sites, and any WordPress site where visitors log in or interact with personalised content. You can read more about how this works in our article on public cache vs. private cache.

Beyond page caching, LiteSpeed Cache also handles image optimisation, CSS and JavaScript minification, lazy loading, and Redis object caching - all from a single plugin. That breadth means you are less likely to need additional plugins for performance tasks.

Other plugins will work on Kualo hosting, but they cannot access the server-level cache that LiteSpeed Cache uses. If you want the best performance from your Kualo hosting, LiteSpeed Cache is the natural starting point.

You can read more about what the plugin does in our introduction to LiteSpeed Cache.

CDNs and how they relate to caching

A content delivery network (CDN) is a network of servers spread across different locations around the world. When a visitor loads your site, a CDN serves static assets - images, CSS, JavaScript - from whichever server is geographically closest to them, reducing the distance data has to travel.

A CDN complements caching rather than replacing it. Your caching plugin speeds up page delivery from your hosting server; a CDN reduces the load time of static files for visitors who are far from that server. The two work well together.

LiteSpeed Cache includes built-in CDN integration options, so you can configure this from within the same plugin once your caching is set up.

Where to go next

This article is an introduction to the concepts. When you are ready to set up caching on your site, our in-depth guide walks you through every step: Configuring LiteSpeed Cache with WordPress.

For broader performance advice - covering PHP settings, database optimisation, images, and more - see Optimising your website.

If you have any questions about which plan includes Redis or need help getting started, raise a support ticket and our team will be happy to help.