On This Page
- Luma and Hyvä: Understanding the Key Differences
- Why Extension Compatibility Matters When Switching to Hyvä
- How Hyvä Checkout Affects Store Functionality
- Payment Options and Gateway Compatibility
- How Hyvä Impacts Discounts and Coupon Functionality
- Should You Migrate from Luma to Hyvä?
- Key Takeaways: Hyvä vs Luma
- Frequently Asked Questions -
Get in Touch
Most Magento store owners start the Hyvä vs. Luma conversation with one question. “Will my store get faster?”
It will, usually. But that’s only half the story. The other half is your extensions. Your payment gateway, your discount tools, your currency switcher. If those don’t play well with the new theme, the speed gain matters little because checkout breaks and customers leave.
So let’s talk about that part. The part people skip.
Luma and Hyvä, in plain words
Luma is the default Magento theme. It has been around for years, and almost every Magento extension ever built works with it. That’s its biggest strength.
The downside is weight. Luma leans on older front-end tools like RequireJS, Knockout, and jQuery. They load a lot of JavaScript, and on a slow phone you feel it. Pages crawl. Checkout feels heavy.
The Hyvä theme takes a different road. It’s built on Tailwind CSS and Alpine.js, so there’s far less code to download and run. Stores that move to it often see a big jump in speed and Core Web Vitals. If you want the details on how that plays out on product pages, our Magento Hyvä product page performance checklist walks through it step by step.
Sounds like an easy win. It’s not always.
Why extensions are the real catch
Here’s the thing. Many extensions were written for Luma. They use its JavaScript tools to draw buttons, forms and popups. Hyvä doesn’t use those tools. So an extension built the old way can show up broken, or not show up at all.
That doesn’t mean the extension is bad. It just speaks a different language than the theme.
The fix is usually a compatibility module. Some extension makers build one, and the Hyvä community has made many for popular ones. Sometimes a developer has to write the bridge by hand. That takes time and money, and you want to know about it before you start, not halfway through the project.
A quick example. Say you run a store with five extensions and three of them touch the frontend. You move to Hyvä, and two of those three work fine. The third one, say a loyalty widget, simply vanishes from the cart page. Nobody notices for a week. Then your support inbox fills up.
That’s why we always say: list your extensions first. Then decide.
Checkout is where it gets serious
A broken banner is annoying. A broken checkout costs you money, straight away.
Hyvä Checkout is a separate piece from the Hyvä theme, and it’s built for speed and a cleaner flow. Fewer steps, less clutter. But checkout is also where most of your important extensions live. Payment methods, shipping rules, discounts, tax tools, order notes.
So the real question isn’t “Is Hyvä checkout faster than the Luma one?” It is. The real question is “Will everything I need at checkout still work there?”
Go through your checkout like a customer. Add something to the cart. Apply a cart discount. Pick a payment method. Change the currency. Place a test order. Do it on a phone too, not just your laptop. If anything feels off, write it down. That list becomes your migration to-do list.
Payment options deserve extra care
Payments are the one thing you can’t afford to get wrong. A theme can look a bit off for a few days and you’ll survive. A payment method that fails at the last click? Not so much.
Let’s go through a few common cases.
Say you want to control which checkout payment methods show up for which customers. Maybe cash on delivery should be hidden for big orders, or a certain method only for wholesale buyers. Magento can’t really do this on its own. The Magento 2 Payment Restrictions extension handles it with rules based on product attributes, customer groups, shipping address and cart items. Its product page also lists Hyvä theme compatibility, which is exactly the kind of detail you should look for before you buy anything.
Now say you take card payments in the US and want a gateway that doesn’t give you headaches. The PayTrace payment gateway for Magento 2 is built for that. Elsner is an official PayTrace partner, and the integration is verified by PayTrace with PCI standards in mind. It also supports saving cards securely. Good stuff. Still, if you’re heading to Hyvä checkout, ask us to confirm how it fits your exact setup. Better to ask than to guess.
And if you sell to people in different countries, the PayPal multicurrency extension lets shoppers pay in their own currency through PayPal Standard or PayPal Express. Multi-currency checkout sounds like a small thing, but it isn’t. People trust a price in their own money far more than one they have to work out in their head.
None of these are magic. They’re just examples of how many moving parts sit around one little “Place order” button.
Discounts can break quietly
This one catches people off guard.
Cart discount tools and other ecommerce discounts often change how the cart total is calculated and shown. On Luma, that’s all handled by the older scripts. On Hyvä, the display layer is different. So a discount might apply correctly in the background but show the wrong number on screen. Or the coupon box might not update until you refresh.
The customer sees a wrong total and thinks, “Hmm, is this site safe?” Then they close the tab.
So test every discount type you run. Percentage, fixed amount, free shipping, buy-one-get-one. All of it. Test with a logged-in customer and a guest too.
So, should you move?
Honestly, for most growing stores, yes. Luma migration to Hyvä is worth it when speed is hurting sales, when mobile traffic is high, or when your developers are tired of fighting a heavy front end.
But go in with open eyes. Here’s roughly how we’d do it.
Start with an extension audit. Write down every module on your store and mark the ones that touch the frontend or checkout. Check each one for Hyvä support. Then count the gaps. A few gaps are normal. Twenty gaps means your budget and timeline need a second look.
Next, build and test on a staging site. Never on your live store. Run through your checkout again and again until it’s boring.
And last, launch when traffic is low, with someone watching orders and payments for the first few days. Small thing, big peace of mind.
If you’d rather not do this alone, that’s fine. We’ve worked with Magento stores for a long time, and the extension audit is usually where we save people the most trouble. You can look through our extensions on the Elsner Store or just talk to our team about your setup.
The short version
Hyvä vs Luma isn’t really a fight about which theme is better. Hyvä is faster, no doubt. The real question is whether your extensions, your checkout and your payment methods will come along for the ride.
Check them first. Fix the gaps. Then switch. You’ll sleep better, and so will your checkout.