WooCommerce checkout not loading: where it stalls

WooCommerce checkout does several things before a buyer can type a card number. It loads the page, builds the form, and asks for shipping rates and totals each time the address changes. Some of those calls go to your own server and some go to other services, such as a rate calculator or a tax tool installed as a plugin. If one of them never answers, the page keeps its totals in a loading state, and the buyer cannot tell whether to wait or leave. The browser's record holds the pending request, which the page itself never shows as an error.

• Open checkout in a private window with one product. Does the form appear under its heading?
• If the heading shows but the form stays empty, note which box never fills in.
• Enter a delivery address. Does the shipping box finish, or does it keep loading?
• In the Mimiq report, open the checkout step. Is a request still pending, or does one show an error status?
• List the plugins that add shipping, tax or address fields. Each one is a candidate for the stalled call.

A blank page with nothing drawn is the most alarming version, and it has ordinary causes. The checkout page setting may point at a page that holds neither the checkout block nor the checkout shortcode. A theme or plugin may expect one kind of checkout and receive the other, so the page draws its header and no form. A server error inside one plugin can also return an empty page, which a buyer reads as broken.

The record separates these cases. A failed server response shows as a request with an error status on the checkout step, while a wrong page setting returns a normal response with the wrong content. Rule out the setting first, because it is the quickest to check, and then read the plugin logs only if the response itself failed. Those two checks take a few minutes.

Shipping rates and totals are often calculated by a call the page makes each time the address changes. When that call goes to a service that is slow or down, the box keeps loading and the Place order button may stay locked. The right version of this check is to find which call is still pending. The wrong version is to refresh and retry, which sends the same call again and waits again.

Fix the calls one at a time. Turn off one shipping or tax plugin on a copy of the store, run the guest task again, and see whether the box finishes. If it does, that plugin was waiting on something outside your store, and you can ask its support or replace it. Do not switch plugins off on the live store to test, because a buyer may be in the middle of an order.

Give Mimiq the shop address and one task a guest would have: buy one paperback as a guest and fill in the delivery address. The task asks for guest checkout, so the visitor never signs in. The report shows each checkout step, the screenshot where the form stopped or finished, and every request that never returned, so a box stuck on loading shows up as the request it was waiting on.

A guest run stops before the final order button. It shows whether the form loads, whether the shipping box finishes and whether the totals appear, which covers most blank and stuck cases. It does not show whether the order is placed or whether the payment is accepted, and those need an order you place yourself. That is the part to repeat after every change.

Rerun the guest task after each change to shipping, tax, payment or checkout plugins. A new calculation that calls an outside service can hang for every buyer at once, and nobody sees it until orders drop. Keep the same task and the same product, so a stall shows up as a change from the last run rather than as a surprise.