Hyvä vs Luma: Which should you choose in 2026?
Hyvä and Luma aren't competing platforms. They're competing frontends for the same Magento backend. The decision is which rendering layer your storefront uses; everything else (admin, products, orders, integrations) stays identical.
By 2026, Hyvä is the default choice for any new Magento build that takes mobile performance seriously. The interesting question isn't "is Hyvä better" — it pretty unambiguously is — but whether the migration cost pays back for your specific situation.
The short answer
Pick Hyvä if you have an existing Magento store with mobile Lighthouse below 70, you're committed to Magento for at least the next 24 months, and your checkout conversion has any room to grow.
Stay on Luma if you're replatforming off Magento within 12 months, you've already sunk heavy custom dev into Luma on a low-traffic store, or your Magento version isn't yet Hyvä-supported.
Everyone else: migrate. The performance gap will keep widening as Google's Core Web Vitals weighting compounds.
What's actually different
| Dimension | Luma | Hyvä |
|---|---|---|
| CSS framework | LESS, BEM patterns | Tailwind utility-first |
| JS framework | Knockout.js + RequireJS | Alpine.js |
| Typical JS payload per page | 2–4 MB | 400–700 KB |
| Typical mobile Lighthouse | 30–55 | 80–92 |
| Render model | Heavy PHP templates + JS bindings | Server-rendered HTML + minimal client JS |
| Extension model | Universal — every Magento extension works | Per-extension Hyvä compatibility module needed |
| License | Free (Magento default) | £1,000–£3,000 per domain, one-time |
| Engineer familiarity | Magento-specific knowledge required | Conventional frontend tools, low ramp-up |
The biggest line in that table is the JavaScript payload row. Magento's default Knockout + RequireJS stack ships several megabytes per page even after gzipping. Hyvä's Alpine + Tailwind stack ships an order of magnitude less. On mobile networks, that's the difference between a usable site and a frustrating one.
The performance gap, in numbers
Across the migrations we've measured:
- Mobile Lighthouse Performance: Luma 30–55 → Hyvä 80–92 (+35 points typical lift)
- Largest Contentful Paint (LCP): Luma 4–7 seconds → Hyvä 1.5–2.5 seconds on mobile
- Total Blocking Time (TBT): Luma 1500–4000ms → Hyvä 100–400ms
- JavaScript payload: ~5x reduction
- Mobile checkout completion rate: typically +8–15% after Hyvä Checkout
These numbers come from our own client work. Your mileage will vary based on extension count and prior-state baselines, but the directional gap is consistent.
Why Luma still exists
Two practical reasons:
Luma is the Magento default. Every Magento installation ships with Luma. It's not a deprecated product Adobe is replacing — it's the baseline that every paid Magento extension targets.
Replacing Luma would break the extension ecosystem overnight. Every paid Magento module ships frontend templates that target Luma's Knockout components and UI Components system. Switching the default would invalidate thousands of paid extensions in the marketplace.
Luma will keep existing for years. Hyvä is increasingly the de-facto choice for any new build, but the Magento default isn't moving.
The migration cost question
A typical Luma → Hyvä migration is £12,000–£35,000 (see our detailed migration cost breakdown for the line-item numbers). The variables:
- Extension count. Each paid extension without vendor-supplied Hyvä compat needs a custom compatibility module — £1,500–£8,000 each.
- Design fidelity. Lift-and-shift faithful rebuild is cheaper. A rebrand bolted on doubles the design work.
- B2B + Adobe Commerce features. Add 2–4 weeks if you have B2B Commerce features (company accounts, shared catalogues, quotes).
For a store doing £1M+ annual revenue with checkout conversion as a meaningful bottleneck, Hyvä typically pays back inside 6–9 months on conversion lift alone.
The migration timeline question
Standard Luma → Hyvä migrations run 6–10 weeks from kickoff to launch. Hyvä Commerce implementations (including Hyvä Checkout) run 10–14 weeks.
The biggest driver is extension count, not catalogue size. A clean Luma store with 8 paid extensions can land in 6 weeks. A heavily customised store with 25 paid extensions pushes into 10–12.
Three scenarios to stay on Luma
We've talked merchants out of Hyvä migrations in these three cases:
Replatforming off Magento within 12 months. If Shopify Plus, BigCommerce, or a custom build is on the roadmap, putting £15–30k into a Hyvä migration first is wasted spend.
Heavily customised Luma frontend on a low-traffic store. Sometimes the existing Luma work is so bespoke that rebuilding under Hyvä costs more than the conversion lift on your traffic level justifies. Under 5,000 monthly sessions, the maths gets tight.
Magento version Hyvä doesn't support yet, with a risky upgrade ahead. Combining a Magento major version upgrade with a Hyvä migration is high-risk. Sequence them: upgrade first, migrate second.
Outside these three, Hyvä is almost always the right call by 2026.
Three scenarios to migrate immediately
Mobile Lighthouse Performance under 50. Every quarter you stay on Luma at sub-50 Lighthouse, you're handing conversion to competitors who already migrated. Google's mobile-first index weights this heavily.
Frontend developer velocity is your bottleneck. If your team takes a week to ship a Luma template change that should take a day, the Knockout learning tax is real. Hyvä's Alpine + Tailwind stack means current frontend engineers are productive on day one.
You're committing to Magento for the long term. If Magento is your platform for the next 3+ years, the Hyvä migration cost pays back in 6–9 months and then keeps compounding.
What about Hyvä Commerce vs Hyvä Theme?
Different question — see Hyvä Commerce vs Hyvä Theme: what's the difference for the breakdown. Short version: Hyvä Theme alone solves the storefront performance problem. Hyvä Commerce adds the one-page Hyvä Checkout (consistently lifts mobile completion 8–15%) plus the modernised admin + customer-account surfaces.
Most merchants start with Theme. Add Commerce when checkout conversion is the bottleneck.
How to decide
A useful five-minute checklist:
- Is your mobile Lighthouse below 70? → migrate
- Is checkout conversion below industry benchmark (mobile completion under 50%)? → migrate, prioritise Hyvä Commerce
- Are you replatforming off Magento within 12 months? → stay
- Is your Hyvä-supported Magento version current? → if no, upgrade Magento first
- Do you have £15–35k of budget + a 6–10 week window? → migrate
Three "yes" answers (in any combination of 1, 2, 4, 5, and a "no" to 3) means it's time. Otherwise, the case for waiting is real.
Next steps
- Read the Magento to Hyvä migration page for the full process
- See How much does a Hyvä migration cost for the line-item budget
- Book a scoping call for a fixed-price quote against your specific store
- Browse the Hyvä Theme glossary entry for the technical context