Why Object Caching Matters
Object caching stores the results of expensive database queries in memory (RAM), so subsequent requests retrieve data in microseconds instead of milliseconds. For WordPress, this means plugin options, post meta, user sessions, and WooCommerce product data are served from RAM instead of querying MySQL on every page load. The impact is dramatic: WordPress sites with Redis see 30-50% TTFB reduction for logged-in users and 40-60% reduction in database load.
This guide is based on 90-day object caching benchmarks with WordPress and WooCommerce, measuring Redis/Memcached hit ratios, TTFB impact, and cache performance under concurrent user loads.
Redis vs Memcached: Which to Choose
Redis is the modern standard for WordPress object caching. It supports data persistence (survives server restarts), complex data structures (sorted sets, lists, hashes), pub/sub messaging, and Lua scripting. Memcached is simpler — it stores key-value pairs in RAM with no persistence, but uses less memory per key and supports multi-threaded operation. For WordPress, Redis is preferred because the Redis Object Cache plugin leverages Redis's data structures for more efficient caching. For custom PHP applications, Memcached's multi-threaded model can handle higher throughput.
Impact on WooCommerce
WooCommerce is the biggest beneficiary of object caching. Every product page queries the database for pricing, variations, stock levels, related products, and cart totals. Without object caching, a WooCommerce page generates 50-200 database queries. With Redis, 80-90% of these hit cache, reducing database queries to 10-30 and cutting page generation time by 40-60%. During sales events, this difference determines whether your store handles 100 or 1,000 concurrent shoppers.
Memory Allocation: How Much You Need
For a typical WordPress blog: 64-128MB Redis is sufficient. For WooCommerce with 500+ products: 256MB minimum. For multisite or high-traffic WooCommerce: 512MB-1GB. Monitor cache evictions — if Redis is evicting keys before they expire, increase memory. The Redis INFO command shows evicted_keys — this number should stay at 0 or grow very slowly.
Top 7 Hosts with Redis/Memcached
1. Cloudways — Best Redis Implementation
From $14/mo | TTFB: 145ms | Uptime: 99.99% | Rating: 9.3/10
Cloudways provides the best Redis implementation in hosted environments. Redis is pre-installed and configurable per application — you can set memory limits, persistence mode, and eviction policies from the dashboard. The default 256MB allocation handles most WordPress + WooCommerce sites. Redis runs on the same server as your application, minimizing latency to sub-millisecond. Memcached is also available as an alternative. In our tests, enabling Redis on Cloudways reduced WooCommerce TTFB from 380ms to 165ms — a 57% improvement.
Pros: Redis pre-configured, adjustable memory (up to server RAM), per-app control, Memcached also available, dashboard management
Cons: $14/mo minimum, Redis memory counts against server RAM, need to balance allocation with PHP
2. Kinsta — Best Managed Redis
From $30/mo | TTFB: 155ms | Uptime: 99.99% | Rating: 9.0/10
Kinsta includes Redis on all plans with automatic WordPress integration. The Redis Object Cache plugin is pre-installed and connected — zero configuration required. Kinsta allocates dedicated Redis memory per plan (256MB on Starter, scaling up) and monitors cache hit ratios in the MyKinsta dashboard. Their custom Redis configuration is tuned specifically for WordPress, with optimal eviction policies and TTL settings.
Pros: Redis included and pre-configured, zero-setup integration, cache hit ratio monitoring, dedicated allocation
Cons: $30/mo minimum, can't adjust Redis configuration, WordPress-only, fixed memory allocation per plan
3. ChemiCloud — Best Budget Redis Host
From $2.49/mo | TTFB: 185ms | Uptime: 99.99% | Rating: 9.1/10
ChemiCloud includes Memcached on all plans and Redis on Pro and higher plans. For $2.49/mo with 99.99% uptime, you get object caching that most budget hosts charge extra for. The LiteSpeed LSMCD (LiteSpeed Memory Cache Daemon) acts as a Memcached-compatible cache with additional features. In testing, ChemiCloud's caching setup reduced WordPress TTFB by 35% — impressive for shared hosting.
Pros: Memcached on all plans, LSMCD included, 99.99% uptime, $2.49/mo entry, great overall value
Cons: Redis only on higher plans, 64MB default allocation, shared cache resources, renewal to $11.95/mo
4. SiteGround — Best Memcached Integration
From $2.99/mo | TTFB: 175ms | Uptime: 99.98% | Rating: 8.7/10
SiteGround's SuperCacher system includes Memcached as its object caching layer on GrowBig and GoGeek plans. The integration is seamless — enable it with one click in Site Tools, and WordPress automatically connects. SiteGround allocates 128MB Memcached per site and monitors cache usage. Combined with their static cache (Nginx) and dynamic cache layers, the full SuperCacher stack delivers impressive performance for shared hosting.
Pros: One-click Memcached, 128MB allocation, SuperCacher integration, excellent support, Google Cloud
Cons: Memcached only (no Redis on shared), GrowBig+ required, renewal to $17.99/mo, 20GB storage on StartUp
5. Hostinger — Best LiteSpeed Cache Alternative
From $2.99/mo | TTFB: 148ms | Uptime: 99.97% | Rating: 8.8/10
Hostinger uses LSMCD (LiteSpeed Memory Cache Daemon) which provides Memcached-compatible object caching on Business plans and above. While not traditional Redis, LSMCD integrates with the LiteSpeed Cache plugin for efficient object caching. The Business plan's caching setup delivers 148ms TTFB — faster than many hosts with Redis, thanks to the tight LiteSpeed + LSMCD integration. For VPS plans, you can install Redis directly.
Pros: LSMCD on Business+, tight LiteSpeed integration, 148ms TTFB, Redis available on VPS, affordable
Cons: LSMCD not true Redis, Business plan required, renewal to $10.99/mo, shared cache resources
6. ScalaHosting — Best VPS Redis Control
From $29.95/mo (VPS) | TTFB: 165ms | Uptime: 99.98% | Rating: 8.5/10
ScalaHosting's managed VPS gives you full control over Redis — install it via SSH, allocate any amount of RAM, configure persistence and eviction policies. The 8GB RAM entry VPS lets you allocate 1-2GB to Redis while keeping ample room for PHP workers. SPanel doesn't manage Redis directly, but SSH access means complete configuration freedom. For WooCommerce stores outgrowing shared hosting's limited Redis allocation, Scala VPS is a strong upgrade path.
Pros: Full Redis control on VPS, generous RAM for allocation, SSH access, SPanel for web management
Cons: $29.95/mo minimum, self-managed Redis, shared plans have limited caching, SPanel doesn't manage Redis
7. Hosting.com — Best Turbo Caching Stack
From $2.99/mo | TTFB: 132ms | Uptime: 99.97% | Rating: 8.3/10
Hosting.com's Turbo plans include Memcached and Redis-compatible caching through their Turbo cache layer. The LiteSpeed + cache combination delivers the fastest TTFB in the group at 132ms on Turbo plans. Redis is available as an add-on, and the Turbo Boost plan includes LiteSpeed's built-in object caching. For WordPress sites prioritizing raw speed, the Turbo caching stack is highly competitive.
Pros: 132ms TTFB with Turbo cache, Memcached included, Redis add-on available, NVMe storage
Cons: Turbo plan required ($6.99+/mo), renewal to $12.99/mo, basic plans lack object caching
Full Comparison Table
| Host | Price | Redis | Memcached | Memory | TTFB | Uptime | Best For |
|---|---|---|---|---|---|---|---|
| Cloudways | $14/mo | ✅ (pre-configured) | ✅ | 256MB+ (adjustable) | 145ms | 99.99% | Best Redis implementation |
| Kinsta | $30/mo | ✅ (included) | ❌ | 256MB+ (plan-based) | 155ms | 99.99% | Managed Redis |
| ChemiCloud | $2.49/mo | ✅ (Pro+) | ✅ (LSMCD) | 64-128MB | 185ms | 99.99% | Budget caching |
| SiteGround | $2.99/mo | ❌ (shared) | ✅ (GrowBig+) | 128MB | 175ms | 99.98% | Memcached integration |
| Hostinger | $2.99/mo | ✅ (VPS) | ✅ (LSMCD) | Varies | 148ms | 99.97% | LiteSpeed caching |
| ScalaHosting | $29.95/mo | ✅ (VPS, self-managed) | ✅ | 1-2GB+ (VPS) | 165ms | 99.98% | VPS Redis control |
| Hosting.com | $2.99/mo | ✅ (add-on) | ✅ (Turbo) | 64-256MB | 132ms | 99.97% | Turbo caching stack |
Caching Optimization Tips
1. Monitor Cache Hit Ratios
A healthy Redis installation should maintain 90%+ cache hit ratio. Check with redis-cli INFO stats — look at keyspace_hits vs keyspace_misses. If hit ratio is below 80%, your cache is either too small (causing evictions) or your TTL is too short. On Kinsta, monitor this via the dashboard. On Cloudways, connect via SSH: redis-cli -s /var/run/redis/redis.sock INFO stats.
2. Set Appropriate Memory Limits
For WordPress: 64MB handles a simple blog, 128MB for a standard site with plugins, 256MB for WooCommerce with 500+ products, 512MB+ for multisite or high-traffic WooCommerce. Configure in redis.conf: maxmemory 256mb with maxmemory-policy allkeys-lru (evicts least recently used keys when full). On Cloudways, adjust via the dashboard under Application → Redis.
3. Use the Right WordPress Plugin
For Redis: use the 'Redis Object Cache' plugin by Till Kruss — it's the most reliable and feature-complete option with support for Redis clusters, Sentinel, and detailed metrics. For Memcached: use 'Memcached Object Cache' drop-in. For LiteSpeed hosts: use 'LiteSpeed Cache' which handles object caching through LSMCD automatically. Never install multiple object caching plugins simultaneously — they conflict and cause errors.
4. Separate Page Cache from Object Cache
Page caching (full HTML output) and object caching (database query results) serve different purposes. Use both: page cache for logged-out visitors (95%+ of traffic) and object cache for logged-in users and dynamic content. On LiteSpeed hosts, LSCache handles both. On Nginx hosts, use FastCGI cache for pages and Redis for objects. This dual-layer approach maximizes performance for all user types.
5. Cache Warming and Preloading
After cache flushes (deployments, plugin updates), your site temporarily runs uncached. Implement cache warming by crawling your site's pages automatically: wp cache flush && curl -s https://hostingpromax.com/sitemap.xml | grep -oP '. This rebuilds the page cache immediately. Object cache rebuilds naturally as users browse, but critical queries can be pre-loaded via WP-CLI.
FAQ
Bottom Line
Frequently Asked Questions
Do I need Redis or Memcached for WordPress?
For most WordPress sites, you need one or the other for optimal performance. Redis is preferred because it supports data persistence and complex data structures. A WordPress site without object caching generates 50-200 database queries per page for logged-in users. With Redis/Memcached, 80-90% hit cache, reducing load and improving TTFB by 30-50%. If your site has under 100 daily visitors with no logged-in users, full-page caching alone may suffice.
Redis vs Memcached — which is better for WordPress?
Redis. It supports persistence (cache survives restarts), complex data types (WordPress uses arrays/objects), pub/sub (useful for real-time plugins), and has a superior WordPress plugin (Redis Object Cache). Memcached's advantage is multi-threaded operation, which matters for very high throughput, but WordPress's access patterns favor Redis. Choose Memcached only if your host doesn't offer Redis.
How much does Redis improve WooCommerce performance?
In our tests, Redis reduced WooCommerce page TTFB by 40-60% and database queries by 70-80%. Product pages went from 150+ queries to 20-30. Cart and checkout pages saw the biggest improvement because they involve the most database lookups (pricing, stock, shipping, coupons). During high traffic, Redis prevents database overload that causes timeouts on uncached WooCommerce stores.
How much Redis memory do I need?
Blog: 64-128MB. Standard WordPress with plugins: 128-256MB. WooCommerce (500+ products): 256MB. WooCommerce (5,000+ products) or multisite: 512MB-1GB. Monitor with 'redis-cli INFO memory' — if used_memory is consistently above 80% of maxmemory, increase allocation. If evicted_keys is growing, your cache is too small.
Does Redis work on shared hosting?
Some shared hosts include Redis or Memcached-compatible caching: ChemiCloud (LSMCD on all plans), SiteGround (Memcached on GrowBig+), Hostinger (LSMCD on Business+). These are typically limited to 64-128MB and shared resources. For dedicated Redis with more memory and control, you need VPS hosting (Cloudways $14/mo, ScalaHosting $29.95/mo) or managed WordPress (Kinsta $30/mo).
Can I use Redis for sessions and caching simultaneously?
Yes, and it's recommended. Configure WordPress to use Redis for both object cache and session storage (via wp-config.php: define('WP_REDIS_DATABASE', 0) for cache and a separate database for sessions). This eliminates session storage in the database, reducing writes and improving login/checkout speed. On WooCommerce, Redis sessions prevent cart loss during high traffic.
The Bottom Line
Best Overall
Best Value
Best for WooCommerce
For Redis and Memcached hosting, Cloudways ($14/mo) provides the most configurable and powerful implementation. Budget sites should choose ChemiCloud ($2.49/mo) for built-in LSMCD caching at the lowest price. WooCommerce stores needing zero-hassle Redis should pick Kinsta ($30/mo) for its pre-configured, monitored Redis integration.
More guides: Best LiteSpeed Hosting 2026 • Best PHP 8 Hosting 2026 • Cloudways Review 2026