Hyvä Theme for Magento 2:

Complete Guide to Features, Benefits, and Development

Magento 2 is a powerful ecommerce platform, but its default front end often becomes the first place where performance problems show up.

Hyvä Theme for Magento 2 was created as a different approach that replaces the traditional front-end stack with lightweight technologies supporting faster page rendering and improved JavaScript optimization. As a result, Hyvä stores often achieve stronger Core Web Vitals metrics, shorter load times, and a more maintainable front-end architecture.

However, the Hyvä Theme has certain limitations. In this article, we explain how Hyvä works, explore its key features and benefits, compare it with other Magento front-end approaches, and discuss situations where alternative solutions may be a better fit.

We also share migration recommendations based on Whidegroup’s practical experience and show the results of a real Hyvä migration project.

Key Takeaways

• Hyvä replaces Magento’s default Luma front end with a lighter architecture based on Tailwind CSS and Alpine.js, helping stores achieve stronger Core Web Vitals (CWV) and faster page load times.
• Hyvä is often a good fit for merchants planning a redesign, storefront modernization, or major functionality expansion without moving to a headless architecture.
• Hyvä can reduce long-term front-end maintenance complexity, but it does not automatically solve performance issues related to servers, databases, or third-party integrations.
• Extension compatibility, custom functionality, checkout logic, and design requirements all influence the Hyvä migration project scope and cost.
• Businesses that need offline browsing, push notifications, or a fully decoupled architecture should evaluate PWA or other headless solutions instead of Hyvä.

What Is Hyvä Theme for Magento 2?

Hyvä Theme is a modern Magento 2 front end designed as an alternative to the default Luma storefront. Hyvä replaces outdated technologies with a leaner, lighter architecture. At the same time, Hyvä remains a monolithic storefront within the Magento platform, unlike decoupled front ends built with headless frameworks.

Architecture setup. Instead of relying on Knockout.js, RequireJS, and other parts of the traditional Luma stack, Hyvä uses Tailwind CSS and Alpine.js. This technology setup reduces front-end complexity, decreases page weight, and helps improve page load speed and CWV metrics.

Additional products. Beyond the storefront itself, the Hyvä ecosystem now includes products such as Hyvä UI, Hyvä Checkout, and Hyvä Commerce. The company also offers Hyvä Enterprise, which extends the platform with additional B2B functionality for Adobe Commerce merchants.

Growing audience. Since its launch, Hyvä has seen steady growth in the number of live stores. Each year, more merchants adopt Hyvä when launching new websites and upgrading existing ones. You can see how brands design their websites by exploring real Hyvä store examples.

The reason why Hyvä is gaining popularity lies in the technologies behind it. In the following section, we explain how Hyvä changes Magento’s front-end architecture by replacing key parts of the traditional Luma stack.

How Hyvä Changes Magento 2 Front-End Architecture

To understand why Hyvä delivers faster storefronts and a simpler development experience, let’s take a closer look at how it changes the Magento front-end architecture.

Front-end styling simplified

Luma relies on a large collection of LESS files and predefined styles that often require extensive customization. Hyvä replaces this approach with Tailwind CSS.

Tailwind CSS handles styling and page layout through utility classes applied directly in templates. When configured properly, this framework helps keep the final CSS payload smaller by removing unused styles during development. 

A heavy library replaced

Interactive elements in the default Magento 2 front end rely on the Knockout.js library. This framework adds extra JavaScript that browsers must download and execute. As storefronts become more customized, the amount of JavaScript grows, increasing browser workload and affecting page performance.

To reduce unnecessary JavaScript overhead, Hyvä provides a complete Knockout.js replacement, using Alpine.js instead. This framework uses significantly less JavaScript and adds interactivity directly within HTML templates.

Alpine.js is especially useful for lightweight interactions such as dropdowns, tabs, quantity selectors, toggles, and simple form behavior. More complex storefront features, like dynamic product options or cart updates, can also be implemented in the Hyvä stack, but they may require additional custom development. 

JavaScript dependencies reduced

In the traditional Luma stack, RequireJS loads and manages interactive functionality in a way that adds dependencies, extra requests, and more browser-side processing.

Hyvä supports RequireJS reduction by using modern native JavaScript. With fewer front-end dependencies and less JavaScript for the browser to load and process, Hyvä helps improve page load speed and provides better Core Web Vitals performance.

Magento templates simplified

Both Luma and Hyvä use Magento’s native PHTML templates, but they use them differently.

In Luma, PHTML templates work alongside Magento UI components, which integrate templates, JavaScript logic, and configuration files. This architecture powers product options, filters, forms, checkout, and other storefront functionality, but it also introduces additional front-end dependencies.

Hyvä removes many of these dependencies by implementing most storefront functionality through simplified PHTML templates, Alpine.js, and native JavaScript. As a result, developers work with templates that are easier to understand and customize.

Let’s recap the changes that Hyvä brings to Magento’s front-end architecture. Hyvä uses simplified PHTML templates as a foundation, Tailwind CSS for styling, and Alpine.js together with native JavaScript for interactivity. Compared to their Luma counterparts, these technologies are lighter and easier to maintain. 

Key Hyvä Themes Features

The Hyvä ecosystem continues to expand with products and tools that help merchants and developers address a wider range of ecommerce requirements. Below are some of the main Hyvä features available today.

Hyvä UI component library

Hyvä UI is a library of pre-designed components that includes both standalone elements, such as add-to-cart buttons and navigation controls, and ready-made storefront sections, such as product specifications, galleries, and category page grids.

All Hyvä UI components are mobile-friendly and easy to customize, which helps designers and developers build and adapt storefronts faster while maintaining brand consistency.

Hyvä checkout options

The standard Magento 2 checkout relies heavily on Knockout.js and Magento UI components, which are not part of the Hyvä front-end architecture. That’s why the checkout page requires a separate migration strategy.

To ensure efficient order processing after moving to Hyvä, merchants can choose from the following options:

• Hyvä Checkout. A commercial solution developed specifically for the Hyvä Theme. It uses the same front-end technologies as the rest of the storefront and receives regular updates from the Hyvä team.
• React Checkout for Hyvä. A free checkout module built with React and styled using Tailwind CSS. Originally created by the Hyvä team, it is now maintained as an open-source project. Hyvä React Checkout can work with both Hyvä and Luma-based Magento 2 stores.

Merchants can still keep the standard Magento 2 checkout after migrating to Hyvä.  Businesses sometimes choose this option when a store has extensive checkout customizations and they want to avoid rebuilding everything from scratch.

Although it’s technically possible to stay with the default checkout, Whidegroup developers generally do not recommend keeping it. The standard setup may simplify the initial launch, but it also saves part of the old Magento development stack in the project. This legacy front end can create extra maintenance work and complicate future Magento or Hyvä upgrades.

Hyvä Commerce as a product suite

Hyvä Commerce is a suite of modules compatible with both Magento Open Source and Adobe Commerce. This suite includes Hyvä Theme, Hyvä UI, and Hyvä Checkout. In addition, Hyvä Commerce provides several features that are not currently available as standalone Hyvä products:

• Hyvä CMS. An alternative to Magento Page Builder for creating and editing website pages directly from the admin panel.
• Admin Theme. A redesigned Magento admin interface that brings a modern user experience to managers’ daily interactions.
• Admin Dashboard. This feature showcases sales data across multiple storefronts and allows managers to compare performance metrics. Admin users can customize the dashboard to meet their exact needs.
• Media Optimization. A module that integrates with Hyvä CMS and media galleries and removes the need for external image-processing tools, such as WebP converters.
• Image Editor. A tool that crops and resizes images directly from the admin panel without relying on third-party software.

Hyvä Enterprise for Adobe Commerce compatibility

Hyvä Enterprise is an add-on for merchants who use Adobe Commerce and want to adopt the Hyvä front end. This module extends Hyvä Theme and Hyvä Checkout to support Adobe Commerce features that are not available in Magento Open Source: B2B functionality, Live Search, Product Recommendations, customer-specific attributes, loyalty, and gifting features.

Extension compatibility ecosystem

When Hyvä first launched, extension compatibility was one of the main migration concerns. Because Hyvä replaced much of Luma architecture, developers often had to create separate compatibility modules to adapt their extensions for Hyvä.

Today, extension compatibility is much less of a challenge, as most major Magento providers offer official Hyvä support or compatibility modules.

Even so, stores that rely on legacy extensions with limited maintenance may still encounter integration issues. In such cases, Whidegroup recommends evaluating modern alternatives that provide similar functionality. If replacing the module is not possible, an experienced Magento development team can adapt the extension to work with Hyvä.

Accessibility-oriented foundation

Hyvä follows the accessibility principles defined in WCAG and incorporates them into the front-end architecture. The theme supports keyboard navigation, screen readers, proper focus management, and semantic HTML structure.

Hyvä also promotes accessibility-focused design through improved color contrast, readable typography, sufficient spacing, and descriptive labels for interactive elements.

The Hyvä ecosystem includes a range of features that improve the experience for both store visitors and ecommerce teams. The following section shows how these peculiarities translate into business value.

Hyvä Theme Benefits for Magento Store Owners

After looking at how Hyvä changes the Magento front end and which tools support this architecture, the next question is what these changes mean for store owners.

Faster page load speed and better Core Web Vitals

Hyvä front-end architecture is lighter and less dependent on large JavaScript and CSS libraries than the default Luma storefront. When implemented correctly, this leaner setup can improve store performance by:

• Reducing page weight: smaller codebases result in faster load times.
• Improving CWV: stores pass the assessment for Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), and Interaction to Next Paint (INP).
• Boosting performance scores: sites achieve much higher scores in Google PageSpeed Insights (PSI), often entering a green zone with 90+ scores.

These improvements help visitors interact with the store faster. In turn, merchants may notice lower abandonment rates and higher conversions.

Smoother mobile and cross-device shopping experience

Hyvä provides faster page rendering and quicker responses to user actions across desktops, tablets, and smartphones. Because storefront elements load and react with less delay, shoppers can move through category pages, product pages, filters, and checkout with fewer interruptions.  

For mobile users, this smoother experience matters even more. When pages load faster and storefront interactions feel more stable, merchants can reduce friction in the shopping journey, supporting lower abandonment rates and better conversion. 

Stronger technical foundation for SEO

Hyvä’s lightweight front-end architecture contributes to several SEO factors, including faster page load speed, stronger CWV metrics, and responsive design. These improvements help create a smoother experience for users and a cleaner technical environment for search engines.

Hyvä’s codebase also makes it easier for developers to implement meta tags, structured data, and other SEO elements. Clean, semantic HTML also allows search engines to crawl and understand store content more efficiently.

Hyvä does not automatically improve search engine rankings, but it provides a stronger technical foundation for SEO than the default Luma storefront.

Easier storefront customization for brand-specific UX

While Hyvä offers pre-designed blocks and elements, it does not lock store teams into rigid theme structures. Developers can use ready-made components and adapt them to match brand identity and specific user flows. As a result, merchants can achieve a tailored storefront experience without having to order a custom design.

Hyvä CMS further simplifies routine content and layout updates, reducing the involvement of technical experts. Still, larger UX improvements and design changes require proper design and development expertise.

Lower long-term development and maintenance costs

Migrating to Hyvä requires upfront development effort, but for many merchants we’ve worked with it makes sense as a long-term investment. Several factors can contribute to this long-term cost efficiency:

• Fewer performance-related fixes. Hyvä provides a stable foundation for CWV and page speed optimization, often reducing extensive ongoing front-end performance work.
• More efficient content management. Tools such as Hyvä CMS allow store teams to manage content and layout updates without involving developers for every routine task.
• Faster development cycles. A cleaner codebase and reusable components can shorten the time needed to launch new features and design updates.
• Simplified maintenance. Because Hyvä relies on fewer dependencies than the Luma stack, upgrades and troubleshooting become more manageable.

One of our clients reports a lower total cost of ownership after migrating to Hyvä, despite completing the project when Hyvä was a paid theme:

Our store has been running on the Hyvä Theme for more than two years. Looking back, I’m confident it was the right decision — ecommerce is a major part of our business, and we have to think about the future.The investment in the license isn’t significant if you’re already planning a retheming project.

One of the retheming challenges is that the entire front-end must be redesigned. This requires organizing all the existing elements, which takes time and budget. Our project, like I believe many other long-standing ones, had accumulated some low-quality elements and implementations over the years. When we switched to Hyvä, we took the opportunity to clean up all of that. The project is now in a much healthier state.

If we were starting a new Magento project today, we would absolutely choose Hyvä from the beginning. The theme is gaining popularity, and I’m sure that more modules supporting it will appear soon. That also means a growing number of qualified developers who know how to work with Hyvä.

Henning Bargest, Head of IT Department at Lichtnelke

See how a Magento store improved performance after moving to Hyvä.

Explore our migration case study

Read now

Hyvä vs. Luma vs. PWA vs. Headless: Which Magento 2 Front End Should You Choose?

There is no single Magento front-end approach that works best for every business. The right choice depends on your budget, performance requirements, development resources, and long-term ecommerce strategy.

The table below compares the most common Magento front-end options to help merchants understand where each approach fits best.

Merchants looking for a faster and easier customizable alternative to Luma often narrow their decision to Hyvä or PWA. Both approaches can deliver good performance, but they differ significantly in development, maintenance complexity, and long-term costs. For a detailed breakdown, read our comparison of Hyvä vs. PWA.

When Should You Choose Hyvä Theme for Magento 2?

In this section, let’s explore closer, when the Magento 2 Hyvä Theme will be a good option for your store.

You are launching an online store for an established offline business

If your company has already built a strong reputation through physical stores, your ecommerce website should deliver the same level of quality and trust that customers already associate with your brand.

Starting with Hyvä allows you to launch a Magento storefront with strong performance potential and a user experience aligned with your brand standards. Instead of investing in a theme that may require major upgrades later, you can build on a more future-oriented foundation from the beginning.

Your current theme has become slow and outdated

Many Magento stores continue to run on themes developed years ago and have accumulated performance and usability issues over time.

When you consider a design refresh alongside performance optimization, it may make sense to do it on the simpler Hyvä tech stack rather than patching an old theme again and again.

Your store has outgrown its existing front end

After scaling your ecommerce business, you may need new integrations or even bespoke features to align with your updated business flow and enhance the user journey. Yet Luma hardly supports expanded functionality without decreasing performance.

In such cases, a Hyvä migration project may be a more cost-efficient option than adding all necessary functions to a Luma-based store and then optimizing it for speed. In addition, Hyvä simplifies upgrades as your business grows further.

You are planning a major Magento store upgrade

A Magento site overhaul is a good time to rethink your front end. If the project already includes redesign, new features, and performance optimization, it makes sense to address them in one roadmap rather than as separate future tasks.

Modifying the existing Luma storefront may seem easier at first, but it does not always solve the underlying front-end limitations. Developers may still need to adapt the new design, adjust custom elements, and continue performance optimization on the same older architecture.

Hyvä migration turns a standard redesign into deep storefront modernization, allowing you to execute required updates much more efficiently than on Luma. Ultimately, customizing an old theme during a large-scale project rarely saves time or cuts costs compared to Magento Hyvä development.

When Hyvä May Not Be the Best Option

Hyvä can provide significant performance advantages, but it is not always the most practical choice for an ecommerce business. There are situations where other approaches may be more practical.

You’ve recently invested in a custom-built Magento theme

If your store runs on a heavily customized front end, especially after a recent redesign or optimization project, a Hyvä migration is rarely the optimal next step. Hyvä requires substantial redevelopment work to recreate existing functionality within its architecture, involving a significant repeated investment.

If you think you still need Hyvä, start by describing in detail the issue with your existing custom theme. A consultation with a Magento development agency can help determine whether supporting the Luma storefront or migrating to Hyvä will deliver better long-term value. 

Your store has simple requirements

If your Magento store has a small product catalog, standard customer journeys, and no immediate plans to scale, investing in a completely new front-end architecture may be premature.

At this stage, maintaining the default storefront or adopting a modern, ready-made Magento theme is usually enough. Luma delivers all the necessary functionality for Magento stores with simple ecommerce requirements.

If you choose to scale your business and need to add custom features, migrating to Hyvä will be a viable next step. Its value becomes clearer as storefront complexity and customization requirements grow.

You need app-like PWA functionality

If your business requires offline browsing, push notifications, installable app-like experiences, or a fully independent front end, these requirements fall outside the scope of Hyvä. 

In this case, a Magento PWA alternative or another headless solution may be a better fit, especially if the project requires advanced customer experiences across websites, mobile apps, kiosks, IoT devices, and other touchpoints.That said, it is important to evaluate whether PWA capabilities are truly necessary for your business. Compared to Hyvä, PWA and other headless solutions involve higher development and maintenance costs, and extend project timelines.

Your store depends on many Luma-specific extensions

Extension compatibility has expanded significantly since Hyvä’s launch, and many major Magento extension providers now offer official Hyvä support.

However, stores that rely heavily on frontend-intensive modules should evaluate compatibility before committing to a migration. Some extensions may still require compatibility packages, custom front-end development, or replacement with alternative solutions.

A technical audit helps identify potential compatibility issues early and provide a more accurate estimate of migration projects.

You’re not ready to invest in a custom migration strategy

Hyvä migration is not a plug-and-play upgrade. Stores with custom functionality, third-party integrations, multiple storefronts, or extensive design requirements require careful planning, development, and testing.

Hyvä delivers the greatest value as part of a broader storefront modernization strategy. If your immediate goal is limited to improving page speed or refreshing the visual, targeted Magento optimization or design services may be more appropriate.

Magento Hyvä Migration: What to Check Before Starting

Initially, your team should evaluate the existing Magento setup, identify potential compatibility risks, and gather migration project requirements that align with your business goals.

1. Current Magento version and theme

The first step is to review your current technical setup:

• Infrastructure: hosting environment, server resources, PHP version, caching configuration, CDN setup, and other factors that affect storefront performance.
• Magento or Adobe Commerce version: stores running outdated versions may require a Magento version upgrade before or during the Hyvä migration project.
• Front-end theme: current theme setup (the default Luma theme, a third-party solution, or a custom theme), plus the level of front-end customization and custom functionality already implemented..
• Performance baseline: metrics from Google PSI, CWV reports, Google Analytics, Search Console, etc. that help measure the impact of the migration after launch.
• Current business pain points: slow page speed, maintenance challenges, outdated user experience, extension conflicts, or other issues that motivate the migration project.

2. Third-party extensions

Most major Magento extension providers now offer Hyvä compatibility, yet compatibility should never be assumed.

Create a list of all installed modules and identify which ones already support Hyvä, which require compatibility packages, and which may need replacement. This review helps avoid unexpected development work later in the project.

3. Checkout, payment, and shipping logic

Checkout is one of the most sensitive areas of any ecommerce website. Review any functionality that extends beyond standard Magento features or ready-made integrations, as these customizations often require additional development and compatibility work.

Review the following areas before migration:

• Custom checkout flows: multi-step checkouts, additional checkout fields, etc.
• Payment integrations: custom gateways or integrations with local payment providers.
• Shipping and tax logic: custom shipping methods, carrier integrations, tax calculations, delivery restrictions, or region-specific pricing rules.
• B2B purchasing processes: company accounts, purchase approvals, quote requests, negotiated pricing.
• Customer account functionality: bespoke account sections, loyalty programs, subscription management, or other features connected to customer data and order history.

4. Custom front-end logic

Since Hyvä uses a different front-end architecture than Luma, the following elements often require compatibility review:

• Custom JavaScript functionality: scripts that support unique product interactions, dynamic content updates, tooltips, modal windows, etc. 
• Product configurators and builders: custom solutions for visual configurators, product personalization, product bundles, engraving options, or other complex purchasing experiences.
• Customized navigation and search experiences: advanced mega menus, layered navigation, predictive search, or product finders.
• Unique UX components: custom filters, interactive product galleries, comparison tools, calculators, or quizzes.

5. SEO and analytics setup

To preserve your search engine rankings and continuity of data reports, make a list of necessary settings:

• Metadata setup: title tags, meta descriptions, and canonical tags.
• Structured data: product, review, breadcrumb, FAQ, and other Schema.org markup.
• Redirect requirements: existing redirects and any URL changes planned during the migration.
• Custom tracking implementations: ecommerce tracking, custom events, CRM integrations, and other business-specific reporting configurations.

6. Design update requirements

Before starting a Hyvä migration, you should decide whether the goal is to recreate the existing storefront design or use the project as an opportunity for a redesign.

In practice, design projects can be organized in one of three ways:

• Design replication: rebuilding the current storefront on the Hyvä architecture, preserving the existing visual appearance, page layouts, and user flows.
• Storefront redesign: updating the visual identity, page structure, navigation, customer journeys, or other UX elements as part of the migration project.
• Hybrid approach: preserving the overall brand identity while redesigning selected sections or pages.

7. Quality assurance (QA) and launch plan

Quality assurance and launch requirements should also be planned from the start to avoid delays and deployment risks:

• Testing scope: functionality, checkout flows, payment methods, shipping calculations, mobile experience, extension compatibility, analytics tracking, and SEO validation.
• Launch constraints: preferred deployment windows, seasonal sales periods, marketing campaigns, blackout dates, or other business events that may affect the launch schedule.
• Downtime requirements: acceptable maintenance windows and business expectations regarding storefront availability during deployment.
• Rollback strategy: procedures for restoring the previous storefront if critical issues are discovered after launch.

Custom Hyvä Theme Development: What It Includes

Unlike traditional Magento themes, Hyvä does not come with fixed page layouts or work as a ready-made storefront for light customization. Instead, the theme provides a lightweight foundation for building a custom Magento storefront, so every project involves some level of custom development.

Step 1: UX/UI design creation

The question of where to place the design phase in the workflow is somewhat controversial among development teams. Not every company puts it first.

At Whidegroup, we consider a design-first workflow the most efficient because it helps reduce the overall project timeline. While designers prepare page mockups and component specifications, developers can begin preparing the technical foundation for the migration.

Step 2: Hyvä installation and setup

The technical work starts in parallel with the design phase. Developers install the Magento 2 Hyvä Theme, configure related modules, and set up the basic storefront structure. This foundation allows the team to start customizing the storefront as soon as the design files are ready.

Step 3: Extension integration and compatibility work

The development team evaluates each extension included in the migration scope and determines whether native Hyvä compatibility already exists. Depending on the module, further work may involve installing compatibility packages, adapting front-end templates, or rebuilding storefront interactions to work with the Hyvä architecture.

Based on Whidegroup experience, features that often need particular attention include:

• Search
• Layered navigation
• Customer account functionality
• Payment methods
• Shipping modules
• Marketing tools

Step 4: Custom functionality development

Bespoke storefront functionality requires separate implementation in the Hyvä storefront. The most common customization requests in our experience include:

• Rebuilding product configurators
• Creating custom calculators
• Implementing loyalty program interfaces
• Adding B2B purchasing workflows to the existing retail store
• Developing customer account dashboards

Step 5: Storefront design implementation

Once the technical foundation is ready, developers build the storefront itself. This includes implementing the approved design across key customer-facing pages, such as:

• Homepage
• Category pages
• Product pages
• Shopping cart
• Checkout
• Customer account area
• CMS and landing pages

As part of the storefront implementation, developers create reusable UI elements which usually include buttons, banners, product cards, navigation menus, filters, and forms. Using these components across multiple pages helps our developers speed up the migration project and simplify future updates.

Step 6: Testing and launch

Before launch, the project team verifies that all migrated functionality works correctly in the new storefront.

At Whidegroup, our testing checklist includes, but is not limited to, the following steps:

• Extension integrations
• Customer accounts
• Product pages
• Cart behavior
• Checkout flows
• SEO elements
• Mobile usability

After validation, the storefront is deployed, and developers monitor its performance after launch to identify issues that may appear under real customer traffic.

How Much Does Magento 2 Hyvä Theme Development Cost?

Hyvä migration costs depend on catalog complexity, design scope, extension setup, and the required level of store customization. Below, we break down the main factors that affect the total cost. 

Key factors that influence Magento Hyvä development costs

• Design requirements:
  • Availability of ready-to-use Figma designs
  • Reliance on ready-made UI elements versus custom layouts
  • Total number of unique page templates
• Data complexity and catalog structure:
  • Using multiple product types (simple, configurable, bundled, or virtual)
  • Complex product attributes and layered filtering logic
  • Multi-store, multi-currency, or multi-language configurations
• Third-party extensions:
  • Total volume of modules that interact with the storefront
  • Number of extensions that lack native Hyvä compatibility
  • Amount of extension customization needed to match your workflows
• Checkout and transaction logic:
  • Number of payment gateway integrations
  • Complexity of shipping and tax rules
  • B2B purchasing logic implementation
  • Custom checkout flows
• Custom front-end functionality:
  • Advanced product configurators and builders
  • Dynamic, real-time pricing logic
  • Custom shopping cart behavior
  • Personalization rules and dynamic UI changes
  • Interactive blocks

These factors typically combine into projects of different complexity. At Whidegroup, we divide projects as shown below.

This table features our prices for existing stores migrating to Hyvä. To learn about the total cost of building a new Magento store from scratch with a Hyvä front end, read our dedicated article on Magento development costs.

Whidegroup Best Practices for Hyvä Theme Development

As an Adobe Bronze Solution Partner and Hyvä Supplier, Whidegroup has worked on both Hyvä migrations and custom storefront implementations. The recommendations below reflect challenges we see in real projects and can help merchants plan migrations more effectively.

Start with a store audit

Before requesting a migration estimate, document your current Magento setup as thoroughly as possible. Review not only the storefront but also the extensions, integrations, and custom modules connected to it. 

The more complete your inventory of existing functionality and planned changes is, the more accurately our development team can estimate timelines and costs.

Check extension compatibility early

After migrating eight Magento stores to Hyvä, our team found that extension compatibility is usually the largest variable in the overall project estimate.

When an extension lacks Hyvä support, replacing it with a compatible alternative is often more cost-effective than adapting the existing solution. We recommend custom development only when no suitable replacement exists. Experience with extension adaptation is therefore an important factor when choosing Hyvä developers for a migration project. 

Use a dedicated development environment

Before the project starts, make sure your development team plans to work in a separate environment with its own code repository and a copy of the production database.

Hyvä migration projects often take several months, during which your existing store remains active. An isolated environment allows developers to implement and test changes without affecting daily operations.

Minimize storefront changes during the migration

Large Hyvä projects can take more than five months to complete, while the existing Luma storefront continues serving customers. During this time, merchants often identify additional improvements they would like to integrate into the live store.

We have seen migration timelines extend significantly because functionality added midway through the project had to be recreated twice — once for the existing store and again for the Hyvä storefront. For this reason, we strongly recommend limiting new front-end features and design changes during the migration.

Avoid maintaining legacy Luma front-end components

Merchants sometimes keep highly customized Luma-based functionality to reduce redevelopment effort. However, maintaining both the Hyvä and Luma front-end stacks rarely lowers long-term costs.

This mixed setup makes development more complex, slows down troubleshooting, and increases compatibility risks with every upgrade to Magento, Hyvä, and extensions.

Don’t expect Hyvä to solve all speed issues

Hyvä provides a strong foundation for faster page rendering, but page load speed depends on more than the front end. Server capacity and configuration, database indexing, third-party integrations, and background processes can also affect store performance.

If these areas are not properly optimized, Hyvä migration alone does not guarantee the expected performance improvements.

Whidegroup Hyvä Migration Result: From Porto to Hyvä

The recommendations above are based on practical experience from Hyvä projects. The following case study shows how these principles translated into measurable performance improvements.

For a German garden plants store, Whidegroup migrated the storefront from the Porto theme to Hyvä. During the migration, we refined the user interface and adapted ten Magento extensions for Hyvä compatibility.

After launching the updated store:

• PSI performance score increased from 67 to 94.
• Largest Contentful Paint (LCP) decreased from 3.7 to 1.5 seconds.
• Cumulative Layout Shift (CLS) improved from 0.158 to 0.006.
• Total Blocking Time (TBT) grew slightly from 30 to 50 ms, but it remained within Google’s recommended range and did not affect the overall PSI score.

Overall, the migration increased the store’s performance score by 27 points and improved Core Web Vitals, which led to faster page loading and a better user experience. 

Final Thoughts

The decision about the Hyvä migration is rarely about an isolated speed optimization project. More often, it is a decision about how the storefront will evolve as the business grows. With the right implementation, Hyvä can improve store performance, streamline maintenance, and support ongoing improvements.

Not sure how Hyvä fits into your business plans? Request a free Hyvä migration consultation with our technical architect. We’ll review your current store, answer your questions, and help you make an informed decision about the next steps.

FAQs