You have probably enabled page caching already — it is the single biggest WordPress speed win. But page caching has a blind spot: it only helps visitors who see the exact same page. Logged-in users, WooCommerce shoppers with carts, membership sites, and busy admin dashboards bypass the page cache entirely and hit the database on every load. That is the gap Redis object caching fills.
This guide explains what object caching actually does, when it is worth enabling on Hostinger, and the exact steps to turn it on in hPanel and connect WordPress to it.
Page cache vs. object cache: the 60-second version
- Page cache stores the finished HTML of a page and serves it as-is. Fast, but useless for anything personalized or dynamic.
- Object cache stores the results of database queries in fast memory (RAM) instead of re-running them. When WordPress needs the same data again — a product list, a user’s session, widget output — it grabs it from memory in microseconds instead of asking MySQL again.
Redis is the in-memory store Hostinger uses for this. Think of it as a short-term memory for your database: the first visitor pays the full cost of a query, and everyone after that gets the memorized answer until it expires or the underlying data changes.
When Redis helps — and when it does nothing
It helps most when:
- WooCommerce or other e-commerce: carts, product filters, and account pages are dynamic and skip page cache
- Membership, forum, or LMS sites with lots of logged-in traffic
- High-traffic blogs where the database is the bottleneck (slow admin, sluggish wp-admin)
- Sites with heavy plugins that run dozens of queries per page
It does little when:
- Your site is a mostly static brochure or blog where page cache already serves 95% of visits
- Traffic is tiny — with a handful of daily visitors, the database is never stressed enough for caching to matter
- The real problem is elsewhere: unoptimized 5 MB images or a 3-second third-party script will not be fixed by any cache
Honest rule of thumb: if your Time to First Byte is slow even for logged-in users, or wp-admin feels sluggish, Redis is worth trying. If anonymous visitors already load in under a second, you will barely notice it.
Is Redis available on your Hostinger plan?
Object caching is not on every Hostinger plan — it is a resource-intensive feature typically reserved for higher tiers (Cloud plans and similar). To check yours:
- Log in to hPanel.
- Go to Advanced → Object Cache (the exact menu label can vary; look under the Advanced or Performance section).
- If you see an option to enable Redis/Memcached object caching, your plan includes it. If the section is absent, your current plan does not — page caching via LiteSpeed Cache remains your main lever (see our WordPress speed guide).
Do not pay for a plan upgrade just for Redis unless you have identified the database as your bottleneck using the test in the previous section.
Step-by-step: enable Redis and connect WordPress
- Enable it in hPanel. In the Object Cache section, toggle Redis ON for your website. Note the connection details shown — typically a host (often localhost or a socket path) and a port. Keep this tab open.
- Install the connector plugin. Two good options:
- LiteSpeed Cache (if you already use it): go to LiteSpeed Cache → Cache → Object, set Object Cache to ON, choose Redis as the method, and enter the host/port from hPanel. This keeps everything in one plugin.
- Redis Object Cache (by Till Krüss): a dedicated, lightweight plugin. Install it, then add the connection constants it asks for to wp-config.php (host, port, and optionally a database number).
- Verify the connection. The Redis Object Cache plugin shows a status screen (“Connected” plus Redis version). In LiteSpeed Cache, the Object Cache settings page shows connection status. If it says it cannot connect, double-check the host/port — a typo here is the #1 cause.
- Flush once, then test logged-in. Flush the object cache a single time after setup, then browse the site while logged in (or test a WooCommerce cart flow). Database-heavy pages should feel snappier; you can confirm with a tool like Query Monitor, which shows the drop in database query time.
- Leave it alone afterward. Object cache invalidates itself when content changes. You do not need to flush it routinely — in fact, frequent manual flushes defeat the purpose.
Troubleshooting
- “Connection refused”: Redis is not actually enabled in hPanel, or the host/port is wrong. Re-check the hPanel Object Cache screen.
- Site feels slower: rare, but a misconfigured persistent cache on a tiny site adds overhead without benefit. Disable it and rely on page cache.
- Stale data after changes: some plugins store data with long TTLs. Flush the object cache once after major changes (theme switch, bulk edits), then leave it.
- Conflict with another caching plugin: run one object-cache solution at a time. If LiteSpeed Cache handles it, do not also activate the standalone Redis plugin.
Frequently asked questions
Is Redis object cache the same as page caching?
No. Page caching stores finished HTML pages and only helps anonymous visitors seeing identical content. Object caching stores database query results in memory and helps dynamic, logged-in, and e-commerce traffic that page caching cannot serve. They complement each other — most fast sites run both.
Do I need Redis for a small blog?
Almost certainly not. On a small blog, page caching handles nearly all traffic and the database is never under strain. Redis earns its keep on dynamic sites: stores, memberships, forums, and high-traffic dashboards.
Will enabling Redis break my site?
It is low-risk: the worst common outcome is “connection refused” in the plugin status, which just means WordPress falls back to normal database queries. Still, enable it during low-traffic hours and verify key flows (login, checkout, forms) afterward, as with any change.
Redis vs. Memcached — which should I pick on Hostinger?
Whichever hPanel offers on your plan. Redis is the more common and better-documented option for WordPress, with richer plugins and tooling. If both are listed, choose Redis.