WooCommerce Cart Loading Slow? Practical Optimization Guide on Cloudways

A slow homepage and a slow cart are two entirely different problems, and conflating them leads to the wrong fixes. A homepage can be fully cached — static assets go through CDN, and load time optimization is relatively straightforward. The cart can't. Every time a user loads it, the server has to check inventory in real time, calculate shipping, validate coupon codes, and read session data. None of that can be cached. It runs fresh every single time.

So if your homepage scores well in speed tests but the cart still drags — you're not missing something. That's a structural characteristic of WooCommerce, not a configuration mistake.

Why Cloudways Is Well-Suited for This

Cloudways is a managed cloud VPS platform — you choose the underlying provider (DigitalOcean, Vultr, or AWS) and get a pre-configured stack: Nginx, Redis, Varnish, PHP-FPM, and automated backups already in place. For WooCommerce optimization specifically, the most practically valuable aspects are the built-in Redis support and the availability of high-frequency CPU plans. Both matter directly for e-commerce workloads.

Step 1: Make Sure Dynamic Pages Aren't Being Cached

Check this first — it's the most common source of mysterious cart behavior. Cart, checkout, and My Account pages must never be cached. If they are, you'll see mismatched cart contents between users, broken login states, and coupon codes that stop working. These are the kinds of issues that generate confused customer support tickets.

In the Cloudways dashboard, go to Application Settings and check Varnish Exclusion Rules. Confirm these paths are excluded:

/cart/
/checkout/
/my-account/

This is WooCommerce's own baseline recommendation. A surprising number of performance problems trace back to this not being set correctly.

Step 2: Enable Redis Object Cache

WooCommerce's performance bottleneck is usually the database, not the CPU. Product prices, inventory status, user sessions, order data — all of it requires frequent MySQL queries. Redis caches hot data in memory, cuts the database load, and cart response times come down as a direct result.

Cloudways includes Redis natively — no installation required. Go to Server Management → Manage Services → Redis → Enable. Then install the Redis Object Cache plugin in WordPress and connect it.

// Add to wp-config.php if the plugin doesn't write this automatically
define('WP_REDIS_HOST', '127.0.0.1');
define('WP_REDIS_PORT', 6379);
define('WP_CACHE_KEY_SALT', 'your_site_name_');

Run another cart load time test after enabling Redis. In most cases the improvement is visible immediately.

Step 3: Clean Up WooCommerce Session Data

This one is easy to miss. WooCommerce stores session data in the wp_options table by default. As order volume accumulates, that table grows, and queries against it get progressively slower. A lot of people spend time hunting performance problems and eventually discover that wp_woocommerce_sessions has ballooned to an unreasonable size.

Clear expired sessions with:

DELETE FROM wp_woocommerce_sessions 
WHERE session_expiry < UNIX_TIMESTAMP();

WP-Optimize or Advanced Database Cleaner can automate this on a schedule, which is more practical than running SQL manually on a recurring basis.

Step 4: Find the Plugins Firing Hidden Ajax Requests

Cart page slowness is often not WooCommerce itself — it's the stack of plugins that fire Ajax requests continuously on that page. Live chat, wishlists, dynamic recommendations, countdown timers: individually fine, but stacked together they can generate dozens of concurrent background requests on every cart page load.

Install Query Monitor and check the Admin Ajax Requests count on the cart page. If it's in double digits, work through the plugins triggering requests and decide which ones are worth keeping. Disabling a single underperforming plugin sometimes cuts cart load time in half.

Step 5: Upgrade to PHP 8.3

Free performance improvement, no downside to not doing it. PHP 8.x handles WooCommerce workloads measurably faster than older versions — official benchmarks put PHP 8.3 roughly 30% ahead of 7.4. Cloudways lets you switch PHP versions from the dashboard without touching the command line. Before switching production, run a compatibility check on the staging environment first. Most current plugins are 8.3-compatible; older or abandoned plugins are where issues occasionally appear.

Step 6: Get Cloudflare Configuration Right

Cloudflare's direct impact on cart speed is limited — it doesn't have much leverage over dynamic pages. But static asset handling is still worth configuring properly. Enable Brotli compression (better compression ratio than gzip), HTTP/3 (reduces connection establishment overhead), and Early Hints (preloads critical resources). These won't transform cart performance, but they reduce overall page load time and improve the perceived experience.

Cart and checkout pages need to be set to bypass caching in Cloudflare. Add both URL paths in Page Rules with Cache Level: Bypass. Missing this causes the same category of session and cart data problems described in Step 1.

Step 7: Choose the Right Cloudways Underlying Plan

WooCommerce's dependency on single-core performance is higher than most people expect. Checkout logic is single-threaded — higher CPU clock speed has a more direct effect on checkout response time than adding more cores at lower frequency.

For a small store doing 100–300 daily visitors, a DigitalOcean 2GB / 2 vCPU plan is sufficient. For stores doing 1,000+ daily visitors or running paid ad traffic, Vultr High Frequency is the better choice — the higher clock speed delivers targeted advantages for WooCommerce specifically. Adding RAM without improving CPU frequency produces limited gains for this workload.

Step 8: Regular Database Maintenance

A WooCommerce store running for six months or more has almost certainly accumulated significant database bloat — post revision history, expired transients, log entries, stale session data. Left unaddressed, this makes every database query incrementally slower over time. Schedule regular cleanup of post revisions, expired transients, and old sessions to keep the database at a manageable size. WP-Optimize handles this automatically on a timer, removing the need for manual intervention.

A Real-World Reference

One cross-border WooCommerce store running on Cloudways with Vultr HF made four changes: enabled Redis, upgraded to PHP 8.3, cleared accumulated session data, and reduced the number of Ajax-heavy plugins on the cart page. No hardware upgrade. Cart load time dropped from over five seconds to under two. Checkout page saw similar improvement.

The Right Order of Operations

If your cart is loading in over three seconds, don't reach for a more expensive VPS as the first response. In most cases, the actual bottleneck is Redis not being enabled, session tables not being maintained, or Ajax plugin requests not being controlled. Work through these configuration steps first. Most stores can achieve significant cart speed improvements without touching their hardware tier at all.