Stall library · Buy
The first press of checkout does nothing
This finding means an AI agent pressed your checkout button and nothing happened: the page stayed where it was and no request left the browser. When it pressed the same button a second time, checkout opened. The purchase went on, which is why this is not a stall, but an agent that trusts its first press reports your checkout as broken.
Why the agent stops
Some themes hold the checkout form when it is submitted, to save something first, such as cart attributes for attribution, and then submit it again once that is done. When there is nothing to save, that second submit can run before the browser has finished with the first, and the browser drops it without an error.
It often happens only for some shoppers, such as those who refused cookies or arrived without tracking tags, which is why it can go unnoticed. A person presses again without thinking. An agent waits for the page to change, sees that it did not, and reports the button as one that does nothing.
How often we see this
Not stated here. A frequency means nothing without the cohort it was counted over, and this page is about one stall rather than one category. Where a category has enough stores measured at every stage, the share of them showing this stall is published on its benchmark page, with the methodology beside it.
See it for yourself
- Open your store in a private window, refuse cookies, add a product and open the cart.
- Open the browser’s developer tools on the Network tab and press checkout once.
- If no request appears and the page stays put until a second press, this is the finding.
What to change
- Have the theme submit the form again only once its save has finished, not straight away inside the submit handler.
- Do not hold the submit at all when there is nothing to save.
- Test checkout with cookies refused and no tracking tags in the address, which is how many agents arrive.
What Ottom looks at
The journey agent presses checkout and watches where the browser goes. When it stays on the same page and the checkout button is still there, the agent presses it once more, as a shopper would. This is raised when that second press reaches checkout, once a walk.
Questions
Our checkout works when we test it. Why is this reported?
Because it may only fail for some visitors. On the store this was first found on, the first press worked for shoppers with an analytics cookie and was dropped for those who had refused cookies, which is how an agent arrives. Test with cookies refused.
Why is this rated medium when the purchase went through?
Because an agent that presses once and waits gets nothing, and reports your checkout as not working. It does not lower your score, since checkout is scored by how far the walk got, and benchmarks do not count it as a stall.