See the picks

The slow checkout guide

WooCommerce checkout slow: the causes, in the order to check them

A WooCommerce checkout is slow because it is the one page that cannot hide. Your product pages can be served from a copy made in advance. Your checkout cannot: it holds one shopper's cart, prices, and payment, so every load is built live, on the spot, by your host's computer doing real work through your store's own setup. That is why the checkout tells the truth about host and store alike, and why it is the page worth timing first.

Measure first: time your checkout before you change anything

Every fix below changes a number. If you never took the number, you will not know which fix worked, and neither will the support desk you end up arguing with. Our free store speed check fetches your homepage, shop page, and checkout from the outside and times each one, then splits the likely cause between your host and your store. Run it now, save the result, and run it again after each change. One owner posting in the WordPress.org support forums describes a place-order step taking 80 seconds; whatever your number is, it is the start of the conversation, not your theme's fault by default.

Where the wait lives, in check order

The six causes below are this page's whole list, drawn as one picture. Work them top to bottom; each one you clear makes the next one's number honest.

1. Your checkout is not cached, and that is normal

WooCommerce's own caching documentation is blunt: the cart, checkout, and my-account pages must stay out of the page cache, because they show information specific to the current customer. Most caching plugins and WooCommerce-aware hosts exclude them on purpose. So a fast homepage beside a slow checkout is not a caching failure. It is the expected shape of a store, and it means your checkout speed is your real speed, with no copy to hide behind. What actually helps is everything below: less live work per checkout, and a computer with more room to do it. One check is worth making, though: if a generic caching plugin or CDN rule is caching the checkout anyway, shoppers can see stale carts or a checkout that misbehaves. Exclusions set wrong break more stores than exclusions set at all.

2. Order storage: is HPOS on?

Older WooCommerce stores keep orders inside the WordPress posts tables, mixed in with pages and blog posts, and every order lookup digs through all of it. High-Performance Order Storage (HPOS) moves orders into tables built for orders. WooCommerce's own HPOS documentation states it is enabled by default for new installations from WooCommerce 8.2 onward, and that existing stores are not migrated automatically; switching is opt-in. Check yours at WooCommerce, then Settings, then Advanced, then Features, under Order data storage. If it still reads WordPress posts storage, the same screen is where you switch: turn on compatibility mode first so orders sync both ways, let the sync finish, then select high-performance order storage. Back up first, and try it on a staging copy if your store takes orders all day. Stores that started before late 2023 are the ones usually still on the old storage.

3. The place-order step waits on other people's servers

When a shopper clicks Place order, your store calls out: to your payment gateway to take the money, often to a shipping service for live rates, sometimes to tax and fraud services too. Your checkout cannot finish until the slowest of those answers comes back. A gateway having a bad afternoon looks exactly like a slow host. The test that separates them: place a test order with a simple offline payment method, cash on delivery or direct bank transfer, and time the step. Fast on the offline method and slow on your real gateway points at the gateway's side of the fence. Slow on both points back at your store and your host, and the rest of this list.

4. Database weight, and the object cache that lifts it

Every checkout asks the database dozens of questions: prices, stock, taxes, the shopper's session, the order being written. A store's database gathers weight over the years: old transients, bloated autoloaded settings, years of order data in the wrong tables (cause 2, above). An object cache, usually Redis on managed hosts, keeps the answers to repeat questions in memory so the database stops being asked the same thing on every page. If your host offers Redis and it is off, turning it on is one of the few one-switch changes that helps the checkout directly. If your host does not offer it at all, that is a fact about the host, and it belongs in the honest-ceiling section below.

5. Your PHP version

WordPress and WooCommerce run on PHP, and each PHP generation runs the same code faster than the one before it. A store still running on an old PHP version is paying for speed it never receives. Your version is shown in WordPress under Tools, then Site Health, then Info, then Server. Changing it happens in your host's panel, takes minutes, and is reversible. Check your plugins are current first; very old plugins are the usual reason a store got left behind on an old version.

6. Plugin weight on the checkout page itself

Every plugin that loads its scripts and styles on the checkout adds to the one page that can least afford it: checkout field editors, order bumps, live chat widgets, tracking tools, popup builders. The honest way to find the heavy one is on a staging copy of your store: turn off everything the checkout does not need, time it, and bring plugins back a few at a time. Our speed check gives you the before and after numbers from the outside, which is the part your admin screen cannot show you. On the live store, the lighter version of the same test is to ask of every plugin on the checkout: does this earn its place on the page where money changes hands?

7. If it got slow right after an update

A checkout that slowed the day something updated is a different animal. Work it in this order: clear every cache layer you have (plugin, host, CDN), because a stale copy of an old file beside a new one is the most common post-update fault. Then check whether the update switched anything structural: an HPOS sync left running, a plugin update that added a new call at place-order, a theme update that added weight to the checkout. If you can, roll the single suspect update back on a staging copy and time both states. The discipline that saves you here is the same as everywhere on this page: one change, one timing, no guessing in batches.

8. If it is slow on mobile and fine on your desk

Mobile shoppers feel page weight first: the same heavy checkout, carried over a slower connection to a less powerful computer in their hand. Images and scripts are the usual load, and our WebP image resizer exists for the image half of it. Test the way owners in the groups we read test: your own phone, on mobile data, clicking your own checkout like a stranger. Then time it properly with the speed check, and compare the checkout number against your homepage number. A small gap is the uncached truth. A huge one is a fixable cause from the list above.

The honest ceiling: when the settings are done and the host is the limit

There is a point where HPOS is on, the database is cached, PHP is current, the checkout is lean, and the number still will not move. That point is real, and it is the rented computer: too few workers behind the counter, too many neighbor stores, no room to grow. We explain the idea in full at what WooCommerce hosting is, in store terms. Past the ceiling, the fix is a different computer. If the store sells every day, that is the managed shelf, compared on true cost. If the budget is the binding constraint, it is the budget shelf, ranked on two-year cost. Either way, time the new host with the same check, so the move is judged on numbers and not on the sales page.

Questions owners ask about slow stores

How to speed up a WooCommerce site?

In the order this page is written: measure first, then order storage, gateway calls, database caching, PHP version, and plugin weight, and only then the host. Most stores find their cause in the first three. The storefront half of speed is easier: product pages can be cached and images compressed, which is why a store can look fast everywhere except the one page that pays.

Why is my WooCommerce site slow?

Because a store is live software, not a brochure. Every visit asks a computer to run WordPress, run WooCommerce, and dig through a growing database, and the busiest pages cannot be pre-made. Slowness is what that work feels like when the computer is crowded, the database is heavy, or the store itself carries too much. The split between those three is a measurement, not an opinion, and it is what our speed check estimates from the outside.

Can WooCommerce handle 50,000 products?

The software sets no product limit; stores far past 50,000 products run on it. The honest limit is the machine and the database underneath: big catalogs make the orders page, search, and filters do heavy work on every visit, so a catalog that size needs the host and database side sized for it, HPOS on, and an object cache running. The plugin is rarely the ceiling. The rented computer is.