02 / 06Default checkout
Hyvä Checkout
Magento’s heavy Knockout checkout replaced with Hyvä Checkout — the same Tailwind and AlpineJS stack, built around how your customers actually pay.
Hyvä CheckoutDelivery slotsPayment methods
Why Hyvä is the default
Luma out.
Hyvä in.
Hyvä replaces Magento’s Luma frontend with a Tailwind and AlpineJS theme. Ten times fewer front-end dependencies, materially better Core Web Vitals, and a codebase developers actually want to open. It’s my default for every new Magento 2 build — unless you’re locked into PWA Studio or a headless frontend.
Core Web Vitals
Lighter pages that pass, on real phones.
Luma → Hyvä
Conversions without a replatform.
Hyvä Checkout
A faster, simpler path to paid.
Luma stack
RequireJS
KnockoutJS
jQuery
jQuery UI
LESS
UI components
JS bundling
Hyvä stack
AlpineJS
Tailwind CSS
That’s the whole frontend.
Capabilities
What I build.
A deliberately narrow list. The pieces I ship week in, week out — and charge for with confidence.
01 / 06
Luma → Hyvä conversions
Your existing store moved onto a Hyvä frontend, extension by extension — trading the whole way through and launched behind a theme switch.
Extension auditDesign portTheme switch launch
03 / 06
Greenfield Hyvä builds
New Magento 2 storefronts designed and built on Hyvä from day one, with no Luma debt to carry forward.
Hyvä ThemeTailwindAlpineJS
04 / 06
Widget & content systems
Campaign heroes, navigation and CTA blocks your merchandisers assemble themselves, so campaigns go live without a developer.
WidgetsPage BuilderCampaign tooling
05 / 06
Extension compatibility
Every module with frontend output gets a verdict — official compat module, community fallback, rebuild or retire — before a line of theme code is written.
Compat modulesRebuildsHonest retirements
06 / 06
Core Web Vitals
Before-and-after benchmarks on real phones, plus the image, font and script discipline that keeps a Hyvä store green after launch.
LCPINPCLSLighthouse CI
Selected Hyvä work
The receipts.
Three storefronts, three very different problems: speed, checkout, and brand.
01 · Fashion · 2024
BrandAlley.
A UK flash-sale retailer traded Luma for Hyvä — and got its speed back.
Improvement in Google PageSpeed score
Before · Luma
After · Hyvä
Magento 2Hyvä ThemeAlpineJS
Hyvä Checkout · step 2 of 3Delivery
Choose your delivery day
Mon
9
Tue
10
Wed
11
Thu
12
Fri
13
Sat
14
Sun
15
Morning · 7am–12pmSelected
Afternoon · 12pm–6pmAvailable
Magento 2Hyvä CheckoutDelivery slots
Read the Daylesford case →
How I engage
Three ways in.
Pick one, or sequence them. Every engagement starts with an honest read on whether converting beats tuning the Luma store you have.
2 weeks · fixed price
Frontend audit
Your theme, extensions and Core Web Vitals reviewed, with a compatibility map and a real quote for the conversion.
- Extension compatibility map
- Core Web Vitals benchmarks
- Tune-Luma-or-convert recommendation
- Live walkthrough with your team
6–8 weeksMost common
Conversion
Luma to Hyvä on your existing store, or a move to Hyvä Checkout. Built in parallel and launched behind a theme switch.
- Scoped brief, priced fixed or capped
- Design ported or refreshed on Tailwind
- Before-and-after benchmarks
- Thirty days of post-launch support
12+ weeks
Hyvä build
A full Hyvä storefront and checkout, with a senior lead embedded in your team from first commit to launch.
- Hands-on senior engineer
- Widget system your team can run
- In-house team training as you go
- Retainer handover on launch
Ecosystem
The stack I live in.
Your stack may differ — I meet it rather than fight it.
How much does a Hyvä theme migration cost?
Extension compatibility is the swing factor. A lean store converts for less than you would expect — a 6–8 week project — while extension-heavy stores need compat work that extends the timeline. The fixed-price frontend audit maps every module and returns a fixed or capped quote, so you decide with a real number, not a range.
Hyvä vs Luma — is it really that much faster?
Yes, and it is structural, not tuning. Hyvä ships roughly a tenth of Luma's JavaScript and none of its render-blocking dependency chains. Lightweight-frontend rebuilds I have shipped score 100 on desktop PageSpeed and 80 on mobile — numbers I have never seen a tuned Luma store reach, and Hyvä is how I deliver them today.
Will our extensions work with Hyvä?
Most will. The Hyvä ecosystem has official compatibility modules for hundreds of popular extensions, and the audit gives every module in your store a verdict: compatible, community fallback, small rebuild, or honestly not worth carrying over. Stores usually end up running fewer, better extensions after the conversion.
Hyvä or headless / PWA Studio?
For most merchants, Hyvä. It delivers the performance headless promises without the second codebase, the Node infrastructure, or the double maintenance bill. Headless earns its complexity when you have genuine multi-channel requirements or a large in-house React team. I build both, so you will get a recommendation based on your team, not my preference.
How long does a Luma to Hyvä conversion take?
Six to eight weeks for a typical store, longer where heavy extension compatibility or custom checkout work is involved. Your current store keeps trading throughout — the new theme is built and benchmarked in parallel and launched with instant rollback.
Does Hyvä work with Adobe Commerce?
Yes — Hyvä supports Adobe Commerce, including B2B features like company accounts and requisition lists. I scope Commerce-specific functionality in the audit so nothing is discovered missing after launch.
Will the migration hurt our SEO?
It should help it. URLs and metadata are untouched in a theme conversion — what changes is speed, and Core Web Vitals are a ranking signal. Faster templates also render more consistently for crawlers. I benchmark organic visibility before and after, the same as on platform migrations.
Can you fix our Core Web Vitals without a full Hyvä migration?
Often, yes — image optimisation, critical CSS and JavaScript deferral can move a failing Luma store to passing. The audit tells you honestly whether tuning will get you there or whether you are paying to polish a ceiling that only a new frontend lifts.
Got a Luma store that should be faster?
Tell me what’s slow. You’ll get a straight answer within one working day — even if the answer is “tune Luma first”.