Speed & performance · Explainer
Page Cache vs Object Cache vs Browser Cache in WordPress
Short answer
Page cache stores finished HTML pages so the server can skip building them, object cache stores database results in memory so WordPress can skip asking the database, and browser cache stores files on the visitor's computer so repeat visits skip downloading them. Use all three, since each covers a gap the others leave.
Key takeaways
- Page cache stores finished HTML pages so the server can skip running WordPress for logged-out visitors.
- Object cache stores database results in memory so WordPress can skip asking the database again.
- Browser cache stores files on the visitor's computer so repeat visits skip downloading them again.
- WP Super Cache serves static HTML to 99% of visitors, meaning those not logged in and without comments.
- Clearing a cache deletes stored results, so the next visits rebuild them and run slower.
What is page cache in WordPress?
Page cache stores finished HTML pages so the server can send them without running WordPress again.
WP Super Cache generates static HTML files from a dynamic WordPress blog. After a file is generated, the web server serves that file instead of processing the heavier WordPress PHP scripts, according to its WordPress.org page.
Its page says 99% of visitors are served static HTML files: users who are not logged in, have not left a comment, and have not viewed a password-protected post.
One cached file can be served thousands of times, so a busy post costs the server almost nothing after the first visit builds it.
What is object cache in WordPress?
Object cache stores database results in memory so WordPress can reuse them instead of asking the database again.
By default the object cache lives in PHP memory for one request only and is emptied at the end of that request, according to the WP-CLI cache documentation on Developer.WordPress.org.
A persistent drop-in changes that. Placing an object-cache.php file in wp-content replaces the built-in cache class, as the WP_Object_Cache reference on Developer.WordPress.org explains, so cached objects survive between requests.
Transients use the same storage. The Transients API stores temporary data with an expiry, and with a persistent object cache the data lives in that cache instead of the database, according to the Transients API introduction on the Developer WordPress blog.
Redis and Memcached are the two common backends for a persistent object cache. Our Redis vs Memcached guide compares them for WordPress.
What is browser cache?
Browser cache is the copy of files a visitor's browser keeps, so repeat visits skip downloading them again.
MDN's HTTP caching guide splits caches into private and shared. A private cache belongs to one client, usually the browser, and can store personalised responses that a shared cache must not keep.
The server controls it with the Cache-Control header. MDN gives max-age=604800 as an example, which keeps a response fresh for 604,800 seconds, or 7 days. The full directive list is on the MDN Cache-Control page.
Browser cache helps repeat visitors, not first visits. A first-time visitor still downloads everything, so it never fixes a slow first load on its own.
How does each cache work?
Each cache stores a finished result at a different point, then reuses it until it expires or is cleared.
Page cache works at the front door. A visitor asks for a page, and if a static file exists the server sends it. If not, WordPress builds the page and saves a copy for the next visitor.
WP Super Cache serves files in three ways, ranked by speed. Expert uses Apache mod_rewrite to serve supercached files and bypasses PHP entirely.
Simple serves the file through PHP and is the recommended way. WP-Cache caching handles known users, URLs with parameters and feeds, according to the plugin page.
Object cache works at the database. WordPress asks for a result by key.
On a miss it queries the database and stores the result, and on a hit it reads memory. Keys live in groups, and the default group is called default, according to the WP_Object_Cache reference.
Browser cache works at the visitor's computer. The browser stores a file with its freshness lifetime. While fresh it reuses the file without asking, and when stale it revalidates with the server, which can answer 304 Not Modified with no body, as MDN explains.
The three layers stack. The browser asks first, then the page cache, then WordPress with its object cache.
How are the three caches different?
Page cache skips building the page, object cache makes building it cheaper, and browser cache skips downloading files twice.
| Cache | What it stores | Where it lives | Who it helps most | What clears it |
|---|---|---|---|---|
| Page cache | Finished HTML pages | Server, or a CDN | Logged-out visitors | Content changes |
| Object cache | Database results and objects | Redis or Memcached memory | Logged-in users, shops | Data changes, or a flush |
| Browser cache | Files such as CSS, JavaScript and images | Visitor's browser | Repeat visitors | max-age expires |
A page cache helps logged-out visitors most. An object cache helps logged-in users, shops and membership sites, where pages cannot be cached as static files. Browser cache helps anyone who returns.
Clearing differs too. Page cache clears when content changes, object cache clears on flush or when data changes, and browser cache clears when max-age expires or the visitor clears it by hand.
Some hosts cache pages at the server level instead of a plugin. Our WP Rocket vs host caching comparison explains the difference.
When should you use each one?
Use all three, since they solve different problems and work best together.
- Blog or brochure site: start with page cache, since it covers nearly all visitors.
- Shop or membership site: object cache matters most, since logged-in pages skip page cache.
- Any site: browser cache for CSS, JavaScript and images, with a long
max-ageon files that rarely change. MDN notes that you can use a largemax-agevalue for files that rarely or never change.
If you can only set up one, pick page cache for a mostly logged-out site and object cache for a mostly logged-in one.
On LiteSpeed hosting, the server cache may already cover page caching. Our guide on whether a cache plugin helps on LiteSpeed hosting explains when a plugin still helps.
What does each cache cost?
Browser cache is free, page cache plugins are often free, and object cache costs whatever the Redis server costs.
WP Super Cache is a free plugin on WordPress.org. The Redis Object Cache plugin is also free, but the Redis server behind it is usually paid.
Kinsta's documentation lists its Redis add-on at $100 per month per site as of November 2026. Other hosts bundle Redis into a plan, so the real cost depends on the host rather than on the plugin.
| Cache | Plugin cost | Server cost | Typical extra cost |
|---|---|---|---|
| Page cache | Free | Included in hosting | $0 |
| Object cache | Free plugin | $0 to $100 per month | Depends on the host |
| Browser cache | None | None | $0 |
Browser caching costs nothing extra. It runs on headers your server or caching plugin already sends.
How do you check caching on your site?
Load a page twice and check the response headers, the plugin status screens, and a speed test.
For page cache, open the Settings → WP Super Cache screen and confirm caching is on. The plugin page lists that settings screen in its troubleshooting steps. Then open the browser Network tab, reload the page, click the HTML document, and read the response headers for cache signs such as x-cache or age.
For object cache, open Settings → Redis and read the hit ratio, or check Query Monitor for the query count. A working cache shows hits rising as pages load.
For browser cache, reload the page in the Network tab and look for files served from disk cache or answered with a 304 status. MDN explains that a 304 answer means the server confirmed the stored copy is still good.
If a CDN sits in front of the site, its cache is a fourth layer. Our Cloudflare cache rules guide covers that layer.
What are the common myths about WordPress caching?
The common myths are that one cache replaces the others, that caching fixes slow hosting, and that clearing the cache speeds a site up.
- “Page cache alone is enough.” It skips building pages for logged-out visitors, but logged-in users still need the object cache and the database.
- “Object cache replaces page cache.” Object cache makes each request cheaper, while page cache avoids the request entirely. They do different jobs.
- “Clearing the cache makes a site faster.” Clearing deletes stored results, so the next visits rebuild them and run slower. Clear a cache to fix stale data, not to gain speed.
- “Browser cache helps first visits.” It only helps repeat visits, since a first-time visitor has nothing stored yet.
- “A cache fixes slow hosting.” A cache hides slow PHP on repeat visits, but the first build is still slow.
Even without headers, browsers guess. MDN calls this heuristic caching and says the spec suggests reusing a response for about 10% of the time since it last changed, so a file unchanged for a year may be reused for about five weeks.
Which cache should you pick for your site?
Pick page cache for a mostly logged-out site, object cache for a mostly logged-in site, and browser cache for every site.
| Situation | First pick | Second pick |
|---|---|---|
| Small blog | Page cache | Browser cache |
| Shop or membership site | Object cache | Page cache |
| News site with comments | Page cache | Object cache |
| Slow admin only | Object cache | Browser cache |
Most sites end up with all three, since each one covers a gap the others leave. Start with page cache, add browser cache headers, then add object cache when logged-in traffic grows.
Our guide to speeding up WordPress walks through setting up all three layers in order.
Frequently asked questions
Can I use object cache instead of page cache?
No. Page cache stores finished pages for logged-out visitors, while object cache stores database results that logged-in users and shops still need. They do different jobs, and most sites use both together with browser cache on top.
Does browser cache make my site faster?
Yes, in the sense that both make repeat visits faster. Browser cache stores files such as CSS, JavaScript and images on the visitor's computer, so only the first visit downloads them in full. Repeat visits reuse the stored files until max-age expires.
Will clearing all my caches speed up my site?
No. Clearing deletes stored results, so the next visits rebuild them and run slower. Clear a cache to fix stale content or a specific problem, not to gain speed. A cache earns its keep by staying warm.
Which cache should a small site set up first?
A page cache plugin such as WP Super Cache, which is free on WordPress.org, covers most small sites. For logged-in traffic, add a persistent object cache with the free Redis Object Cache plugin, plus a Redis server from your host.
How can I tell if caching is working on my site?
Open the Network tab in your browser's developer tools and reload the page. Cached pages often show cache headers such as x-cache or age, files served from disk cache show as cached, and stale files revalidated by the server answer with a 304 status.
Sources
- WP Super Cache WordPress.org
- wp cache – WP-CLI Command WordPress Developer Resources
- An introduction to the Transients API WordPress Developer Resources
- HTTP caching MDN
- Cache-Control header MDN
- WordPress Hosting Add-Ons Kinsta
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
