Cache Manager
Object Cache vs Page Cache in WordPress
Understand what WordPress page cache and object cache store, which requests each can accelerate, and why they require different keys, invalidation, and troubleshooting.
Main Menu
Caching is the difference between a site that feels instant and one that makes people wait, and it is also the most common reason a change you just made does not appear. Both facts come from the same mechanism: something between your database and the visitor is holding a copy.
The complication is that there is never only one cache. A WordPress page can be held in a page cache on the server, an object cache in front of the database, a browser cache on the visitor’s machine, and a CDN edge somewhere near them — four independent layers, each with its own idea of how long a copy stays fresh. Fixing “my changes are not showing” means knowing which one is answering.
These guides work through that stack. Setting caching up safely, deciding what must never be cached — carts, checkouts, logged-in sessions — and understanding the headers that control how long anything is kept. Then the optimisation layer that usually arrives with caching: minification, lazy loading, image formats, and the Core Web Vitals numbers those choices move.
A large group here covers breakage, because aggressive optimisation breaks things in specific, recognisable ways. A minified stylesheet that collapses a layout, deferred JavaScript that kills a menu, two caching plugins fighting each other, a CDN serving yesterday’s HTML.
Start with the explainer on how caching works if the layers are new to you. Almost every other article assumes you can tell them apart.
Understand what WordPress page cache and object cache store, which requests each can accelerate, and why they require different keys, invalidation, and troubleshooting.
Diagnose stale or over-bypassed WordPress pages by comparing origin and Cloudflare responses, aligning cache keys and exclusions, and purging only the affected edge entries.
Connect a CDN to WordPress safely by starting with static assets, defining cache and TLS behavior, testing private routes, and keeping a documented DNS rollback.
Use WebP in WordPress as part of a tested responsive-image workflow. Preserve originals, compare quality and file size, verify MIME delivery, and avoid stale or missing derivatives.
Reduce WordPress image weight by serving the right dimensions, responsive candidates, format, and encoding quality while preserving originals and avoiding visible artifacts.
A lazy-loaded hero image can delay Largest Contentful Paint. Learn how to identify the actual LCP element, expose it early, choose the right responsive source, and use priority hints carefully.
Lazy-load offscreen WordPress images and iframes without delaying the LCP image or causing layout shifts. Learn which media to exclude and how to test real scrolling behavior.
Understand how defer and interaction-based delay affect WordPress JavaScript, which scripts can wait, and how to avoid breaking navigation, consent, forms, or checkout.
Trace a WordPress JavaScript minification failure from the first console error to the responsible script or build option, then fix or exclude it without changing unrelated loading behavior.
Find the exact stylesheet, selector, asset URL, or ordering change behind a WordPress CSS minification failure, then fix or exclude it without disabling every performance feature.