{"id":15,"date":"2026-09-05T18:27:01","date_gmt":"2026-09-05T18:27:01","guid":{"rendered":"https:\/\/hostcrafter.com\/kb\/object-cache-redis\/"},"modified":"2026-09-06T17:36:34","modified_gmt":"2026-09-06T12:06:34","slug":"redis-object-cache","status":"publish","type":"post","link":"https:\/\/hostcrafter.com\/kb\/redis-object-cache\/","title":{"rendered":"Redis Object Cache: When to Turn It On, and When Not To"},"content":{"rendered":"

Turn Redis on if your site has a cart, a checkout, memberships, or visitors who log in.<\/strong> On a blog or a brochure site the page cache is already doing that work for you, and this switch is built for the pages a page cache cannot serve. Knowing which is which is the whole of this page.<\/p>\n

\n
\n
Turn it on for<\/dt>\n
WooCommerce, memberships, logins<\/dd>\n<\/div>\n
\n
Leave it off for<\/dt>\n
Blogs, brochures, portfolios<\/dd>\n<\/div>\n
\n
Costs<\/dt>\n
Nothing. Included<\/dd>\n<\/div>\n
\n
Where<\/dt>\n
Panel \u2192 Redis Cache<\/dd>\n<\/div>\n<\/dl>\n

Why It Does Nothing for a Blog<\/h2>\n

There are two caches, and they work at different moments.<\/p>\n

\n\n\n\n\n\n
<\/th>\nPage cache<\/th>\nObject cache (Redis)<\/th>\n<\/tr>\n
What it stores<\/strong><\/td>\nThe finished HTML page<\/td>\nThe answers to individual database queries<\/td>\n<\/tr>\n
When it helps<\/strong><\/td>\nBefore WordPress starts<\/td>\nAfter WordPress has started<\/td>\n<\/tr>\n
Who it helps<\/strong><\/td>\nAnyone not logged in<\/td>\nAnyone the page cache cannot serve<\/td>\n<\/tr>\n
Typical gain<\/strong><\/td>\nHundreds of times faster<\/td>\nNoticeable on complex, uncacheable pages<\/td>\n<\/tr>\n<\/table><\/div>\n

On a blog, almost every visitor is anonymous and gets a page the web server already has on disk. WordPress is never started, so there are no database queries for Redis to have saved. Adding it changes a number that was not the problem.<\/p>\n

On a shop, the pages that matter most are exactly the ones a page cache must never serve: a cart with somebody’s items in it, a checkout, an account page. Those run WordPress every time, and that is where an object cache is felt.<\/p>\n

If your site is slow and it is a blog, this is the wrong switch.<\/b> Look at the page cache first. See The best WordPress cache plugin on our servers, measured<\/a>, which is the plugin we install on every site and the one that does the work for anonymous visitors. <\/div>\n

Turning It On<\/h2>\n

Open your hosting account in the client area and choose Redis Cache<\/strong>. Every WordPress site we manage is listed with its own switch.<\/p>\n

\"The
The Redis Cache screen. One switch per website, with a Flush button on the sites where the cache exists.<\/figcaption><\/figure>\n

Flip the switch for the site that needs it. The panel installs the object-cache drop-in, connects it, and the site keeps serving throughout. There is nothing to configure and no plugin to install.<\/p>\n

Each website’s object cache is private to that website.<\/strong> Nothing else reads it, on your account or anyone else’s.<\/p>\n

Flushing It<\/h2>\n

A Flush<\/strong> button appears beside any site that has the object cache on. It empties that site’s cached query results and nothing else. Reach for it when you have changed something directly in the database, or when a value on the site is stale in a way a page-cache clear did not fix.<\/p>\n

“On, but WordPress Cannot Reach Redis”<\/h2>\n

If the panel says this, the drop-in is installed but Redis is not answering. Your site is not broken.<\/strong> WordPress falls back to querying the database directly, exactly as it does with the cache off. What you have lost is the speed-up, not the site.<\/p>\n

Turn the switch off and on again. If it comes back, open a ticket; we can see the node’s own logs and you cannot.<\/p>\n

Turning It Off<\/h2>\n

Flip the switch back. The drop-in is removed and WordPress goes back to the database. Nothing is lost, because an object cache holds only copies of answers it can work out again.<\/p>\n

Questions<\/h2>\n
\n

Does Redis cost extra?<\/h3>\n

No. It is included, and it is off by default because on most sites it changes nothing worth the moving parts.<\/p>\n

Do I need to install a Redis plugin?<\/h3>\n

No, and please do not. The switch installs and configures the drop-in itself. A plugin like Redis Object Cache added on top will fight with it over the same file.<\/p>\n

Will Redis make my WooCommerce store faster?<\/h3>\n

Usually yes, and specifically on the pages that were always slow: cart, checkout, my-account, and admin. Product listings that anonymous visitors see were already coming from the page cache.<\/p>\n

Can another customer see my cached data?<\/h3>\n

No. Every website’s object cache is private to that website.<\/p>\n

Should I turn it on for a staging copy?<\/h3>\n

There is no need. A staging copy has one visitor: you.<\/p>\n<\/div>\n

\n

Read next<\/h2>\n