Hyvä vs Luma: Why Hyvä Is the Future of Magento Frontend Development
Hyvä vs Luma compared — JavaScript stack, CSS, performance, developer experience and extension compatibility — plus when Luma still makes sense and how to decide for your Magento 2 store.
Every Magento 2 store owner eventually asks the same question: should we stay on Luma or move to Hyvä? Here's a practical, side-by-side comparison from someone who builds on both.
The short answer
For most stores in active development, Hyvä is the better long-term frontend. It ships far less JavaScript, is easier to develop on, and makes good Core Web Vitals achievable without heroics. Luma still makes sense in a few specific situations — covered below.
How Luma works
Luma is Magento 2's original reference theme. Its frontend stack is:
- RequireJS to load JavaScript modules
- KnockoutJS and UI components for dynamic parts (minicart, checkout, customer data)
- jQuery / jQuery UI widgets
- LESS for styles
It's powerful and deeply integrated, but it loads a large amount of JavaScript on every page, and even small UI changes can mean working through XML layout, UI component configuration and Knockout templates.
How Hyvä works
Hyvä keeps Magento's backend and layout system, but replaces the frontend layer with:
- Alpine.js — a tiny reactive library declared directly in templates
- Tailwind CSS — utility classes, purged at build time so only used CSS ships
- Plain PHTML templates with view models instead of UI-component XML
<!-- Hyvä: a toggle is a few attributes, no separate JS module -->
<div x-data="{ open: false }">
<button type="button" @click="open = !open" :aria-expanded="open">Details</button>
<div x-show="open" x-transition>…</div>
</div>Side-by-side comparison
| Aspect | Luma | Hyvä |
|---|---|---|
| JavaScript | RequireJS + KnockoutJS + jQuery — heavy | Alpine.js — very light |
| CSS | LESS, large compiled stylesheet | Tailwind, purged per build |
| Typical performance | Hard to reach good mobile scores | Good Core Web Vitals are realistic |
| Developer experience | XML + UI components + Knockout templates | PHTML + Alpine + Tailwind |
| Extension compatibility | Works with almost every extension | Needs Hyvä-compatible versions or compat modules |
| Checkout | Built-in Luma checkout | Luma checkout fallback or Hyvä Checkout |
| Licensing | Included with Magento | Check hyva.io for current licensing of the theme and add-ons |
Why Hyvä wins for most stores
Performance that affects revenue
Page speed influences conversion and SEO. Because Hyvä removes most of Luma's JavaScript, pages become interactive sooner — especially on mid-range mobile devices, where most traffic lives.
Faster development
Changes that take an afternoon of Knockout and XML in Luma are often a few lines of Alpine in Hyvä. That lowers the cost of every future feature, not just the migration.
A healthy ecosystem
Most major extension vendors now ship Hyvä support, and compatibility modules cover many others. That's the biggest change from Hyvä's early days.
When Luma still makes sense
Hyvä isn't always the right call
Moving frontends is an investment. Sometimes staying on Luma is the pragmatic choice.
- Many frontend extensions without Hyvä support — porting them can outweigh the benefit.
- A planned replatform or headless rebuild — don't migrate a frontend you'll replace soon.
- Very low traffic, very few changes — the ROI may not be there yet.
- Going headless instead — if you're building a React/PWA storefront on custom GraphQL, Hyvä isn't needed.
How to decide
- Audit your extensions — list every module that touches the frontend and check Hyvä compatibility.
- Measure your baseline — Lighthouse and real-user (CrUX) data for home, category, product and cart.
- Estimate the porting work — custom templates, widgets and checkout customisations.
- Compare against the roadmap — how many frontend changes do you expect in the next 12–24 months?
If the audit looks good, follow a structured migration — I've written a step-by-step Luma to Hyvä migration guide.
Thinking about Hyvä for your store? I offer Hyvä theme development and Luma-to-Hyvä migrations — send me your store URL and I'll tell you honestly whether it's worth it.
