Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

WordPress

WordPress cache layers: page cache, object cache, CDN and browser cache

Published August 2026 · 2 min read · Updated 2026-09-05

WordPress caching is several layers: browser cache, CDN/reverse proxy, page cache, PHP opcode cache, object cache, and database/storage caches. Performance improves when each layer has a clear job and invalidation rule; stacking plugins and proxies blindly can create stale pages, login leaks, or hard-to-debug bypasses.

Map the request path first

Document whether traffic passes through a CDN, proxy cache, web server, WordPress page-cache plugin, PHP-FPM, object cache, and database. Determine which layer answers a cached page before adjusting TTLs.

Use response headers and cache-plugin diagnostics to confirm cache hits and misses.

Keep personalized and write paths out of shared page cache

Cart, checkout, account, admin, previews, form endpoints, REST writes, and pages varying by authentication/cookies usually need bypass rules. WooCommerce and membership plugins may publish recommended exclusions.

Never cache responses containing user-specific data across visitors.

Define invalidation for content changes

Publishing/editing posts, changing menus/widgets, updating products, or purging plugin state should invalidate the right URLs. A long TTL without purge logic can keep errors visible even after the origin is fixed.

Avoid global purge storms if targeted invalidation is supported.

Measure origin performance too

A fast cache hit can hide an origin that takes seconds on every miss. Test both warm and bypassed requests, then tune PHP/database/application work so cache failure or expiry does not become an outage.

  • Map every cache layer.
  • Bypass personalized paths.
  • Test invalidation.
  • Benchmark cache hit and origin miss.

Next step

Map each WordPress caching layer, protect personalized pages, verify invalidation and measure origin performance so stale content does not become the fix.

Explore DotMoose WordPress hosting

Keep reading

Related guides.

Do I need web hosting for WordPress? What WordPress actually needs

Self-hosted WordPress needs web hosting, but it does not require a specially branded WordPress plan. Compare WordPress.com, regular shared hosting, WordPress hosting and VPS options.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

PHP timeout troubleshooting: PHP, PHP-FPM or the web server?

Find which PHP timeout fired, check the right configuration, and distinguish PHP execution limits, PHP-FPM termination and nginx FastCGI read timeouts.

Read the guide

More wordpress guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move