Arun Arya, Cofounder, Engineering

Hyvä Theme for Magento 2: The Performance Upgrade That Actually Delivers

Hyvä replaces Magento's bloated Luma frontend with Alpine.js and Tailwind CSS, cutting page weight by 80%. Here's what the migration involves and when it's worth it.

magentohyvaperformancefrontend

Magento 2's default Luma theme ships with 2MB+ of JavaScript, RequireJS module loading, and Knockout.js bindings that make even simple pages feel sluggish. For years, the Magento community accepted this as the cost of a powerful backend.

Hyvä changed that equation. By replacing the entire frontend stack with Alpine.js and Tailwind CSS, Hyvä cuts page weight by 80% and delivers sub-second load times without sacrificing Magento's backend power.

We've migrated six stores from Luma to Hyvä. Here's what we've learned.

What Hyvä actually replaces

Hyvä isn't a child theme or a skin. It's a complete frontend rewrite that removes:

  • RequireJS — Magento's module loader that adds 200-400ms of JavaScript parsing time
  • Knockout.js — The two-way data binding framework that powers Luma's dynamic components
  • jQuery and jQuery UI — Still shipped by default in Magento's frontend
  • Less CSS — Replaced with Tailwind CSS utility classes

In their place, you get:

  • Alpine.js (~15KB) — Lightweight reactive components
  • Tailwind CSS — Utility-first CSS that purges unused styles at build time
  • Vanilla JavaScript — For anything Alpine doesn't cover

The result: a typical category page drops from 2.1MB / 180 requests to 400KB / 25 requests.

Performance numbers we've measured

Across our six Hyvä migrations, here are the before/after Core Web Vitals (mobile, 75th percentile):

  • LCP: 4.2s → 1.4s (67% improvement)
  • INP: 380ms → 90ms (76% improvement)
  • CLS: 0.15 → 0.02 (87% improvement)
  • Lighthouse Performance score: 35-45 → 85-95

These numbers translate directly to conversion rates. Google's research shows that every 100ms of added latency costs 1% of conversions. A 2.8-second LCP improvement is significant revenue.

When Hyvä makes sense

Hyvä is the right choice when:

  • Performance is a business priority. If your Luma store scores below 50 on Lighthouse mobile and you've exhausted caching and infrastructure optimisations, the frontend is likely the bottleneck.
  • You're planning a frontend redesign anyway. Migrating to Hyvä requires rebuilding your templates. If you're already planning a redesign, the incremental effort is small.
  • Your extension count is manageable. Hyvä has a compatibility module for many popular extensions, but heavily customised Luma extensions need porting. If you have 50+ extensions, audit compatibility first.
  • You're staying on Magento long-term. If you're planning to migrate to Shopify within a year, the ROI on a Hyvä migration is questionable.

When Hyvä doesn't make sense

  • You have heavy Knockout.js customisations. If your team built custom Knockout components (product configurators, complex cart logic), those need rewriting in Alpine.js. The effort can be substantial.
  • Your budget is under $15k. A Hyvä migration for a mid-complexity store typically costs $20k-$50k. Below that budget, you'll get a rushed job.
  • You need PWA features. Hyvä is a traditional server-rendered frontend. If you need offline support, app-like navigation, or push notifications, consider Hyvä's React-based checkout or a headless approach instead.

The migration process

Step 1: Extension audit (1-2 days)

Before anything else, inventory every frontend-facing extension and check Hyvä compatibility:

  • Hyvä-compatible: Has an official Hyvä module. Install and go.
  • Needs porting: Works on Luma but has no Hyvä module. We write Alpine.js equivalents.
  • Backend-only: No frontend impact. These just work.
  • Replace: Some extensions should be replaced entirely. Hyvä's built-in features cover many common use cases (lazy loading, slider, mega menu).

Step 2: Design implementation (2-4 weeks)

We rebuild your templates in Hyvä's Alpine.js + Tailwind stack. This isn't a pixel-for-pixel copy — it's a chance to improve UX while maintaining brand identity.

Key templates to build:

  • Homepage with CMS blocks
  • Category/collection pages with layered navigation
  • Product detail pages (simple, configurable, grouped, bundled)
  • Cart and mini-cart
  • Customer account pages
  • Search results

Step 3: Checkout (1-2 weeks)

Checkout is the most critical page. Hyvä offers two checkout options:

  1. **Hyvä Checkout** — Alpine.js-based, fast, customisable
  2. **React Checkout** — More complex but supports advanced payment integrations

We usually recommend Hyvä Checkout unless you need features that require React (like complex multi-step payment flows).

Step 4: Testing and launch (1-2 weeks)

  • Cross-browser testing (Chrome, Safari, Firefox, Edge)
  • Mobile device testing (iOS Safari, Android Chrome)
  • Payment gateway verification
  • Performance benchmarking against Luma baseline
  • Redirect verification for any URL changes
  • Load testing to validate performance under traffic

Cost and timeline

A typical Hyvä migration:

  • Simple store (< 5 custom templates, < 10 extensions): $15k-$25k, 6-8 weeks
  • Mid-complexity (10-20 custom templates, 15-25 extensions): $25k-$50k, 8-12 weeks
  • Complex store (custom product configurators, B2B features, 30+ extensions): $50k-$80k, 12-16 weeks

The ROI calculation is straightforward: if a 67% LCP improvement increases your conversion rate by even 0.5%, the migration pays for itself within months on a $5M+ store.


Running a slow Magento store? Start with a [free Magento health check](/magento-health-check) — we'll tell you whether Hyvä is the right move for your specific situation. Or [book a discovery call](https://calendly.com/codifier-info/30min) to discuss your project.