Checkout reliability

A slow checkout

Name the wait before you rebuild anything. The visible waits are different: the page's main content has not rendered, a cart change has not finished, shipping choices have not appeared after an address is available, a field is slow to respond, or an existing payment attempt is waiting on the provider. Chrome's Largest Contentful Paint describes when the largest visible content renders. Interaction to Next Paint describes how long a click, tap, or keypress takes to paint. Neither metric is a shipping lookup or a bank delay, and this page sets no speed threshold. On WooCommerce, shipping methods are shown for the address that matches a zone. A delayed payment method can leave an order on hold while confirmation is still pending. On Stripe, a PaymentIntent in processing is an asynchronous method, which Stripe says can take up to a few days. Record the step and the clock from a session you already have. Do not place a new payment to time it. Describe the work you need. Prism will confirm scope, responsibilities, fees, and terms before work begins.

For: An owner or authorized representative of a research-use-only peptide business whose checkout feels slow and who has not yet identified the waiting step.

Updated 2026-09-21

The waiting step chooses the investigator

A checkout can be slow in one place and ordinary everywhere else. Rebuilding the theme does not answer a carrier rate that has not returned, and a payment provider cannot explain a page that has not rendered. Write the step that was still waiting, when you started the clock, and when it stopped.

Use a session that already happened, or watch a checkout up to but not including a new payment. The sheet is a location, not a grade. Chrome publishes ranges it calls good for its metrics. Those ranges are not a pass mark for this checkout and are not a reason to rebuild.

Page load and field response are browser observations

Largest Contentful Paint reports when the largest image, text block, or video in the viewport has rendered, counted from the navigation. It describes the load the person can see. It does not describe the time after they enter an address or submit a payment.

Interaction to Next Paint observes the latency of click, tap, and keyboard interactions during the visit. The latency runs from the start of the interaction until the browser can paint the next frame. A slow field is this kind of wait. A button that cannot be seen or tapped is a different problem: that is an obstacle, even when the page itself rendered quickly.

The person who maintains the theme, the checkout script, or the host can investigate these two waits. The observation does not name the line of code. If you do not know who last changed the page, that owner is unknown.

Shipping retrieval and payment waiting are later steps

WooCommerce shows the methods of the one shipping zone that matches the shipping address, after the address is available. A wait that begins when the address is entered and ends when the methods appear is a shipping-retrieval wait. If the method is a third-party or carrier rate, WooCommerce's zone document points you to that extension's developer. The core zone list does not explain the carrier's response time.

A payment wait starts after a payment attempt exists. WooCommerce can leave an order on hold when the method confirms later, such as a delayed notification method, or when authorization and capture are separate. The order notes and that gateway's documentation are the source. Stripe's PaymentIntent lifecycle uses requires_action when the attempt still needs a step such as authentication, and processing after an asynchronous method such as a bank debit. Stripe says those asynchronous methods can take up to a few days. A succeeded status means that Stripe payment flow is complete. Another gateway's waiting states are unknown until its current document is open.

Do not cache or replay a checkout or payment response to make the step look faster. The result belongs to that address and that attempt.

What the record lets you decide

You can stop a rebuild that does not touch the slow step, and you can send the timestamped step to the party who owns it: the storefront maintainer, the shipping-rate component, or the payment provider named on the attempt. You cannot conclude that the provider will accept the account, or that a faster page will produce more orders. Those outcomes are not in these documents.

Prism can discuss a documented storefront or checkout question in a consultation, including a provider's questions about the website. Scope, fees, and terms are discussed before work. A review is informational and is not a certificate.

Checkout wait location

Time one real session. Do not submit a new payment. Leave a step blank if you did not watch it. Worksheet entries are not submitted by this worksheet or saved by this site. Use only non-sensitive summaries; do not enter credentials, government identifiers, card or bank-account numbers, private receipt links, or customer details.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

Checkout wait location. The last column is for temporary notes.
Visible step	When the clock starts and stops	Who can investigate it	What you saw
Page content appears	From opening the checkout URL until the main content is visible.	The storefront maintainer or host. This is a load observation, not a shipping or bank time.	Page content appears: What you saw
Cart change finishes	From a quantity or line change until the cart shows the new result.	The store platform or the cart extension that performs the update. A cart wait is not a shipping lookup or a payment wait.	Cart change finishes: What you saw
Shipping choices appear	From a usable destination until the shipping methods are listed.	The shipping-zone settings, or the carrier or app that returns the rate. Unknown if you cannot name that component.	Shipping choices appear: What you saw
A field responds	From a tap or keypress in one field until the screen paints the result.	The script on that field. A covered or missing control is an obstacle, not this timer.	A field responds: What you saw
An existing payment attempt	From the attempt you already have until its provider status changes, or until you stop watching.	The payment provider. Stripe processing can last for days on an asynchronous method. Do not create a new attempt to measure this.	An existing payment attempt: What you saw
Device and clock	Device, browser, time zone, and the time you started.	A single session does not set a threshold and does not describe every buyer.	Device and clock: What you saw

These are temporary notes. Leaving or reloading this page may clear them. The consultation form does not include these entries.

Limits

A Prism consultation can help you organize the facts and discuss the website or processing question. The payment provider decides eligibility, pricing, reserves, and whether an account is opened or closed.
This page sets no speed threshold and does not promise more completed orders.
Do not place a new payment to time the last step, and do not cache or replay a checkout or payment response.

Related guides

Sources checked 2026-09-21

Chrome Largest Contentful Paint — checked 2026-09-21. Largest Contentful Paint is the render time of the largest image, text block, or video in the viewport, relative to the navigation.
Chrome Interaction to Next Paint — checked 2026-09-21. Interaction to Next Paint observes the latency of click, tap, and keyboard interactions, from the interaction until the next paint.
WooCommerce shipping zones — checked 2026-09-21. Methods shown are those of the single zone matching the shipping address. A method that is not a core method is likely a third-party extension.
WooCommerce order statuses — checked 2026-09-21. On hold can be used while a delayed payment notification is still pending, or when authorization and capture are separate. Order notes and the gateway's documentation explain that order.
Stripe PaymentIntent lifecycle — checked 2026-09-21. requires_action means more action is needed, such as authentication. processing is used for asynchronous methods, which can take up to a few days. succeeded means that payment flow is complete.
Prism solutions — checked 2026-09-21. Public support is a storefront review, card-processing preparation, or help with a provider's website questions. The provider decides account terms.
Prism contact — checked 2026-09-21. Scope, fees, and terms are discussed before work. The request does not book an appointment or submit a processing application.

Request a consultation

Describe the business and this specific question. Prism follows up by email to discuss fit and scope. An inquiry is not a processing application or an approval.

Request a consultation All resources