Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My WooCommerce checkout is slow, or customers cannot finish paying

Short answer

A slow or failing WooCommerce checkout usually comes from one of four places: a cached checkout page, a plugin or theme conflict, a payment gateway that cannot report back to the store, or a server running out of time or memory. Place a test order, read WooCommerce's logs, and test conflicts on a staging copy, never on the live store.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The checkout page spins for a long time after I press Place order.
  • Customers say they paid but I see the order stuck on Pending payment.
  • The checkout shows an error, a blank page or the wrong shipping total.
  • It works for me but not for some customers, or only on mobile.
  • It got worse after a plugin, theme or PHP update.

Why does this happen?

  1. The checkout page is being cached

    The cart and checkout have to be built fresh for each shopper. WooCommerce's performance guide says caching should be set up so dynamic content such as the cart and checkout pages stays uncached. A cache rule that catches them can show one customer another customer's totals or break the form.

  2. A plugin or theme conflict

    Themes and plugins add code to the checkout, and two pieces of code can give conflicting signals. WooCommerce says testing is the only reliable way to find which one is responsible, and recommends doing it on a copy of the store so live sales are not affected.

  3. The payment gateway cannot report back to the store

    A webhook is how the payment gateway tells WooCommerce that a payment changed status. If that message does not arrive, the order stays on Pending payment even though money moved. WooCommerce notes that missing order notes often suggest the gateway failed to communicate with the store.

  4. The server runs out of time or memory

    Checkout runs the most code of any page: tax, shipping, stock, coupons and the gateway call. On a weak or overloaded server it can hit PHP's time or memory limit or a gateway timeout, and the customer sees a spinner or a server error.

What can I do about it today?

  1. Place a test order yourselfUse a real product and your normal payment method, on a phone and on a computer. Note the time and what you saw. Refund yourself afterwards if the payment went through.
  2. Look at WooCommerce's own logsOpen WooCommerce, then Status, then Logs. WooCommerce says missing order notes often mean the gateway failed to communicate with the store, so check whether the failing orders have notes from the gateway.
  3. List the orders that did not finishCompare your payment provider's dashboard with the orders in WooCommerce. Write down any payment that has no matching order. Do not re-create or re-charge anything until you know which is which.
  4. Write down what changedA plugin update, a theme update, a new caching or security plugin, or a PHP change by your host. The date of the last change is the most useful clue I can be given.
  5. Do not switch plugins off on the live storeDisabling plugins on a store that is taking orders can break the checkout further or lose carts. Ask your developer or host for a staging copy and test there.

When should I bring someone in?

  • Customers are being charged and the orders do not appear in WooCommerce.
  • The checkout broke after an update and nobody on your side can say which one.
  • You have no staging copy, so every test would happen on the live store.

How do I handle it?

  1. Take a backup and make a staging copyNothing is changed on the live store until there is a restore point and a copy to test on.
  2. Follow one failed order from start to finishI trace a failed attempt through the checkout, the gateway call and the webhook, so the cause is found by evidence, not by guessing at plugins.
  3. Test conflicts on the copyTheme and plugins are switched off one at a time on staging, using the same method WooCommerce documents, until the failing part is named.
  4. Fix, then repeat the test orderThe fix goes live with a rollback ready, and I place real test orders on the live store to confirm the checkout finishes.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Is it my host or my plugins?

It can be either. A test on a staging copy with plugins switched off separates the two: if the checkout is still slow with only WooCommerce active, the server or the gateway call is the more likely cause.

Customers paid but there is no order. Do I lose the money?

The payment still exists at your payment provider. Compare the provider's dashboard with your orders, and ask for help before refunding or re-creating anything, so no customer is charged or refunded twice.

Can a caching plugin cause this?

Yes. WooCommerce's performance guide says dynamic content such as cart and checkout pages should stay uncached, so a cache rule that includes them is a common thing to check.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.