WordPress Object Caching: Setup For Sites That Need It

Object caching stores expensive query results so subsequent requests don't repeat the work. WordPress has an in-memory object cache that resets per request; persistent object caching extends it across requests using Redis or Memcached.

For sites where the database is the bottleneck on uncached pages, object caching produces dramatic improvement. The setup varies by hosting environment.

What object caching helps

Admin pages. The dashboard runs many queries; object caching reduces repetition.

Cache-miss pages. When page cache doesn't apply (logged-in users, dynamic content), the underlying queries benefit from object caching.

AJAX endpoints. The dynamic responses often run database queries; caching reduces them.

REST API requests. Same as AJAX.

The setup with Redis

Install Redis on the server. Most quality hosting includes Redis or supports installation.

Install the Redis Object Cache plugin in WordPress.

Configure the plugin with Redis connection details. Default localhost:6379 usually works on shared hosting that includes Redis.

Enable object cache through the plugin's interface.

Verify it's working: the plugin shows hit rate statistics. Hits should accumulate as the cache populates.

The setup with Memcached

Similar to Redis but with Memcached daemon and a Memcached-compatible plugin.

Memcached and Redis are largely equivalent for WordPress object caching. The choice depends on what your hosting supports.

The setup on managed hosting

Quality managed WordPress hosts (Kinsta, WP Engine, Pressable) include object caching configured. Verify it's enabled through the host's control panel.

The host typically uses Redis or proprietary equivalent. Configuration is minimal because the host handles infrastructure.

The verification

After setup, verify object caching is working:

1. The plugin's dashboard shows hit rate. Should be increasing over time.

2. Page generation times should decrease for cache-miss pages.

3. Admin dashboard should feel more responsive.

The verification confirms the setup. Without verification, object caching might be configured but not actually working.

The honest framing

Object caching is a real optimization that's appropriate for sites where the database is the bottleneck. The setup is moderate effort; the improvement is meaningful for the right use cases.

For sites without database bottleneck, object caching adds infrastructure without producing visible benefit. Don't add it prophylactically.