For most US Magento 2 merchants, Hyva is the better frontend when your store is chasing Core Web Vitals, mobile conversion, and lower long-term frontend cost. Luma only stays the right call when deep custom-module dependencies or a tight budget make a migration cycle impractical this year. This guide shows you how to decide.
The Hyva-versus-Luma question changed in November 2025. Hyva Theme became fully free and open source, so the license fee that used to sit on top of every migration is gone. That removes one of the last reasons a US merchant would default to staying on Luma. What is left is a straightforward engineering and business decision: what does each frontend cost you in speed, revenue, and maintenance over the next three years.
We are Bemeir, a Brooklyn ecommerce agency and the first US-based Hyva Gold Partner. We build, migrate, and support both Luma and Hyva stores every week, so this guide is written from shipped work, not theory.
What Luma and Hyva Actually Are
Luma is Magento 2’s original frontend theme. It is built on Knockout.js, RequireJS, jQuery, and LESS. That stack was reasonable when Magento 2 launched in 2015, but it ships a large amount of JavaScript to the browser and executes much of it before a shopper can interact with the page. On a typical product detail page, a Luma store parses somewhere in the range of 700 KB to over 1 MB of JavaScript.
Hyva is a modern replacement frontend for the same Magento 2 or Adobe Commerce backend. It throws out Knockout, RequireJS, and most of the jQuery layer and rebuilds the storefront on Tailwind CSS and Alpine.js. The result is a page that ships roughly 50 to 100 KB of JavaScript instead of a megabyte. Crucially, Hyva runs on the same Magento backend, database, admin, and extensions ecosystem. You are replacing the storefront layer, not replatforming your business.
That distinction matters for how you scope the project. A Luma-to-Hyva migration is a frontend rebuild. A move to headless or PWA Studio is a full architecture change. They are not the same size of undertaking, and confusing the two is the most common budgeting mistake we see. Our Hyva development services page covers where the line sits.
The Performance Gap, in Numbers
The reason merchants migrate is measurable, not cosmetic. Google confirmed Core Web Vitals as a ranking factor, and the two metrics that hurt Luma stores most are Largest Contentful Paint (LCP) and Interaction to Next Paint (INP), both driven by JavaScript execution time.
Hyva’s own published figures, from hyva.io, state that a Hyva page cuts the number of HTTP requests by around 98 percent and reduces page weight by around 86 percent compared to a default Luma page. Those are vendor numbers, but they align with what we see in the field.
| Metric | Typical Luma store | Typical Hyva store |
|---|---|---|
| JavaScript shipped (PDP) | 700 KB to 1.2 MB | 50 to 100 KB |
| Mobile PageSpeed score | 30 to 60 | 85 to 98 |
| Mobile LCP | 3.5 to 5.0 seconds | 1.2 to 1.8 seconds |
| Cumulative Layout Shift | often above 0.10 | often near 0.02 |
| HTTP requests per page | high | roughly 98% fewer (hyva.io) |
| Passes Core Web Vitals | inconsistent | far more often |
Treat these as ranges, not promises. Your real result depends on hosting, image discipline, third-party scripts, and how many extensions inject their own JavaScript. A store carrying five heavy marketing tags will not hit a 98 unless those tags are also cleaned up. That is exactly the honest analysis our guide on how to fix Magento Core Web Vitals walks through page by page.
When Hyva Is the Right Call
Hyva is the right decision for a US merchant when most of the following are true:
- Your mobile PageSpeed score sits below 50 and mobile is more than half your traffic.
- Your field Core Web Vitals in Google Search Console are failing on product or category templates.
- You plan to keep investing in this Magento store for at least two more years.
- Your frontend backlog keeps stalling because Luma customizations are slow and expensive to change.
- You want lower frontend maintenance cost going forward, since Tailwind and Alpine are cheaper to hire for than Knockout.
The now-free license changes the math in Hyva’s favor. Before November 2025, a small merchant had to weigh a per-store license fee against uncertain gains. That fee is gone. The remaining cost is engineering, and engineering pays back through faster pages, better rankings, and higher conversion.
When Luma Is Still the Right Call
We do not migrate every store, and you should be suspicious of any agency that says you must. Staying on Luma is defensible when:
- You have deep custom modules that hook directly into Luma templates and phtml files, and rewriting them would dominate the budget.
- You are on an older Magento core (below 2.4.4) and a required core upgrade would need to come first.
- Your budget this year cannot absorb a migration cycle, and a targeted Luma performance pass can get you an acceptable score for now.
- You are planning to replatform entirely within twelve months, in which case a Hyva migration would be throwaway work.
For that middle group, there is a real interim option: optimize Luma. Deferring unused JavaScript, fixing image sizing and preload, trimming third-party tags, and tuning full-page cache can move a Luma store from the 30s into the 60s on mobile. It will not reach Hyva territory, but it buys time. The honest framing is that Luma optimization is a bridge, and Hyva is the destination.
Cost and Timeline for US Merchants
Migration cost is driven almost entirely by extension and customization complexity, not by page count. The theme itself is now free. What you pay for is the work of making every extension and custom feature render correctly on the new frontend.
| Store profile | Typical timeline | Typical US cost range |
|---|---|---|
| B2C, fewer than 10 extensions | 4 to 6 weeks | $15,000 to $35,000 |
| Mid-market, 10 to 25 extensions | 6 to 10 weeks | $35,000 to $70,000 |
| Adobe Commerce B2B (company accounts, shared catalogs, quotes) | 12 to 16 weeks | $60,000 to $90,000+ |
| Add a required Magento 2.4.x core upgrade | add 2 to 4 weeks | add to the above |
These are practitioner ranges for the US market, where blended agency rates are higher than offshore shops. The single biggest variable is your extension list. Every third-party module that touches the frontend needs a Hyva-compatible version, a community port, or a custom rewrite. The first thing any credible agency should do is audit your extensions against the Hyva compatibility list before quoting. Our full breakdown of phases, dependencies, and cost drivers lives in the Luma to Hyva migration playbook.
B2B on Hyva: The Question Most Comparisons Skip
Most Hyva-versus-Luma articles quietly assume a simple B2C catalog. US mid-market and wholesale merchants are usually on Adobe Commerce B2B, and they need to know whether company accounts, shared catalogs, requisition lists, quick order, and negotiable quotes work on Hyva. They do. Hyva supports Adobe Commerce B2B features, but the implementation is more involved than a B2C storefront because those workflows are heavier and some rely on the same legacy Knockout components Hyva is replacing.
In practice this means B2B migrations sit at the longer end of the timeline and need explicit testing of the quote and requisition flows. Do not accept a B2B Hyva quote that treats those features as a rounding error. They are the project. This is a Magento capability question as much as a theme question, and our Magento development services team scopes B2B migrations feature by feature rather than as a flat storefront rebuild.
How to Choose Your Migration Partner
Because Hyva is now free, the differentiator is no longer license access. It is who does the migration. A few things to check:
- Ask whether they are an official Hyva Partner and how far back their Hyva experience goes. The theme is five years old; agencies that have shipped Hyva since the early releases have hit edge cases newcomers have not.
- Ask to see their extension-audit process before any quote. A partner who quotes without auditing your modules is guessing.
- For B2B, ask specifically how they test company accounts and negotiable quotes on Hyva.
- Ask for US timezone support if your team runs on Eastern or Pacific hours. Offshore-only support during a live migration creates real risk.
As the first US-based Hyva Gold Partner, we have a direct line to the Hyva core team, which matters when a niche extension or a B2B flow needs an answer the docs do not cover. You can read more about that on our About Bemeir page.
Frequently Asked Questions
Is Hyva theme free now?
Yes. On November 10, 2025, Hyva Theme became fully free and open source under the OSL 3.0 and AFL 3.0 licenses, the same license family as Magento Open Source. The former per-store license fee is gone. Hyva UI, a separate component library, remains a paid product, but the core theme carries no license cost.
Do I lose my extensions when I migrate from Luma to Hyva?
No. Backend extension logic stays intact because Hyva runs on the same Magento backend. What changes is the frontend rendering. Extensions that only touch backend behavior work unchanged. Extensions that render on the storefront need a Hyva-compatible version, a community port, or a custom rewrite, and that work is the main cost of the migration.
How much faster is Hyva than Luma in real terms?
Expect mobile PageSpeed scores to move from the 30 to 60 range into the 85 to 98 range, and mobile LCP to drop from roughly 3.5 to 5 seconds down toward 1.2 to 1.8 seconds. The exact result depends on hosting, images, and third-party scripts. Hyva reports around 98 percent fewer HTTP requests and 86 percent less page weight versus a default Luma page.
Should I migrate to Hyva or go fully headless?
For most Magento merchants, Hyva delivers the large majority of headless performance at a fraction of the cost and timeline, while keeping the standard Magento admin and templating your team already knows. Headless or PWA Studio makes sense only when you have a specific need for a decoupled frontend, such as a shared frontend across multiple channels. Hyva is the default; headless is the exception.
Can I optimize Luma instead of migrating?
Yes, as a bridge. Deferring unused JavaScript, fixing image preload and sizing, trimming marketing tags, and tuning full-page cache can move a Luma store from the 30s into the 60s on mobile. It will not match Hyva, but it is a reasonable interim step if your budget or timeline rules out a migration this year.
How long does a Luma to Hyva migration take?
A straightforward B2C store with fewer than 10 extensions typically takes 4 to 6 weeks. A mid-market store with 10 to 25 extensions runs 6 to 10 weeks. A full Adobe Commerce B2B migration takes 12 to 16 weeks. Add 2 to 4 weeks if a Magento core upgrade to 2.4.x is required first.
