E-commerce

What Is Hyvä and Why It Pays Off for Magento 2

Hyvä is the Magento 2 frontend theme built on Alpine.js and Tailwind CSS: what it is, how it differs from Luma, and the benefits and limits to weigh.

Area
E-commerce
Published
November 16, 2026
Reading time
5 minutes

In this guide

What you will find

Hyvä is a frontend theme for Magento 2 (Adobe Commerce and Magento Open Source) that replaces the Luma theme with a lighter interface built on Tailwind CSS and Alpine.js. It does not change the core of the store, meaning catalogue, orders, pricing rules and integrations: it changes how the store is displayed and developed. People searching for "hyva magento" or "hyva theme" usually want to know two things: whether it is worth it, and under what conditions.

What is Hyvä for Magento 2

Hyvä is a commercial product built by Hyvä Themes, not the official Magento theme. The vendor's site presents it as "The lightweight powerhouse" and lists a product family: Hyvä Theme, Hyvä Checkout, Hyvä UI, Hyvä Commerce for Magento Open Source and Hyvä Enterprise for Adobe Commerce. The technical documentation explains that it installs with Composer, using a free licence key requested on the website, and that it relies on parts of Magento's GraphQL API (Hyvä documentation).

The difference from the legacy theme is the frontend stack. Luma relies on jQuery, KnockoutJS and RequireJS. Hyvä uses Tailwind CSS for styling and Alpine.js for interactivity, with Magento's PHTML templates in place of many JavaScript libraries.

Hyvä vs Luma: what actually changes

  • Less JavaScript to load. With fewer libraries the browser downloads and runs less code. The expected benefit is on loading and interaction, two things measured by Core Web Vitals.
  • Simpler development. Tailwind and Alpine have a shorter learning curve than Knockout and RequireJS. Customising a component takes fewer steps and fewer files.
  • Lighter maintenance. Fewer layers of code mean fewer places where an update can break something.
  • Same backend. Catalogue, prices, promotions, orders and integrations with ERP, PIM and marketplaces stay exactly as they are in Magento.

A concrete example is the Semprefarmacia case study: on the client's very large catalogue we adopted the Hyvä template for Magento 2, and the site became faster and easier to maintain. The same approach, with Adobe Commerce, is described in the Antica Farmacia Orlandi case study.

Why Hyvä pays off

Hyvä pays off mostly when the current theme has become a cost: slow pages to optimise, trivial changes that take days, updates that break the frontend. In those cases a simpler frontend lowers the time of every later intervention.

The reference values for measuring improvement are Google's: a "good" experience needs LCP within 2.5 seconds, INP within 200 milliseconds and CLS within 0.1, assessed at the 75th percentile. Before migrating, measure where you stand today on the pages that earn the most revenue, so you know your starting point and can honestly compare the result when the project is done, without relying on generic promises.

When Hyvä is not the right choice

Hyvä is not adopted with one click: besides the licence you have to budget development and testing work, and there are limits to know about before deciding.

  • Extension compatibility. Extensions built for Luma or Blank need a compatibility module to work with Hyvä. Hyvä publishes a tracker of existing modules, but less common extensions may need bespoke development.
  • Checkout. Checkout is the most delicate part: if it depends on Luma-based extensions, you can consider Hyvä Checkout or the Luma fallback for some pages.
  • Versions and requirements. The documentation lists minimum Magento and PHP versions and the Node.js needed to build Tailwind: check them against your environment before starting.
  • Heavily customised stores. The more the Luma theme has been modified, the more work it takes to rewrite the components.

How to decide whether to move to Hyvä

A good starting point is a short audit that answers four questions:

  1. Which frontend extensions does the store use, and which already have a compatibility module?
  2. How is the checkout built and how customised is it?
  3. What are the current Core Web Vitals on the pages that drive revenue?
  4. How much custom code is in the theme?

The answers give you a scope and a realistic estimate, and show whether a full or a gradual, page-by-page migration makes more sense. If you are building a new store, starting directly on Hyvä avoids a later migration; the next guide explains how to migrate from Luma to Hyvä step by step. With Ecommerce Factory we design and build online stores on Adobe Commerce with a Hyvä frontend or on Shopify Plus, and after go-live the store moves to DNA Support and DNA Evolution.

FAQ

Frequently asked questions

Can't find the answer? Write to us and we will get back to you.

Ask your question

Services

The services linked to the guide

  • Ecommerce Factory

    We design and build B2C and B2B online stores on Adobe Commerce (Magento) with Hyvä and on Shopify Plus: analysis, UX, development, integrations, go-live.

See all services

The DNAFactory service lines that put into practice what this guide explains.

Guides

More guides

How e-commerce platforms, custom management software and AI work and how to choose, from the people who work on them every day.

Contact us

We are ready to hear about your project

Tell us about your online store or your idea. One of our experts will get back to you within 24 hours.

Request a quote Or write to us at [email protected]