Magento checkout conversion-rate optimization is the audit-and-fix discipline that targets the twelve highest-impact UX defects in Magento 2's default checkout, Luma or Hyvä, using Baymard Institute's checkout usability research as the evidence base in 2026. Not generic "simplify checkout" advice, twelve Magento-specific defaults that hurt conversion, paired with the exact etc/checkout_index_index.xml, etc/config.xml, or theme override that changes each one.
What Baymard's research says better checkout design is worth.
Baymard's research finds that the average large-scale ecommerce site can potentially gain a 35% increase in conversion rate through better checkout design (Baymard)[1]. Its average documented cart abandonment rate is 70.22%, across 50 studies (Baymard)[2]. Magento 2.4.x's default checkout hits eleven of the twelve most-cited friction patterns Baymard catalogues. The file paths below are the same paths I edit on every checkout sprint at kishansavaliya.com.
The 12 points at a glance
| # | Friction point | Magento default | Why it matters | Fix effort |
|---|---|---|---|---|
| 1 | Email field ordering | Combined / inline with password | Email first, on its own | S |
| 2 | Guest vs account-first | Forces choice before email | 18% abandon over forced account creation (Baymard) | S |
| 3 | Address autocomplete | Off, no API key | Less typing, fewer address errors | M |
| 4 | One-page vs multi-step | Single accordion on Hyvä | Rarely the bottleneck < 30k SKU | S |
| 5 | Trust badges placement | Footer / header only | Badges where the customer pays | S |
| 6 | Shipping cost transparency | Revealed at step 3 | 40% abandon over extra costs (Baymard) | M |
| 7 | Discount-code visibility | Collapsed accordion | An open field sends shoppers hunting for codes | S |
| 8 | Field count | 14 visible fields | Target 8 visible fields | M |
| 9 | Mobile keyboard types | All type="text" | Right keyboard per field | S |
| 10 | Tax display | Excluded by default in EU | No late price increase | S |
| 11 | Save cart for later | Persistent cart cookie only | Recovery emails need the cart | M |
| 12 | Place-order button | Half-width on mobile | Easy to find and tap | S |
S = < 1 hour, M = 1-4 hours, L = 4-12 hours. The full set lands in roughly 18-24 hours on a stock Magento 2.4.9 + Hyvä build.
1. Ask for the email first, on its own, before any password or account choice.
Put the email field on its own, before any account-vs-guest decision, rather than combining it with a password or an account-first step; A/B test it against your current form. The customer perceives the email field as continuation of the cart action, not as account commitment.
Magento 2.4.x defaults to combined email-and-password for logged-out customers. Hyvä opens with email but the inline password trigger sits right there, framing-wise the same.
<!-- view/frontend/layout/hyva_checkout_components.xml override -->
<component name="checkout.shipping.email"
template="Vendor_Theme::magewire/checkout/email-first.phtml"
sortOrder="10"
parent="checkout.shipping"/>
<component name="checkout.shipping.account-toggle"
template="Vendor_Theme::magewire/checkout/account-toggle.phtml"
sortOrder="20"
parent="checkout.shipping"/>Email goes alone in sortOrder 10. The account-vs-guest toggle moves to 20, after the customer has typed an email. On Luma the same change happens in checkout_index_index.xml, override jsLayout.components.checkout.children.steps.children.shipping-step.children.customer-email to sortOrder="10".
2. The guest-vs-account choice should never come before the email field.
In Baymard's survey of reasons for abandonment, 18% of shoppers said the site wanted them to create an account (Baymard)[2]. Magento 2 forces the choice as the first interaction when account registration is on. The fix: default to guest, surface account creation as a checkbox on the order-success page ("Save my details for next time?").
<!-- etc/config.xml -->
<config>
<default>
<checkout>
<options>
<guest_checkout>1</guest_checkout>
<customer_must_be_logged_in>0</customer_must_be_logged_in>
</options>
</checkout>
<customer>
<create_account>
<auto_group_assign>1</auto_group_assign>
<default_group>1</default_group>
</create_account>
</customer>
</default>
</config>Then add an observer on checkout_submit_all_after that creates the account post-order if the customer ticked "Save my details" on the success page. This keeps account sign-ups without the front-loaded friction; compare the sign-up rate before and after.
3. Address autocomplete is the highest-ROI single change on Magento checkout.
Address autocomplete (Google Places, Loqate, Algolia Places) cuts typing and form time and tends to help completion; A/B test it on your store. Magento 2.4.x ships zero autocomplete, every customer types every line manually.
The cost: one API key, two days on Luma (Knockout) or four hours on Hyvä (Alpine.js). Google Places is ~$2.83 per 1,000 sessions; a 500-orders-per-day store pays ~$1.40 per day.
<!-- Hyvä Magewire template -->
<input type="text"
id="shipping-street-1"
wire:model.lazy="address.street.0"
x-data="placesAutocomplete"
x-init="init($refs.streetInput)"
x-ref="streetInput"
autocomplete="address-line1"
class="block w-full rounded-md border-gray-300" />The Alpine.js component debounces 300ms and writes parsed components to the Magewire model. Quote::collectShippingRates fires once per address change, autocomplete cuts friction and server load. Typed addresses also fail validation more often, re-rendering the shipping step; autocomplete kills that tail.
4. One-page versus multi-step is a wash for stores under 30k SKUs.
Under 30k SKUs and under 4 line items average, one-page vs multi-step rarely decides the result either way. Above 30k SKUs or B2B carts of 10+ items, multi-step tends to work better. Hyvä's three-step accordion is the right default for most stores.
<!-- view/frontend/layout/hyva_checkout_components.xml -->
<component name="checkout.shipping" sortOrder="10"/>
<component name="checkout.payment" sortOrder="20"/>
<component name="checkout.review" sortOrder="30"/>Keep the default. Invest the saved hours in points 1, 3, 6, 8, each pays back more.
5. Put trust badges under the place-order button, not in the header or footer.
SSL seals, money-back guarantees, and payment-card logos placed directly under the place-order button tend to do more than the same badges in the header or footer; A/B test the placement. The customer questions trust at the moment of payment commitment, not page arrival.
Magento 2 ships zero badges in the checkout block by default. Add a Hyvä container after checkout.payment.methods:
<!-- view/frontend/layout/hyva_checkout_components.xml -->
<component name="checkout.payment.trust-badges"
template="Vendor_Theme::magewire/checkout/trust-badges.phtml"
sortOrder="500"
parent="checkout.payment"/><!-- magewire/checkout/trust-badges.phtml -->
<div class="mt-3 flex flex-wrap items-center justify-center gap-3 text-xs text-gray-600">
<span class="inline-flex items-center gap-1"><svg>...</svg> 256-bit SSL</span>
<span class="inline-flex items-center gap-1"><svg>...</svg> 30-day returns</span>
<img src="/static/icons/visa.svg" alt="Visa" width="32" height="20" />
<img src="/static/icons/mastercard.svg" alt="Mastercard" width="32" height="20" />
</div>Three rules: SVG or inline (no external CDN that slows LCP), brand-voice (no stock "100% SECURE" banners), and the seal must reflect actual certificate coverage.
6. Hiding shipping cost until step 3 is the single biggest abandonment driver.
In Baymard's survey of reasons for abandonment, extra costs (shipping, tax, fees) are the top reason: 40% name them, against 20% for slow delivery, the next reason (Baymard)[2]. The signal is not that shipping is too expensive; it is that the cost is revealed too late, after the customer has spent cognitive load on the address form.
Magento 2.4.x's default cart shows a zip-only shipping estimator that many stores leave disabled. Enable it. Better: show actual cost on the product page when the customer's IP geolocates to a predictable region.
<!-- Admin: Stores → Configuration → Sales → Checkout -->
<config path="carriers/flatrate/show_method">1</config>
<config path="checkout/cart/estimate_shipping">1</config>
<config path="checkout/cart_link/use_qty">1</config>On Hyvä the shipping estimator is a Magewire component, expand it by default with the country pre-filled from Cloudflare's X-Geo-Country or MaxMind GeoIP2. Customer commits early or leaves early, both save checkout-page server load.
7. Keep the discount-code field collapsed, not always visible.
An always-visible "Discount code" field can send the customer off to hunt for a code. A collapsed field with a small "Got a code? Apply it" link avoids that; A/B test it and watch AOV.
Magento 2.4.x's default coupon block is collapsed correctly. The mistake is theme overrides that always-expand it "for visibility". Verify no theme override forces checkout.review.discount-code open.
<!-- Hyvä check: ensure this attribute stays at default -->
<div x-data="{ open: false }">
<button @click="open = !open" class="text-sm underline">Got a code? Apply it</button>
<div x-show="open" x-collapse>
<input wire:model.lazy="couponCode" />
<button wire:click="applyCoupon">Apply</button>
</div>
</div>Bonus pattern: if a customer arrives with ?coupon=SAVE10, auto-apply server-side and skip the field. An auto-applied code avoids the empty field that sends shoppers hunting.
8. The 14-field Magento default should be 8 fields, and 6 of those should be auto-filled.
Every field the customer has to fill adds work, and drop-off tends to rise with it. Magento 2.4.x's default shipping form has 14: First Name, Last Name, Company, Street 1/2/3, City, State, Postal Code, Country, Phone, Email, plus two checkbox toggles. Six fields too many.
Per-field: Company hides unless customer-group is B2B; Street 2/3 collapse behind "+ Add apartment"; State derives from postal code via point 3's autocomplete; Country defaults from IP, hidden until "Ship to another country"; Phone is optional unless shipping is express.
<!-- etc/config.xml -->
<config>
<default>
<customer>
<address>
<street_lines>1</street_lines>
<telephone_show>opt</telephone_show>
<company_show>no</company_show>
<fax_show>no</fax_show>
</address>
</customer>
</default>
</config>A hyva_checkout_components.xml override renders the hidden fields on toggle. Visible form drops from 14 to 8; hidden fields stay in DOM for B2B but cost most customers nothing.
9. Give every mobile field the right keyboard type.
Mobile completion tends to improve when inputs declare the right inputmode or type so the mobile keyboard surfaces the correct character set. Magento 2.4.x defaults all fields to type="text", every field gets QWERTY, even postal code and phone.
The fix is one-line attribute additions per field:
<input type="email" name="email" inputmode="email" autocomplete="email" />
<input type="tel" name="telephone" inputmode="tel" autocomplete="tel" />
<input type="text" name="postcode" inputmode="numeric" autocomplete="postal-code" pattern="[0-9A-Za-z -]*" />
<input type="text" name="street" inputmode="text" autocomplete="address-line1" />
<input type="text" name="cc-number" inputmode="numeric" autocomplete="cc-number" pattern="[0-9 ]{13,19}" />Magento 2's default templates omit inputmode on postal code and credit card. Add in Hyvä at view/frontend/templates/magewire/checkout/shipping/address-form.phtml or override the Luma customer/widget/name.phtml family. autocomplete matters too, mobile browsers use it to populate the form from the device profile.
10. EU stores must display VAT-inclusive prices throughout checkout.
Showing tax-excluded prices to EU consumers, then adding 19-25% VAT at review, tends to raise abandonment compared with VAT-inclusive display throughout. Same signal as point 6, a late price increase makes the customer question the whole purchase.
Magento 2.4.x ships VAT excluded by default. The config flags to flip for EU stores:
<!-- Admin: Stores → Configuration → Sales → Tax -->
<config path="tax/display/type">2</config> <!-- Including Tax -->
<config path="tax/cart_display/price">2</config>
<config path="tax/cart_display/subtotal">2</config>
<config path="tax/sales_display/price">2</config>
<config path="tax/sales_display/subtotal">2</config>
<config path="tax/sales_display/grandtotal">1</config>For multi-store EU/US setups, scope per website or store_view via app/etc/config.php. US stays VAT-excluded (US convention), EU flips to inclusive, same codebase, store-scoped config.
11. Save-cart-for-later persistence is what makes abandoned-cart emails work.
A recovery email only works if the cart is still there: the email is worthless if the customer arrives back at an empty cart. Track how many recovery emails lead to a completed order.
Magento 2.4.x's persistent-cart cookie lives 24 hours by default. Bump to 30 days for known emails (past point 1) and ensure the cart is serialized to the database, not just the cookie. Hyvä respects this out of the box.
<!-- etc/config.xml -->
<config>
<default>
<persistent>
<options>
<enabled>1</enabled>
<lifetime>2592000</lifetime> <!-- 30 days -->
<remember_enabled>1</remember_enabled>
<remember_default>1</remember_default>
<clear_on_logout>0</clear_on_logout>
</options>
</persistent>
</default>
</config>Wire the abandoned-cart cron at 1h, 24h, 72h. Track the recovery rate of each send; anything after 72h rarely earns its place. Open Source needs a third-party (Mageplaza, Amasty); Adobe Commerce includes Magento_AbandonedCart.
12. The place-order button must be full-width and primary-colored on mobile.
A full-width primary-colored place-order button on mobile is easier to find and tap than a half-width or neutral one; A/B test it on your store. It is the single most-clicked element in checkout; visual treatment matters more than any other UI element.
Magento 2.4.x's Luma button is full-width on mobile via the grid but defaults to neutral gray on most themes. On Hyvä with Tailwind it is properly styled but theme overrides often shrink it.
/* view/frontend/web/tailwind/tailwind-source.css */
.checkout-place-order-button {
@apply w-full;
@apply rounded-md;
@apply bg-primary;
@apply px-6 py-4;
@apply text-base font-semibold text-white;
@apply shadow-md transition-colors;
@apply hover:bg-primary-dark;
@apply focus:outline-none focus:ring-4 focus:ring-primary/30;
@apply disabled:cursor-not-allowed disabled:opacity-60;
}
@media (min-width: 768px) {
.checkout-place-order-button {
@apply w-auto min-w-[16rem];
}
}Three sub-rules: 44x44 px minimum touch target (Apple HIG); never use plain "Submit", use "Place Order, $147.40" with total baked in; never disable on API wait, show a spinner inside the button. Customers tap a disabled button five times; they tap a spinner once.
Measurement: three layers I track on every audit
Twelve changes without measurement is twelve guesses. Three layers run on every Magento checkout sprint at kishansavaliya.com: per-step GA4 funnel events (checkout_step_view with step_index) for drop-off; web-vitals.js INP measured on the place-order button (a slow INP on the most-tapped element hurts conversion); and sequential A/B tests via store-view cookie assignment, two weeks per test, never concurrent.
A six-week order of work
Spread the work across six weeks: points 1, 2, 8, 9 first; then 3 and 6; then 5 and 12; then 7, 10, 11; check that point 4 is already correct. Measure checkout conversion, mobile conversion, cart abandonment, average order value and checkout time against the baseline you captured first, one change at a time.
FAQ
Does this apply to Adobe Commerce as well as Magento Open Source?
Yes. Eleven of the twelve points apply identically; point 11 (save cart for later) needs a third-party module on Open Source but ships out of the box on Adobe Commerce.
Will any of these break PCI compliance?
No. None of the twelve touch the payment-form iframe or change which fields are stored. Trust-badge placement is visual only.
Can I run all twelve fixes at once?
You can ship them, but do not measure them simultaneously. Sequential A/B testing per fix is the only way to know which fix moved the needle.
Does this work on PWA Studio or headless?
Points 1, 2, 4, 6, 7, 10, 11 are server-side or config and apply identically. Points 3, 5, 8, 9, 12 are frontend-implementation and need re-implementation in React or Vue. Baymard's data does not change, only the file paths do.
How do I prioritize if I only have 8 hours?
Points 1 (email-first), 2 (no account gate), 8 (field count), and 9 (mobile keyboards). Those four are quick to ship and tend to remove the most friction; A/B test them one at a time.
Citations
- [1] Baymard Institute, Checkout Usability, baymard.com/checkout-usability
- [2] Baymard Institute, Cart Abandonment Rate, baymard.com/lists/cart-abandonment-rate
- Adobe Commerce DevDocs, Checkout Configuration & Layout, developer.adobe.com/commerce/frontend-core
Related reading
- Add a custom field in Magento checkout (Luma + Hyvä)
- Magento Core Web Vitals, the actual LCP, INP & CLS recipe
- Hyvä theme development service
- Magento 2 development service
I ship the twelve-point audit (Luma or Hyvä), the measurement layer, and the first six weeks of sequential A/B tests on a fixed-quote sprint. Fixed written quote after a short brief. See /hire-me or message me at wa.me/918401270422.
Tagged #Checkout #Hyvä #Baymard #Conversion Rate #UX
Written by
Kishan Savaliya
Adobe-certified Magento 2 + Hyvä developer. 60+ open-source extensions published. Founder of Panth Infotech.
Adobe Certified since 2021Hyvä and Luma
All posts by Kishan Savaliya