What Is Cache?
In computing, a cache (pronounced "cash") is a high-speed data storage layer that holds a subset of data, typically transient in nature, so that future requests for that data can be served faster than by accessing the data's primary storage location. On the web, caching operates at multiple layers and serves the shared goal of reducing the time and resources required to deliver content to visitors.
The most common types of web caching are browser (or client-side) caching, server-side caching, and CDN caching. Browser caching stores static assets like images, fonts, stylesheets, and scripts on the visitor's device after their first visit. When they return to the same page or navigate to another page on your site, these assets are loaded from local storage rather than fetched again from the server, making subsequent page loads significantly faster. This is controlled through HTTP headers like Cache-Control and Expires.
Server-side caching stores pre-built HTML pages or database query results in memory (using tools like Redis or Memcached) so that WordPress or another CMS does not need to re-process each page request from scratch. This is particularly impactful for South African WordPress sites on shared hosting, where database query time is often the primary bottleneck. A full-page cache plugin like WP Rocket or LiteSpeed Cache can reduce server response times from over a second to under 100 milliseconds on the same hardware.
Object caching is a subset of server-side caching that stores the results of specific database queries or computations in memory, so repeated identical queries do not hit the database. This is most beneficial for high-traffic sites with dynamic content, such as e-commerce stores, news portals, and membership sites. CDN caching, covered in more detail in the CDN glossary entry, stores static assets and sometimes full HTML pages at edge nodes positioned geographically close to visitors.
Cache In Practice
A Pretoria-based news portal was experiencing slow page loads during peak traffic, typically between 06:00 and 09:00 SAST when commuters checked headlines. Their server was regenerating every page from the database on each request. After implementing full-page caching with a one-hour expiry, the server only regenerated each article page once per hour rather than thousands of times. This reduced server CPU load by roughly 70% and cut average page load time from 3.8 seconds to under 0.9 seconds, measurably improving both user engagement and Core Web Vitals scores.
Cache invalidation, the process of clearing outdated cached content when you publish updates, is the most common operational challenge with caching. Most caching plugins handle this automatically when you publish or update a post, but problems arise when changes to shared elements like menus, sidebars, or widgets are not propagated. Understanding your caching setup and knowing how to manually purge the cache is an essential skill for any South African web developer or digital marketer managing WordPress sites.
FAQ
Why should I clear my cache when testing website changes?
When you make changes to your website, your browser or a CDN may still serve the old cached version. Clearing the cache forces a fresh request to the server so you see the updated content. For South African agencies managing client sites, always clear both the server cache and the browser cache when verifying changes after a deployment.
What is the difference between server-side cache and browser cache?
Server-side caching stores pre-built page responses on the server so it does not have to re-process each request. Browser caching stores assets like images and stylesheets locally on the visitor's device. Both types work together to speed up page loads but are controlled differently and serve different roles in the content delivery chain.