A slow WooCommerce store leaks money in a way you rarely see on a report. The customer who waits four seconds for a product page to load and leaves never shows up as a complaint. They just don’t buy. Google has measured it for years: every extra second of load time drags down conversions, and stores feel it hardest at the checkout, the exact moment a slow page costs you a sale. This guide shows how to speed up WooCommerce where it counts.
The frustrating part is that most advice on how to speed up WooCommerce is written for blogs. Install a caching plugin, compress your images, done. That works for a brochure site. It barely touches a store. WooCommerce is a different animal, and if you don’t see why, you’ll burn a weekend tuning plugins while the cart still crawls.
We’ll cover why WooCommerce is slow by default, the optimisation steps that genuinely help, and the one layer almost everyone gets wrong: the server underneath it.
Why WooCommerce is slow by default
A normal WordPress page can be cached. The server builds it once, saves a static copy, and serves that copy to everyone. Fast and cheap.
WooCommerce breaks that model on purpose. The cart, the checkout, the my-account page, and anything showing live stock or a logged-in price are different for every visitor. They cannot be served from a static cache, because a cached cart would show one customer another customer’s items. So those pages skip the cache entirely and get built fresh by PHP talking to your database.
That means the busiest, most revenue-critical pages on your store are the ones a caching plugin can’t help. Every “add to cart”, every checkout step, every account login runs real code and real database queries on your server in real time. On a crowded, underpowered host, that is where the lag lives.
This is the whole reason hosting matters more for a store than for a blog. You can’t cache your way out of a slow checkout. You have to make the underlying server genuinely fast.
Start with hosting, because it’s the foundation
If you only change one thing to speed up WooCommerce, change where it lives. Three things about your server decide how fast your dynamic pages render, and no plugin can override them.
Dedicated resources. Cheap shared hosting puts hundreds of sites on one machine, all fighting for the same CPU and memory. When a neighbour’s site gets a traffic spike, your checkout slows down and you can’t do a thing about it. A store needs guaranteed resources it never shares with strangers, so performance is the same on a quiet Tuesday as it is during a Black Friday rush. We break down the trade-off in our guide to shared vs dedicated hosting for WordPress.
A fast PHP stack. WooCommerce is PHP. The speed of your PHP engine directly sets how fast every uncacheable page builds. A modern web server running current PHP renders a cart in a fraction of the time an old, default stack takes. It is invisible in plugin lists and one of the biggest levers you have.
Object caching. This is the single most underused WooCommerce speed fix. Object caching stores the results of repeated database queries in memory, so the server stops asking the database the same questions over and over. For a store running constant dynamic queries, in-memory object caching can cut page build times dramatically. Most budget hosts don’t offer it at all.
Get these three right and the rest of the work below compounds. Get them wrong and you are optimising a car with the handbrake on.
How to make WooCommerce faster: the optimisation checklist
Once the server is solid, these are the changes that actually move the needle, roughly in order of impact.
Turn on object caching. If your host supports an in-memory object cache like Redis, enable it and connect WooCommerce to it. WooCommerce object caching is the highest-value step for a dynamic store, and it’s the one shared hosts most often lack.
Run a current version of PHP. Make sure your store is on a recent PHP release, not whatever was default three years ago. Newer versions are significantly faster and more memory efficient. Test your plugins on staging first, then switch.
Cache the cacheable pages properly. Your homepage, product pages, and category pages can and should be cached. Set up page caching, but exclude the cart, checkout, and my-account pages so customers never get served a stale or shared session. Good WooCommerce caching is about caching everything that’s safe and nothing that isn’t.
Clean up the database. Stores accumulate junk fast: expired transients, abandoned sessions, old order metadata, and bloated autoloaded options that load on every single request. Clear expired transients, keep autoloaded data lean, and if you’re on a recent WooCommerce version, enable High-Performance Order Storage so orders live in their own optimised tables instead of clogging the posts table.
Right-size your images. Product photography is usually the heaviest thing on the page. Serve images in a modern format like WebP, scale them to the size they actually display at, and lazy-load anything below the fold so the first screen paints fast.
Audit your plugins. Every plugin adds code that runs on page load, and store owners stack up extensions over time. Find the slow ones with a query monitoring tool, then remove anything you don’t need and replace heavy plugins with lighter alternatives. One bloated extension can undo a lot of server tuning.
Use a CDN. A content delivery network serves your static files, images, CSS, and scripts, from locations close to each visitor. That offloads work from your server and speeds up load times for distant customers.
Tame cart fragments and heavy AJAX. WooCommerce refreshes the cart contents in the background on many pages, even pages with no cart on them. On a busy store these requests pile up. Limit cart fragment loading to pages that need it so you’re not hammering the server on every product view.
How to test WooCommerce speed (TTFB and checkout)
Here is the mistake almost everyone makes: they test their homepage, see a good score, and call it done. Your homepage is cached. It was never the problem.
Test the pages that can’t be cached. Run a product page, add to cart, and walk through the full checkout while watching load times. Pay attention to Time To First Byte (TTFB), the time your server takes to start responding. A slow WooCommerce TTFB on a checkout page points straight at the hosting layer, not your front-end. A query monitor plugin shows you exactly which queries and plugins are eating the time, so you fix the real bottleneck instead of guessing.
How Forge fits
Forge Web Services was built for the exact problem this guide describes: stores that are slow at the server level, where no plugin can reach. Here’s how Forge’s WooCommerce hosting maps to the three foundations above.
Dedicated resources, every store. Every Forge plan runs on its own dedicated high-frequency compute VPS. No shared infrastructure, no noisy neighbours fighting your checkout for CPU. Your store gets a whole machine to itself, and you never have to manage it.
A genuinely fast stack. Forge servers run OpenLiteSpeed with current PHP, which executes WooCommerce’s dynamic pages faster than the Apache and old-PHP setups most budget hosts still ship. Redis object caching is pre-configured on every server, so the single biggest WooCommerce speed fix is already on before you log in.
The rest, handled. Caching, SSL, and a CDN come configured out of the box. Daily backups and a staging environment mean you can test a PHP upgrade or a plugin change safely. ForgeMail is included on every plan with proper domain authentication, so your order confirmations and password resets actually reach the inbox instead of the spam folder. And server-level security plus All-in-One WordPress Security and CDN run constantly in the background, so speed never comes at the cost of safety.
Pricing is flat and there is no renewal price hike. Plans start at $39 a month for a single dedicated store and scale to $69, $119, and $209 as you grow. What you sign up at is what you keep paying.
You can spend a weekend tuning plugins on a slow server and claw back a little, or move the store onto hardware built to run it and watch most of the problem disappear. The checklist above is real and worth doing, but it works far better on a foundation that isn’t holding you back.
Want a faster store without the weekend of work? Forge handles the migration for you, free, on every plan, and puts your store on a dedicated server with object caching already running. See plans and pricing or start a free migration. Not ready to switch yet? Join the waitlist and we’ll tell you the moment a spot opens in your region.