Page caching solves the easy half of the problem. It serves a finished page to a stranger in milliseconds. However, it does nothing for a logged-in customer, a filtered shop page or a checkout, because those pages cannot be reused. That is where object caching earns its keep, and it is the step most sites skip.

What object caching actually stores

WordPress asks the database the same questions constantly: settings, menus, user data, product attributes. On a busy page that can run to hundreds of queries. Object caching keeps the answers in memory, so the second request never reaches the database at all.

By default WordPress caches those answers only for the length of one request. Adding Redis or Memcached makes the cache persistent across requests and across visitors. Therefore the benefit grows exactly where page caching gives up: dynamic pages under load.

When it is worth doing

  • WooCommerce or membership sites. Carts and accounts bypass page cache entirely.
  • Big catalogues. Filtering and search hammer the database.
  • Slow admin. The dashboard is never page-cached, so editors feel every query.
  • Traffic spikes. Memory absorbs bursts that a database will not.

Meanwhile, a small brochure site with page caching already in place will notice very little. So measure first. Query Monitor will tell you how many queries a page runs and how long they take, and that number decides the case.

Getting it right

Ask your host whether Redis is available, because a shared plan often does not offer it. Next, give the instance its own memory limit and an eviction policy, otherwise a full cache starts refusing writes. The Redis documentation explains those settings plainly.

Above all, do not run one shared Redis instance across several sites without separating them. One site flushing the cache should never slow down another.

In short, object caching is the fix for pages you cannot cache. Pair it with the basics in the hosting stack behind a fast site, and make sure your plan can support it by reading shared vs VPS vs managed hosting. Our team sets this up as part of a performance engagement.