Checkout can be at the initial opening, after changing the region and method of sending, or just when pressing the record button. These three steps have different requests. If you don't separate the exact time and the slow request, you may optimize the image and CSS while an Ajax is waiting for a few seconds to calculate the sending or API.
Quick answer:In DevTools tab Network, save documents and Ajax/Fetch requests separately. Match status, duration and response with the log, PHP and external requests on the same timestamp. Do not cache the checkout page and have backup and payment controlled before changing gateway or session.
At what stage does slowdown occur?
- Loading of the page:Templates, assets, cart/session and primary queries.
- Updated to the checkout:Calculate shipping, taxes, coupons and total.
- Order recording:Validation, order creation, inventory reservation and payment selection.
- Transfer to the payment gateway:Create an API request, DNS/TLS and receive a redirect.
- Payback:Callback/webhook and change order status.
Follow each step with a specific order or time tag and do not log card or secret data.
Detection with the DevTools Browser
Activate Preserve log and run a controlled purchase. Check for long requests, waterfall, and payload errors. If the request is in Pending mode, the network or server is waiting; if the response is fast but the interface is slow, check JavaScript and Long Task. The response may have an error message even if the status is 200.
Calculation of shipments and taxes
The transportation plug-in may call multiple APIs by changing the address. Inappropriate debounce or repeat hook causes back-end requests. Measure latency, timeout and number of calls per provider. The resulting cache should be valid based on origin, destination, weight, and conditions; do not reuse another user's forwarding rate.
Session and Cart Fragment
Cookies, session storage and fragment requests are required for the basket, but domain/HTTPS interference, public cache or storage slowness can create unstable behavior. Test with a new anonymous session and then a user logged in.
Gate and external services
When you place an order, a gateway, anti-heart, text, CRM or webhook may be called. If the operation is synchronous, its slowness directly affects the user experience. Check connect and read timeout, retry and idempotency.
Query and Lock database
Creating multiple write and read orders is available. A query report or a heavy job can create a lock or I/O at the same time. See slow logs and long transactions in the same space. Deleting meta orders or changing the index on the production path does not detect; first clone and backup.
PHP-FPM and the request line
The checkout page removes the cache and requires a real worker. If all the workers are busy, the request will wait even before WordPress runs. Check queue status and message to the ceiling.PHP-FPM for WordPressIt shows why a worker without enough RAM is more dangerous.
Check the interference safely.
In staging with the same version and data, set the default template and only the necessary WooCommerce/portal plugins; then add the plugins step by step. Record the result of each step with the same request. Disabling the port or active shipping on production without user notice can cause the actual order to be missed.
A step-by-step correction path.
- Build backup, baseline and trial payment.
- Request and identify the component that owns it.
- Fix PHP, retry and repeat hook errors.
- Remove unnecessary external calls from the synchronous path.
- Modify the query and index according to plan.
- Set the PHP and database capacity to the actual load.
- Post the change with smoke test order and callback.
Do not cache the checkout.
General Checkout HTML may be incorrect about nonce, session, method of sending, and user information. Bypass should cover all affiliate paths and WooCommerce cookies. Object cache also requires validation and proper separation. Speeding up with the old total display is not an acceptable result.
The Criteria of Success
- Document time and every Ajax is important.
- P95 time of order
- Validation and gateway error rates
- Unusual order number Pending or Failed
- PHP queue and latency database
- Total correctness, shipping, tax and coupon
- Receive a callback and email order.
Common Mistakes
- Page caching Checkout
- Increased timeout without finding service.
- Multiple push of the pay button while pending
- Testing with old session and browser plug-in
- Disable SSL verification
- Restore old database and lose new orders.
The slow difference with the arresting of the order.
If the request ends with the correct answer, the latency problem. If the spinner remains, the request is repeated or the order is made without redirect, the path is not cleared.Checkout when you place an orderFirst, check the order or transaction that actually made so you don't pay again.
When do you need special assistance?
If the delay occurs only when actual payment is made or if test changes to orders are defective, the continuation of the test is on production periscope.Support for the WooCommerce storeIt can track the request, log the payment gateway and check the order status without removing evidence.
Common Questions
Does a CDN speed up checkout?
Static assets may be faster, but dynamic processing and payment API are still performed at origin.
Why is Checkout only for the guest?
Compare session creation, validation, and guest-specific paths with the logged-in user.
Why does it slow down with the change of province?
Usually, the request shipping/tax calculation is executed; check the number of calls and latency of the provider.