What is Hyvä and why is it the fastest thing to happen to Magento in years?

If you run a Magento store, you’ve probably heard the word Hyvä a few times recently. Maybe from your developer. Maybe from another agency. Maybe just floating around at an event or in a LinkedIn comment thread.

Most explanations either go too technical too fast or stay so vague they tell you nothing useful.

This is my attempt at an honest middle ground. I’ve been building on Magento for years and working with Hyvä since it started gaining serious traction. Here’s what it actually is, what it does, and why it matters for your business.

First, some context on the problem it solves

Magento is a powerful platform. For mid-market and enterprise ecommerce, there’s still nothing that matches it for flexibility and control.

But its default frontend, the part of the platform your customers actually see and interact with, has always been its weak point. The traditional Magento frontend is built on a system called Luma. And Luma is slow.

Not slow in a vague, hard-to-measure way. Slow in a very specific, measurable way.

A standard Magento store running Luma typically loads somewhere between 1.5MB and 2MB of JavaScript and CSS files before your customer can interact with the page. That can mean load times of 4, 5, 6 seconds or more on mobile. Sometimes worse.

To put that in context, research consistently shows that most mobile users will abandon a page that takes more than 3 seconds to load. For a store spending money on paid traffic, every slow page is money thrown away.

Luma was also built in a way that makes development slow and expensive. Lots of interconnected files, lots of dependencies, lots of opportunities for things to conflict when you’re trying to make changes. A checkout customisation that should take a week ends up taking a month because of how the system is structured.

That’s the problem Hyvä was built to solve.

So what is Hyvä?

Hyvä is a replacement frontend for Magento and Adobe Commerce. It keeps everything that makes Magento powerful, the product management, the order processing, the admin, all of it, and replaces the part of the system that renders what customers see.

It’s built on modern, lightweight technology. Alpine.js and Tailwind CSS, for anyone technical reading this. The important thing for non-developers is what that means in practice.

Instead of loading 200+ files totalling nearly 2MB, a Hyvä storefront typically loads two files totalling around 0.2MB. That’s roughly 1% of the weight of a standard Magento frontend.

The result is a noticeably faster website. Load times that sit under 2 seconds on mobile rather than over 5. Google PageSpeed scores in the 90s rather than the 40s or 50s. Core Web Vitals that pass rather than fail.

What does that mean for development?

This is where it gets interesting from my side of things.

Because Hyvä strips away a lot of the complexity that made Magento development slow, projects take significantly less time to build and test. A rebuild that would have taken 18 weeks on a traditional Magento frontend can often be done in 6 to 8 weeks with Hyvä.

That’s not corners being cut. It’s the same quality of work with far less friction in the process.

The cost difference reflects that. Checkout customisations that would have cost £30k to £40k on a standard Magento build can often be delivered for £10k to £20k with Hyvä. Not because we’re charging less per hour, but because the hours required are genuinely fewer.

For ongoing maintenance and development, the same logic applies. Changes that used to require significant testing and careful handling because of how Luma was structured can be made more quickly and with less risk. That keeps retainer costs down and means we can respond faster when something needs to change.

Is it right for every Magento store?

Honestly, no.

If you’re on Magento and your store is small, your traffic is low, and you’re not planning significant ongoing development, a full Hyvä rebuild might not be the right investment right now. There are cheaper ways to improve performance incrementally.

But if your store is growing, if performance is affecting your conversion rate, if you’re spending meaningful money on development and finding it slow and expensive, or if you’re planning a redesign anyway, Hyvä should be on the table.

The stores that benefit most are the ones doing serious volume where a 1 or 2 second improvement in load time translates directly into revenue, and the ones with active development roadmaps where the efficiency gains compound over time.

What the numbers actually look like

I’m always sceptical of before and after stats that are too clean. So I’ll be specific about what we’ve seen.

Page load times on mobile typically drop from the 4 to 7 second range down to 1 to 2 seconds after a Hyvä rebuild. Google PageSpeed scores on mobile, which are notoriously hard to move on Magento, regularly hit 90 or above post-launch.

One store we rebuilt on Hyvä saw monthly revenue grow from around £25k to over £1m in the months following launch. That wasn’t purely down to the frontend rebuild, there were other improvements made at the same time, but the performance gains were a significant contributing factor.

The development time savings are consistent. Across the Hyvä projects we’ve delivered, build time is roughly 40% to 50% shorter than an equivalent project on Luma would have been.

A few things worth knowing before you start

Hyvä is not a plugin or an upgrade you apply to your existing theme. It’s a rebuild of your storefront. Any custom frontend work on your current theme will need to be redone in the Hyvä framework.

Some Magento extensions are not yet fully compatible with Hyvä, though the community has grown significantly and compatibility is improving all the time. Part of a proper Hyvä project is auditing your current extensions and either finding Hyvä-compatible alternatives or building custom solutions where needed.

It’s also worth knowing how Hyvä’s pricing actually works, because it’s changed. Hyvä Themes, the core frontend framework, is now free. The licence fees come in if you want Hyvä Checkout or Hyvä Commerce, which are separate products. For many stores the free Themes layer alone delivers the performance gains they’re after. For others, adding Hyvä Checkout is worth the cost because of how much it streamlines the purchase flow. Worth understanding which parts of the stack you actually need before budgeting.