What Hyvä actually is — and what it replaces
Hyvä is a replacement frontend for Magento 2. It removes the default Luma-based theme stack — including Knockout.js, RequireJS, jQuery, and the legacy XML layout system — and replaces it with Alpine.js and Tailwind CSS. The result is a dramatically simpler frontend codebase that loads faster and is easier to work with.
Magento's backend, admin panel, APIs, and business logic remain untouched. Hyvä only changes how the storefront is rendered in the browser. Think of it as swapping the exterior of a building while keeping the plumbing, wiring, and foundation intact.
This distinction matters. You are not migrating to a new platform. You are modernising the frontend layer of your existing Magento store. Your catalog, order management, integrations, and admin workflows stay the same. The upgrade path is well-defined and does not require re-platforming decisions.
Since its launch in 2021, Hyvä has been adopted by thousands of Magento stores globally. By 2026, it is the de facto standard for new Magento 2 frontend builds and an increasingly common choice for existing stores undergoing redesigns or performance overhauls.
Why performance gains matter commercially
The primary reason merchants adopt Hyvä is performance. A typical Luma-based Magento 2 storefront loads between 2 and 8 MB of JavaScript. A Hyvä storefront typically loads under 300 KB. That difference is not cosmetic — it directly affects Core Web Vitals scores, mobile usability, and conversion rates.
Google has used Core Web Vitals as a ranking signal since 2021. Stores that score poorly on Largest Contentful Paint (LCP) or Interaction to Next Paint (INP) are penalised in search results. Hyvä stores routinely achieve green scores across all three metrics without heroic optimisation efforts.
For merchants, this translates to measurable business outcomes:
- Higher organic search visibility due to improved page experience signals.
- Lower bounce rates on mobile, where slow load times are most punishing.
- Improved conversion rates, particularly on product listing and product detail pages.
- Better ad performance — faster landing pages mean lower cost per click in Google Ads.
Our work with Sigma Imaging demonstrated this clearly. Performance improvements after a Hyvä migration contributed to measurable gains in both organic traffic and on-site conversion. These are not theoretical benefits — they show up in analytics within weeks of launch.
Developer experience and long-term maintenance costs
Luma's frontend architecture is notoriously difficult to work with. The combination of XML layout files, PHTML templates, Knockout.js bindings, and RequireJS dependency chains creates a steep learning curve. Making even simple frontend changes often requires touching multiple files across several layers.
Hyvä simplifies this radically. Templates use standard PHP and Tailwind utility classes. Interactive elements use Alpine.js, which most frontend developers can learn in a day. The result is that changes take less time, onboarding new developers is faster, and bugs are easier to trace.
This has direct cost implications:
- Frontend development tasks typically take 30–50% less time compared to Luma.
- Fewer developers are needed for ongoing maintenance.
- QA cycles are shorter because there are fewer hidden dependencies between components.
- Technical debt accumulates more slowly because the codebase is smaller and more predictable.
For merchants paying for ongoing development — whether through an agency like Nordic Web Team or an in-house team — this means lower monthly costs and faster time-to-market for new features. Over a two-to-three-year period, the reduced development overhead often exceeds the initial investment in migration.
Compatibility, extensions, and the ecosystem in 2026
The most common concern merchants raise about Hyvä is compatibility. Because Hyvä removes Luma's JavaScript stack entirely, any Magento extension that relies on Knockout.js or RequireJS will not work out of the box. The frontend components of those extensions need to be rebuilt or replaced.
In 2021, this was a genuine barrier. By 2026, the situation has changed substantially. The Hyvä ecosystem now includes a compatibility module library covering over a thousand popular extensions. Major extension vendors — including Amasty, Mageworx, and Smile — ship Hyvä-compatible versions. Payment providers like Klarna, Adyen, and Nets have well-tested Hyvä integrations.
That said, you should audit your current extension stack before committing. The evaluation process typically involves:
- Listing all installed third-party extensions.
- Checking each against the Hyvä compatibility tracker.
- Identifying any custom frontend functionality that needs rebuilding.
- Estimating the effort required for unsupported extensions.
Most stores find that 70–90% of their extensions either work natively or have a Hyvä-compatible alternative. The remaining gaps are usually manageable custom builds. Your agency should be able to provide a detailed compatibility audit as part of the scoping process. We do this routinely for merchants exploring the switch.
When Hyvä is the right choice — and when it is not
Hyvä fits well when you are already running Magento 2 and want to improve frontend performance, reduce development costs, or modernise your storefront without changing your backend infrastructure. It is especially strong for:
- B2C stores where page speed directly impacts conversion.
- Catalog-heavy merchants who need fast browsing across thousands of products.
- Multi-store setups where a simpler theme architecture reduces duplication.
- Merchants planning a redesign — combining visual refresh with a Hyvä migration maximises return on investment.
Hyvä may not be the best fit if your store relies heavily on a fully decoupled or headless architecture with a JavaScript framework like Next.js or Nuxt. In those cases, Magento's GraphQL API layer and a standalone frontend may be more appropriate. Hyvä is a server-rendered approach — it is fast and pragmatic, but it is not headless.
Since November 2025, Hyvä Theme is free and open source, licensed under OSL3 and AFL3. The previous licence fee has been removed. Hyvä also offers commercial add-ons (Hyvä Checkout and Hyvä UI) and a comprehensive Hyvä Commerce suite for merchants who want checkout customisation, CMS with live preview, and an updated admin panel. For most merchants, the zero licence cost combined with lower ongoing development costs makes Hyvä a strong financial case from the first project.
How to plan a Hyvä migration in practice
A Hyvä migration is not a weekend project, but it is far less disruptive than a platform migration. For a typical mid-market Magento 2 store, expect a project timeline of 6–12 weeks depending on complexity, customisation level, and the number of extensions in play.
A practical roadmap looks like this:
- Audit: Review current theme, extensions, and custom frontend code. Identify compatibility gaps.
- Scope: Define what needs rebuilding, what can be replaced, and what works as-is.
- Build: Develop the new Hyvä theme, rebuild custom components, and integrate compatible extensions.
- Test: Run thorough QA across devices, browsers, and user journeys. Validate Core Web Vitals in staging.
- Launch: Deploy with a rollback plan. Monitor performance and conversion data closely for the first two weeks.
Hyvä Theme itself is free and open source. For merchants who want the full Hyvä Commerce suite (including CMS, checkout module, admin panel, and media tools), there is a commercial licence at a flat annual fee with no variable costs tied to traffic or revenue. Details are published on hyva.io.
If you are considering Hyvä as part of a broader Magento upgrade or replatforming evaluation, it makes sense to assess it alongside other infrastructure decisions — hosting, ERP integration, and payment provider choices. These projects compound well when planned together.
Nordic Web Team has delivered Hyvä builds for merchants across B2B and B2C segments. If you want a realistic scoping conversation, we are happy to walk through your current setup and advise on whether Hyvä belongs in your next phase.
