What is Hyvä Themes?
Short answer Hyvä Themes is a Magento 2 storefront theme built on Tailwind CSS and Alpine.js that replaces the default Luma theme. It drops jQuery, RequireJS and Knockout from the storefront, which is why Hyvä stores load so much less JavaScript than Luma stores. Since November 2025 the theme itself is free and open source. On most stores I move to Hyvä, the real work is not the theme but the extensions, because each Luma extension with front-end code needs a Hyvä compatibility module.
- Replaces the Luma JavaScript stack 01
- Server-rendered HTML, Alpine for interactivity 02
- Extensions need Hyvä compatibility modules 03
- Hyvä Checkout is a separate product 04
- Compatible with Magento 2.4.4+ Open Source and Adobe Commerce 05
Most common mistake Skipping Hyvä Checkout
Five things Hyvä actually changes under the hood
Hyvä is not a new skin on Luma. It replaces the front-end stack Luma has used since Magento 2 launched. This is what changes in practice.
-
01
Replaces the Luma JavaScript stack
Hyvä removes jQuery, RequireJS, KnockoutJS and Magento UI Components from the storefront and uses two tools instead: Tailwind CSS for styling (utility classes, no LESS) and Alpine.js for small interactive parts. The browser downloads and runs far less JavaScript. On Luma stores, that JavaScript is usually what holds mobile performance back, so this is where most of the speed comes from.
-
02
Server-rendered HTML, Alpine for interactivity
PWA Studio is a React single-page app on top of GraphQL. Hyvä is not. Magento still renders the HTML in PHP templates, the same way it always has, and Alpine handles drawers, modals, the mini-cart and quantity steppers. There is no client-side router and no hydration step. When a component needs more state, Magewire (a Livewire-style PHP component layer) handles it on the server.
-
03
Extensions need Hyvä compatibility modules
The first question clients ask is “what about my extensions?” Any extension that ships Luma front-end code (RequireJS, Knockout, jQuery widgets) needs a Hyvä compatibility module to work on the storefront. Many popular extensions already have one, from the vendor or from the Hyvä community, and Hyvä keeps a public tracker of them. Before I quote a migration, I list every installed extension and check it against that tracker.
-
04
Hyvä Checkout is a separate product
The theme and the checkout are separate. Hyvä Themes covers the storefront (category pages, product pages, header, footer, mini-cart) and falls back to Magento’s Luma checkout by default. Hyvä Checkout is a separate licensed module that replaces that checkout with one built on Magewire and Alpine. I always discuss the checkout early, because otherwise the slowest page on the store stays slow.
-
05
Compatible with Magento 2.4.4+ Open Source and Adobe Commerce
Hyvä works on Magento 2.4.4 and later, on both Magento Open Source and Adobe Commerce. It is not a fork of Magento. It is a theme plus a set of modules installed with Composer into a normal Magento install. The admin, product attributes, price rules and B2B setup stay the same. Only the storefront rendering changes.
Four situations where Hyvä is the obvious answer
Hyvä is not the answer for every store, but in these four situations I recommend it without much debate.
-
New Magento builds in 2026
For a new Magento store today, I start on Hyvä by default. Building a new store on Luma means paying for a theme migration later anyway. Starting on Hyvä means the store is fast from launch and the front-end code is simpler to maintain.
-
Existing Luma stores with poor mobile scores
If a Luma store scores badly on mobile Lighthouse, I can usually improve it with caching, image work and JavaScript bundling, but only up to a point. After that you are fighting Luma’s JavaScript stack. A Hyvä migration on the same server, database and catalog removes that limit, which is why it often gives a bigger gain than more tuning.
-
Fashion, electronics, B2B: stores where mobile UX drives sales
Stores where mobile UX drives revenue get the most from it. Fashion has image-heavy category pages and impulse buys, electronics has long product pages and many filters, and B2B has big catalogs and complex product options. If conversion rate is a KPI the client tracks and most traffic is mobile, Hyvä is usually the front-end change I recommend first.
-
Stores preparing for peak season (Diwali, BFCM)
Stores that run Diwali, Black Friday or back-to-school campaigns need pages that stay quick under load. With less JavaScript and server-rendered HTML, mid-range Android phones on mobile data stay responsive, and full-page cache and CDN caching keep working as before. I always plan a Hyvä migration to finish well before peak season, never during it.
Three traps that turn a Hyvä migration into a project rescue
Every overrun Hyvä project I've been called in to rescue made one of these three mistakes early. Avoid them and the migration runs on schedule.
-
Skipping Hyvä Checkout
A Hyvä theme on top of the stock Magento Luma checkout still ships ~250 KB of jQuery + KnockoutJS the moment a customer hits step one. You leave roughly half of the perf win on the table, and worse, the checkout is the page where slow JavaScript hurts conversion most. Always budget Hyvä Themes ($1-2k) plus Hyvä Checkout ($1k) together. Treat them as a single line item, not two separate decisions.
-
Migrating without an extension audit
Most Luma stores carry 20-40 paid extensions accumulated over years. Migrating without first auditing each one against the Hyvä Compatibility Module ships you straight into broken PLPs and missing storefront features in week 6. Always inventory every extension on day one, classify each as native-Hyvä / Compat-Module / replace / drop, and lock the list before any theme work starts. The audit takes 3-5 days and saves weeks of rework.
-
Treating Hyvä as a UI refresh
Hyvä is not a re-skin, it is a frontend stack rewrite. PHTML templates rewritten, LESS dropped for Tailwind, KnockoutJS replaced with Alpine, custom modules ported. Plan for 4-12 weeks of dev time depending on customisation depth, plus QA, plus a soft-launch window. Stores that scope it as a "theme swap" routinely overrun by 2-3x. Brief the project as a frontend rebuild, with a feature freeze on the Luma side for the duration.
Hyvä Themes: frequently asked questions
-
Is Hyvä Themes free?
No. Hyvä Themes is a one-time commercial license, typically $1,000 to $2,000 per project depending on the variant (single-store, multi-store, agency). The license is perpetual: you pay once per major version, not per seat or per month. Hyvä Checkout is a separate $1,000 license. Compared with the conversion lift most stores see (8-25%), the license cost is recouped within the first few months of go-live. -
Does Hyvä Themes work with Adobe Commerce?
Yes. Hyvä is fully compatible with both Magento Open Source and Adobe Commerce (formerly Magento Commerce) on versions 2.4.4 and above, including Adobe Commerce Cloud. You keep all the Adobe Commerce features, B2B, content staging, page builder, customer segments, and only the storefront rendering layer changes. The Hyvä Adobe Commerce license is sold at the same price as the Open Source license. -
Can my Magento extensions still work?
Most of them, yes. Hyvä ships a free Compatibility Module that wraps Luma-only extensions so they render inside a Hyvä storefront. As of 2026, the vast majority of popular paid Magento extensions are either natively Hyvä-compatible (vendor ships Hyvä support out of the box) or covered by the Compat Module. The remaining ~10-20% need either a paid native port from the vendor, a manual port by your dev team, or a swap to a Hyvä-native equivalent. Always run a per-extension audit before migration. -
Is Hyvä the same as headless Magento?
No. Hyvä is server-rendered, not headless. Magento renders the HTML on the PHP side, Hyvä uses Alpine.js for small client-side interactions. Headless Magento, typically PWA Studio with React on top of GraphQL, is a different architecture: separate frontend app talking to Magento purely through API. Hyvä is simpler, cheaper to maintain, and faster on most metrics. PWA Studio is more flexible if you need a single frontend across multiple backends or a native mobile app sharing logic with the web. For most Magento stores, Hyvä is the right answer. -
Does Hyvä support B2B?
Yes. Hyvä works with Magento B2B (Adobe Commerce B2B module): company accounts, requisition lists, quote workflow, shared catalogues, negotiable quotes, all render in the Hyvä storefront. Some B2B-specific UI (the requisition list page, the quote request form) needs Hyvä-native templates if your team has heavily customised the Luma B2B views; the Compat Module covers the unmodified default views. B2B stores often see the biggest performance lift from Hyvä because they tend to have heavy PLPs and large catalogues where every kilobyte of JavaScript hurts. -
How long does Hyvä migration take?
Typical range is 4 to 12 weeks for an existing Luma store, depending on customisation depth and extension count. Lightly customised stores (mostly default Luma + 5-10 extensions) can land in 4-6 weeks. Mid-complexity stores (custom theme + 15-25 extensions + custom B2B flows) take 6-10 weeks. Heavy stores (deeply customised theme + 30+ extensions + bespoke checkout / configurator logic) take 10-12 weeks plus a phased cutover. Brand-new builds on Hyvä are faster because there is no Luma legacy to port: usually 3-6 weeks for a standard store.
Want a Hyvä audit on your Magento store?
Send your storefront URL: I will run a Lighthouse + extension-compat audit and reply with a written migration plan, fixed-price quote, and earliest start date. 24-business-hour turnaround.