How To Fix A Slow WooCommerce Store

WooCommerce asks a lot more of your server than a normal WordPress site, and the gap gets wider as your store grows and the orders pick up. A slow store costs you twice: shoppers give up before they buy, and you and your staff lose time every day waiting on the admin area.

Speed work is also more than installing a plugin and hoping. The fixes below work best when you find the actual cause first, so we start with measuring and then work through the changes that make the biggest difference.

Why WooCommerce Is Harder to Speed Up

A typical WordPress site is mostly pages that can be cached. A store has several areas that can each be slow for different reasons: product and category pages, add to cart, the cart and checkout, the customer account area and the admin backend. Your store is also a business application your team works in all day, so backend speed matters just as much as what customers see.

The Main Fixes

1. Measure before you change anything

Run a speed test on your home page, a product page and the cart before you touch anything, so you have a baseline to compare against. Under 1 second feels instant to most visitors. Around 1.5 seconds is achievable for most stores and still feels quick. Once you go past 5 seconds, both your Google rankings and your sales start to suffer.

If you look at Core Web Vitals data, aim for at least 75% of visits in the green, which is roughly where Google’s “fast” rating starts. A big block of red and a big block of green with almost nothing in between usually points to one specific technical problem rather than general slowness.

2. Get hosting that’s built for WooCommerce

Hosting is the foundation everything else sits on, and it’s the most common reason a store is slow. Cheap shared hosting packs a huge number of sites onto each server, so every site gets a small slice of CPU and can only handle a few visitors at once. That hurts most on the cart, checkout and backend, which can’t be served from a cache.

Good hosting gives your account real processing capacity, stays fast when orders and traffic spike, has fewer outages and includes a memory based object cache. The price gap between cheap and good hosting is usually smaller than people expect. A self-managed VPS can have plenty of power, but server configuration matters more than raw specs, so we’d only go that way if you’re a server specialist. If your hosting is the bottleneck, fix that before anything else.

3. Set up page caching, with the right exclusions

A page cache builds each page once and serves that saved copy to the next visitor, instead of generating the page from scratch every time. On WP Alpha, server caching is available and here’s how to set it up. If you prefer a plugin, WP Rocket is simple to configure, while W3 Total Cache is free and fast but more complex.

Whatever you use, exclude the cart, checkout, my account and wishlist pages (and everything under them) from the page cache. If you don’t, checkouts can break and shoppers can end up seeing each other’s carts. Caches usually don’t serve cached pages to logged in users either, so always test from a separate browser where you’re logged out. For help choosing, see the best WooCommerce caching plugins.

4. Use Redis object caching

Object caching stores the results of repeated database queries so they don’t have to be run again. It speeds up the parts page caching can’t help with: the backend, add to cart and checkout, especially when several customers are checking out at once. It must run in memory. A disk based object cache actually makes things slower. Here’s how to turn on Redis object caching on WP Alpha.

5. Put a CDN in front of the store

A CDN serves parts of your site from servers around the world. That speeds things up for visitors far from your server and takes a lot of load off your hosting, which leaves more capacity for cart and checkout requests. Cloudflare has a free plan that suits most stores. On WP Alpha you can also turn on Nginx static file serving so images, CSS and JavaScript are delivered directly by the web server.

6. Block bad bots and brute force attacks

A typical WooCommerce store gets somewhere between 1,000 and 10,000 brute force login attempts a day, plus crawlers that add and remove cart items several times a second. Every one of those requests uses server resources. Stopping them at the Cloudflare firewall, before they reach WordPress, can cut the load on your store dramatically, even on the free plan. You should also stop well behaved bots crawling cart links with robots.txt rules like these:

Disallow: /*?add-to-cart*
Disallow: /*?add-to-wishlist*

Our WooCommerce robots.txt guide has a complete file, and this guide covers stopping fake spam orders.

7. Clean up and optimise the database

A slow database drags down every uncached request. Make sure your tables use the InnoDB storage engine rather than the older, slower MyISAM, and clear out accumulated junk. The free WP-Optimize plugin can help with the clean up. Take a backup first, and check how to restore backups on WP Alpha before you start. The full process is in our WooCommerce database optimisation guide.

8. Compress your images

Stores carry a lot of product images, and compressing them can take seconds off page loads by cutting how much data visitors download. Use lossless compression so product photos keep their quality. ShortPixel handles bulk compression well, can convert PNG files without transparency to smaller JPGs, and can create WebP versions, which are often 2 to 5 times smaller at the same quality. Serve WebP with picture tag markup so browsers that don’t support it fall back to the original.

9. Run the newest PHP version your site supports

WordPress and WooCommerce run on PHP, and each newer version runs faster than the one before it. Check your theme and plugins are compatible, test on a staging site, then switch. Here’s how to change PHP versions on WP Alpha.

10. Update or remove old plugins

Sites that have been running for years often carry plugins nobody uses any more, so audit your list and remove what you don’t need. Pay special attention to older paid plugins. Many of them don’t use the WordPress update system and sit untouched for years. We’ve seen stores running premium plugins more than 10 years old that throw errors behind the scenes, which shows up as slowness on the front end.

11. Dig deeper with Query Monitor

If the store is still slow, install Query Monitor. It shows what happens on each page load, including PHP errors, slow database queries and slow calls out to payment and shipping services. Errors that never appear in the dashboard can still add delay to every request. You can also turn on WordPress debug mode to log them. Check for JavaScript errors too: right click the page, choose Inspect, open the Console tab and look for anything in red. Overly aggressive JavaScript optimisation is a common cause of broken carts.

Fixing Specific WooCommerce Speed Problems

If one part of your store is slow while the rest is fine, go straight to the matching guide:

• Slow add to cart
• Slow checkout
• Slow WooCommerce backend and admin panel
• Optimising the WooCommerce database
• Slow pages for logged in customers
• Choosing a WooCommerce caching plugin
• An optimised WooCommerce robots.txt file
• The fastest WooCommerce themes