The checkout that only breaks on phones

What breaks on small screens

A cookie banner, a chat bubble or a newsletter pop-up that sits in a corner on desktop can cover the entire “Place order” button on a phone. A sticky header can hide the error message that tells the customer what is wrong with their address.

The on-screen keyboard pushes fields out of view, and a layout that relies on hover never shows a tooltip on touch. None of it breaks a desktop test, and all of it stops a real purchase.

Wallets are mobile-first

Apple Pay and Google Pay buttons only appear on supported devices and browsers. If the wallet script fails or the domain verification lapses, the button silently disappears — and the customers who would have paid in one tap now face a card form.

Nothing errors on the page. It simply shows one less way to pay, which is the kind of failure that never reaches a support inbox.

Test like a customer

After every release, walk through checkout on an actual phone, as a guest, on mobile data if you can. Check that every button can be tapped, that errors are visible, and that the wallet buttons you expect are there.

For continuous coverage, run a scheduled checkout check with a mobile viewport alongside the desktop one. When the two disagree, you have found a layout problem before your customers did. Related: missing Apple Pay and Google Pay buttons and a slow checkout.

Check your own store now, free: the WooCommerce checkout checker or the Magento checkout test walks the checkout in a real browser and shows the step where it stops.