Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
The fastest checkout wins on Magento are usually not a new checkout at all: show total costs early, allow guest checkout, add express wallets such as Apple Pay, Google Pay and PayPal, cut unneeded fields and fix slow or broken steps. A Magento one step checkout (an extension or Hyvä Checkout) is worth it when the default two-step Luma checkout is slow, hard to customize or has too many fields for your customers, and when you have measured where shoppers drop off.
This guide gives you a checkout friction audit with fixes ranked by effort, then compares the Luma checkout, Hyvä Checkout and one-step checkout extensions.
Why checkouts lose orders
Baymard Institute's cart abandonment page (last updated September 22, 2025, checked November 2026) documents an average cart abandonment rate of 70.22%, calculated across 50 studies. In its survey of US shoppers, after excluding people who were just browsing, the most common reasons for abandoning during checkout included extra costs being too high (40%), slow delivery (20%), not trusting the site with card details (19%), being asked to create an account (18%), a too long or complicated checkout (17%) and site errors or crashes (17%). Baymard's benchmark also found the average US checkout shows 23.48 form elements by default.
Notice that only some of these reasons are about the number of steps. Costs, trust, delivery and errors matter just as much, which is why a one-step layout on its own rarely fixes a weak checkout.
Checkout friction audit: fixes ranked by effort
Work through this table on mobile and desktop, as a guest and as a logged-in customer. Effort levels are typical for a Magento store; your extensions and theme can move them.
| Friction point | How to check | Fix | Effort |
|---|---|---|---|
| Surprise shipping or tax at the last step | Can a shopper see the delivery cost and total in the cart? | Shipping estimator in cart, clear free-shipping threshold, tax display settings | Low |
| Forced account creation | Is guest checkout enabled? | Enable guest checkout; offer account creation after the order | Low |
| No express wallets | Are Apple Pay, Google Pay or PayPal offered before the form? | Enable express buttons on product, cart and checkout through your payment provider | Low to medium |
| Unneeded fields | Count fields; question company, second address line, phone | Hide or make optional in configuration or layout | Low to medium |
| Poor address entry | Test typing an address on a phone | Address autocomplete, correct input types, postcode lookup where common | Medium |
| Weak trust signals | Are returns, delivery times and security visible near the pay button? | Short reassurance copy, recognizable payment marks, clear returns link | Low |
| Slow steps | Measure Interaction to Next Paint and step load times | Reduce third-party scripts, fix slow shipping-rate and tax calls, cache totals | Medium |
| Errors and validation | Check logs and session recordings for failed submits | Inline validation, clear messages, fix payment and address errors | Medium |
| Hard-to-change layout | How long does a small checkout change take your developers? | Hyvä Checkout or a one-step extension | High |
Do the low-effort rows first and measure. Many stores find their biggest gains before they touch the checkout layout.
Admin settings worth checking first
Several fixes in the table are configuration rather than code. In the Magento admin, review:
- Guest checkout and whether customers are asked to log in before checkout
- Address field options, such as how many street lines are shown and whether company, phone and fax fields are required
- Tax display in the cart and checkout, so totals do not change unexpectedly
- Free-shipping thresholds and the shipping methods shown to each country
- Which payment methods appear, and in what order
These are quick to change and easy to test, so they belong at the start of any checkout project.
Express pay: the quickest structural win
Express wallets let shoppers skip most of the form because the wallet supplies the address and payment details. In Adobe Payment Services, for example, Adobe documents Apple Pay, Google Pay, PayPal, Venmo and Pay Later buttons on the product page, mini cart, cart and checkout, with availability depending on country, onboarding type and device. Other providers offer similar options through their own Magento modules. Our guide to Adobe Commerce payment gateways compares what each provider supports.
Two cautions: test that shipping methods and tax are calculated correctly when the address comes from the wallet, and check that the order data your ERP needs (such as phone number) is still collected.
Luma checkout vs Hyvä Checkout vs one-step extensions
| Factor | Luma checkout | Hyvä Checkout | One-step checkout extension |
|---|---|---|---|
| Layout | Two steps: shipping, then review and payment | One-page or two-page layouts | Single page with all sections |
| Technology | Knockout.js and RequireJS UI components | Server-driven components (Magewire), no Knockout | Usually extends the Luma checkout components |
| Performance | Heavy JavaScript; often slowest part of a Luma store | Lighter front end by design | Similar to Luma, as it builds on it |
| Customization | Possible but complex | Easier for PHP-focused teams | Configurable in admin; deeper changes still Knockout |
| Payment compatibility | Widest; every Magento payment module supports it | Needs a Hyvä Checkout compatible integration per payment method | Most Luma payment modules work; test each |
| Theme | Luma-based themes | Hyvä themes; can also run on non-Hyvä stores through theme fallback | Luma-based themes |
| Licence | Included | Commercial product, separate from the free Hyvä Theme | Commercial, from extension vendors |
When each makes sense
- Keep Luma checkout if the audit fixes above remove your main friction and the checkout performs acceptably.
- Choose Hyvä Checkout if you run or plan a Hyvä theme, want a faster checkout that your team can change easily, and your payment providers have compatible integrations. See what Hyvä is for the wider picture.
- Choose a one-step extension if you want a single-page layout quickly on a Luma theme and accept that the underlying technology stays the same.
How to measure a checkout change
- Track each step as an event: checkout started, shipping submitted, payment submitted, order placed.
- Segment by device, new vs returning, and payment method.
- Record field Core Web Vitals for checkout pages, especially INP (good is 200 ms or less).
- Change one major thing at a time, or run an A/B test where traffic allows.
- Watch payment errors and support tickets for two weeks after any change.
Our guide to ecommerce conversion rate optimization covers testing methods and how to prioritize beyond checkout.
Frequently asked questions
Is a one-step checkout always better?
No. A single page with many fields can feel longer than two short steps. What matters is the number of decisions and fields, total cost clarity and speed.
Can I use Hyvä Checkout without the Hyvä theme?
Hyvä says its checkout can run on non-Hyvä stores through theme fallback. Test your payment and shipping extensions before committing.
Does checkout speed affect conversion?
Slow responses after each click are frustrating at the most sensitive point of the journey. Measure INP and step timings and fix slow server calls first.
Next step
If the audit points to performance, Mistri's Magento performance optimization service covers slow checkout steps and scripts. If it points to a rebuild, our Hyvä theme development team can scope Hyvä Checkout for your payment and shipping setup.
Sources
Cart abandonment rate statistics (Baymard Institute); Payment options (Adobe Payment Services, Experience League); Hyvä Checkout (Hyvä); Interaction to Next Paint (web.dev); Hyvä Checkout documentation (Hyvä Docs).
