Redis Object Cache: When and Why It Speeds Up WordPress

Every time someone opens a WordPress page, PHP fires dozens, sometimes hundreds, of queries at the MySQL/MariaDB database: which options are active, which plugins run, what belongs in the menu, what the post content is. Most of those queries repeat for nearly every visitor. Redis object cache stores those results in fast memory (RAM) and returns them without hitting the database again. The result is less database load and shorter page build times.

When Redis actually helps

Not every site benefits equally. A static brochure site with full-page caching often never touches the database, so Redis adds little there. But the moment you have dynamic content — a WooCommerce store with carts and accounts, a forum, memberships, a plugin-heavy site, or an LMS — things change. On those sites the admin and cart cannot be fully cached as HTML, so every visit hits the database. That is where Redis typically cuts page generation from, say, 600 ms down to 200-300 ms.

Object cache vs. page cache

It is easy to confuse the two. Page cache stores the finished HTML of a whole page and serves it to anonymous visitors. Object cache stores individual query results and helps even where page cache cannot — in the admin, on the cart, for logged-in users. The best results come when both run together: page cache for guests, Redis for everything else.

How to turn it on

Your host needs a Redis server installed and the PHP redis extension enabled. Then you add a plugin like Redis Object Cache in WordPress, click Enable, and if needed add a unique key prefix in wp-config.php so two sites do not mix. After that the plugin stats show a hit ratio — how many queries were served from memory. Aim for above 90%. If it is lower, some plugin is usually querying the database in a way that is not cacheable, so it is worth checking.

What to watch out for

Redis uses RAM. On shared hosting that is limited, so it matters that the provider reserves memory correctly and sets an eviction policy for old keys (maxmemory-policy). If memory fills without that policy, Redis can start rejecting new writes. That is why it is safest when Redis is part of the hosting plan and configured by the provider, not something you patch together yourself.

With us Redis comes tuned alongside NVMe disks and caching, so the database keeps breathing even at peak. See WordPress hosting or compare the plans and pick the one that fits your site size.