Current front end
You stay on Luma
Best when
Sales are steady, the change budget is small, and mobile speed isn't driving customers away.
Decision cost
Every further fix costs more, because the old front end keeps getting harder to maintain.
Hyvä for Magento 2
You don't have to change platforms. With Hyvä we replace only what customers see: the store gets a new look, new features and opens straight away. Products, orders and integrations stay as they are.
Speed score
95+ in Google after moving to Hyvä
Where AI helps here
What the customer sees
Photo, price and the buy button appear before the customer has time to scroll.
Fast pages score well on Core Web Vitals, the metrics Google uses to judge how easy a page is to use.
The product goes into the cart instantly, and the customer stays on the page to keep shopping.
The page weighs a fraction of the default front end, so it opens fast even on a weak signal.
The front end is simpler, so new elements such as product bundles or banners take less time and cost less.
Decision
The choice depends on how much a slow front end hurts sales and how much you want to spend. We review the store first, then advise.
Current front end
Best when
Sales are steady, the change budget is small, and mobile speed isn't driving customers away.
Decision cost
Every further fix costs more, because the old front end keeps getting harder to maintain.
Hyvä
Best when
Magento handles sales well, but the front end is slow or expensive to develop.
Decision cost
A short module review up front. We handle the rest, and the store keeps selling throughout.
Separate front end
Best when
You sell across many channels, need full freedom and have the budget for it.
Decision cost
More systems to maintain and more integrations.
Staged migration
You don't have to switch everything over in one day. Pages we haven't moved yet keep running on the old front end through the Hyvä Fallback module, and the store keeps selling the whole time.
We agree the order of stages with you, usually starting with the pages that bring the most traffic.
Hyvä Old front end
| Stage 1 The pages most customers see | Stage 2 Cart and customer account | Stage 3 Checkout, e.g. on Hyvä Checkout | |
|---|---|---|---|
| Home page | Hyvä | Hyvä | Hyvä |
| Categories | Hyvä | Hyvä | Hyvä |
| Product page | Hyvä | Hyvä | Hyvä |
| Cart | Old front end | Hyvä | Hyvä |
| Customer account | Old front end | Hyvä | Hyvä |
| Checkout | Old front end | Old front end | Hyvä |
Before migration
How well a migration pays off depends on modules, scripts and how the current front end was built. That's why we check them first.
We check which extensions touch the front end and the cart. Some need rewriting or replacing.
Analytics, chats and ad tags can slow down even a light front end. We tidy them up during the migration.
We keep URLs, descriptions and redirects, so the store doesn't lose traffic from Google.
We move the store without stopping sales and not in the middle of your peak season.
FAQ
No. Hyvä changes what the customer sees. The admin, catalogue, orders and integrations stay the same.
Not always. We often start with the most important pages and move the checkout and the rest in later stages.
A faster store usually loses fewer customers along the way, but conversion also depends on the offer, payments and traffic quality. That's why after the migration we measure customer behaviour, not just the Lighthouse score.
It depends on the number of custom views, modules and integrations. After reviewing the store we give a date for the first stage.
Notes from our work on online stores and business systems.
We'll build a store on Hyvä from scratch or move your current one off Luma, without stopping sales.