The short answer: an object cache keeps in memory the answers WordPress asks the database for, so it does not ask again. It helps where the page cache cannot reach: the dashboard, the shop, people who are logged in. You use Redis, which you install on a VPS where you have full access. It does not replace the page cache; it adds to it.
When it is worth it
| Situation | Does it help? |
| Presentation site, almost read-only | Little. The page cache already solves it: LiteSpeed Cache. |
| Shop (WooCommerce) or members site | Yes. Many pages cannot go in the page cache. |
| Slow dashboard, many plugins | Yes, you usually notice it in the dashboard. |
| Server with no free memory | No. Redis takes memory; fix that first: Out of memory on a VPS. |
| Shared hosting | This is not where Redis is installed; you need a VPS where you can install services. |
Installing it, step by step
|
|
|
|
|
| Never open Redis’s port to the internet. By default it has no password and whoever gets there reads and deletes everything. Keep it on 127.0.0.1 and the port closed in the firewall: Keeping your VPS secure. |
| After changing the theme, after a lot of updates or if something looks “old”, flush the object cache in the plugin. And watch the memory: Seeing what uses CPU, memory and disk on your VPS. |
|
Want help deciding whether Redis is worth it on your site? Open a ticket with the address and the VPS plan. Open a support ticket |
RECOMMENDED PRODUCT WordPress hosting One-click install, updates handled, and speed that holds up. from $6.60/mo (3-year plan, with coupon) See plans |
- 0 Users Found This Useful











