🔧 Flat-price WordPress fixes from $69 — start with a free diagnosis, no card. Get a free diagnosis →

Performance

WordPress Caching Explained: Which Layer Is Stale?

Nov 17, 2026 · 8 min read · By the Mend engineering team

If WordPress is showing old content, odd layout issues, or changes that “won’t stick,” the problem is often not one cache but several layers caching different things. The fix is to identify which layer is stale: page cache, object cache, browser cache, or CDN cache.

That matters because clearing the wrong cache can waste time without solving anything. In some cases, the site is fine and only one layer needs to be flushed; in others, a plugin, host setting, or CDN rule is serving the wrong version of the page.

What “caching” means in WordPress

Caching is simply storing a copy of something so it can load faster next time. In WordPress, that can happen in multiple places, and each layer stores a different kind of data.

Think of it like this: your server may cache a full page, WordPress may cache database results, your browser may cache images and CSS, and a CDN may cache assets or even whole pages at the edge. When one layer gets out of sync, you can see a mix of old and new content.

The four caches that matter most

1. Page cache

Page caching stores a complete HTML copy of a page so the server does not have to rebuild it for every visitor. This is usually the biggest performance win and is often handled by a caching plugin or your host.

Common symptoms of page cache problems include:

  • Homepage updates not appearing for some visitors
  • Old text, prices, or announcements staying visible after you edit them
  • One page updating while another stays stale

Page caching can also be tricky on sites with logged-in users, membership content, or dynamic blocks like cart totals and personalized messages.

2. Object cache

Object caching stores the results of expensive database queries so WordPress does not have to ask the database for the same information again and again. It is often powered by Redis or Memcached, depending on your host or setup.

Object cache problems usually do not show as obviously “old pages.” Instead, you may see:

  • Admin screens loading slowly
  • Widgets, menus, or counts not updating correctly
  • Content appearing inconsistent between different parts of the site

Object cache is very useful, but if it is misconfigured or not cleared at the right time, it can keep serving outdated data.

3. Browser cache

The browser cache lives on the visitor’s device. It stores files such as images, CSS, JavaScript, and sometimes fonts so the page loads faster on repeat visits.

Browser caching is usually not the cause when only you see the problem on your own computer, while everyone else sees the correct version. That said, it can absolutely make a change seem broken when the server is actually fine.

Typical browser cache signs include:

  • Your edits show on one device but not another
  • The layout looks broken until you do a hard refresh
  • New images or logos seem missing even after upload

4. CDN cache

A CDN, or content delivery network, caches files or pages on servers closer to your visitors. It reduces latency and can absorb traffic spikes, but it adds another layer where stale content can live.

If you use a CDN, the site may still appear old even after you clear WordPress cache and your browser cache. In that case, the CDN may need a purge, or the caching rule may be too aggressive for a section of the site that changes often.

Why WordPress caching gets confusing

The main problem is that these layers can overlap. You might clear the plugin cache, but the host’s page cache and the CDN cache still serve the old version. Or you may update a file, but the browser still has an old CSS file stored locally.

Another common issue is that people try to “fix performance” by turning on more caching without understanding what each layer is doing. That can help a fast site get faster, but it can also make debugging harder when something changes and does not appear right away.

How to tell which cache is stale

Start with the simplest checks before changing settings. If you are about to adjust anything on a live site, take a backup first.

  1. Check the site in an incognito or private window. If the problem disappears, your browser cache may be part of it.
  2. Check on another device or network. If others see the correct version, the issue may be local to your browser or network.
  3. Clear the WordPress cache plugin. If you use a caching plugin, purge its cache and test again.
  4. Check host-level caching. Many managed hosts include server caching you can flush from their dashboard.
  5. Purge the CDN. If you use Cloudflare or another CDN, clear its cache too.
  6. Test a hard refresh. On desktop browsers, a hard refresh often forces fresh CSS and JavaScript to load.

If you still see the issue after clearing all layers, the problem may not be cache at all. A plugin conflict, a failed deploy, a bad rewrite rule, or a broken asset path can look like a caching issue at first glance.

Safe ways to clear cache without breaking the site

Clearing cache is usually safe, but the safest approach is to change one thing at a time so you know what actually fixed it.

  • Back up first. Even though cache purges are low risk, a backup protects you if you discover a deeper issue during testing.
  • Clear the cache layer closest to the problem first. If the problem is only visible in your browser, start there.
  • Do not disable caching globally unless you must. That can make the site slower and hide the real issue.
  • After each purge, reload and verify. Wait for the correct page, then confirm that it appears on mobile and desktop.

If you manage WooCommerce, membership, or a site with logged-in users, be extra careful with page caching. Pages like cart, checkout, account, and admin-related views often need exclusion rules so they do not get cached like public content.

When cache is not the real problem

Sometimes the site looks stale because something else is broken:

  • A CSS or JS file is still being referenced with the old file name
  • A plugin is generating different output for logged-in and logged-out users
  • The CDN is caching HTML that should not be cached
  • The host’s cache is being regenerated too aggressively after every visit
  • Server-side object cache is holding old query results after content changes

In those cases, repeatedly clearing cache only masks the symptom. The real fix is to find which layer is serving the wrong response and why.

How to prevent stale cache problems

A stable caching setup is less about “more cache” and more about clear boundaries. Good WordPress setups usually do a few things well:

  • Cache public pages aggressively, but exclude dynamic or logged-in areas
  • Use versioned asset files so CSS and JavaScript updates are recognized immediately
  • Keep only one layer responsible for each job when possible
  • Document which cache belongs to the plugin, host, and CDN
  • Test updates on a staging site before pushing them live

A reliable maintenance routine also helps because cache issues often appear right after updates, deploys, or content changes. If you want a broader system for preventing those problems, see What a Good WordPress Maintenance Routine Looks Like and Safe WordPress Updates Without Breaking Your Site.

When to call a professional

If you have cleared browser, plugin, host, and CDN cache and the site still shows stale content, it is time to look deeper. That is especially true if the wrong page appears for some visitors, cart or account pages are cached, or your changes keep reverting after you save them.

Mend can help isolate the exact cache layer that is misbehaving, check for CDN and host rule conflicts, and fix the underlying issue without turning the whole site’s performance settings upside down. If you want a fast, backup-first diagnosis, start with free diagnosis; if the site is actively broken and you need hands-on help, use Emergency Rescue.

If you prefer to hand off ongoing cache, update, and stability work before the next problem hits, a Care Plan can keep the site maintained with regular updates, backups, and monitoring.

A simple mental model that helps

When WordPress caching is confusing, ask one question: “Which version of this page is being served, and from where?”

If you can answer that, you can usually fix the issue quickly. If not, the safest next step is to trace the page from browser to CDN to host to WordPress, one layer at a time.

Frequently asked questions

Why does my WordPress site show old content after I edit it?

Usually one cache layer is still serving the old version. Start with your browser, then your caching plugin, then host cache, then CDN cache.

Should I disable caching to test a WordPress problem?

Not usually. It is safer to purge one layer at a time so you can tell which cache was causing the issue and avoid slowing the site unnecessarily.

Can object cache make WordPress content stale?

Yes, especially if Redis or another object cache is misconfigured or not cleared properly. It often affects admin screens, counts, menus, and dynamic content rather than obvious full-page staleness.

Do I need different cache rules for WooCommerce?

Yes. Cart, checkout, and account pages should usually be excluded from page caching so customers always see the correct, live content.