What Magento Frontend should you choose

Whether you are just starting your eCommerce adventure or you already have an established webshop, you might ask yourself which frontend to choose for your Magento shop. Maybe you are experiencing difficulties implementing new frontend features, or your shop is loading very slowly. Or maybe, you just want to get the best start for your Magento shop.


​​​​​​​While 2-3 years ago there was only one option for frontend except for something custom, nowadays the question “Which Magento Frontend to choose” makes you search and analyze a big variety of alternatives including PWA & headless solutions. So in this article, we saved you the time and did it for you.

As the most popular themes, we picked the Hyvä theme, Vue Storefront, Magento PWA Studio, and of course Luma.

The main criteria for comparison are:

  • Price if applicable

  • Additional hosting requirements, if any

  • Complexity of development

  • Development team and tech stack

  • Supportability and upgradability

  • Google page speed and google lighthpise scores

  • 3rd party extension support

Magento Luma


To be short, that’s the very default Magento frontend & theme that comes out of the box with the Magento application. 99.9% of Magento Frontend developers are experienced in the Luma theme, so such specialists are quite common and obviously familiar with Magento itself.
That was the first strongest side of Luma, and a second one is - support by 3rd party extension providers and extensibility. Every extension from a Magento Marketplace is developed and tested for and on Luma, which provides a possibility to save investments on custom development of functionality that might be covered by them.
However, the coin has its negative side. Simply saying, in many cases, the customization is reached by overwriting the components of the Luma theme or the extensions’, or the theme items that are already rewritten by the 3rd party vendors. That means that this approach makes them dependent and sensitive to backward-incompatible changes. So, as a result, the more 3rd party extensions you install and customize or just adjust to fit the design, the more difficult it would be to upgrade them and Magento itself. For large and heavily customized stores, up to 40% of the Magento upgrade time is being spent on updating the frontend, even if the design remains the same.
The second major disadvantage is the performance, which can be measured by a Google Page Speed Score as an example.


As we can see, the category page has scores of 49 for mobile and 79 for desktop.



Google Lighthouse report results except for SEO are also average. While part of the Lighthouse report ratings can be adjusted by proper Magento configuration and optimizing images, the Pagespeed score can be improved by investing in optimization. However, that’s hardly possible to have at least 90, also it will degrade with the time the new extensions and features are being delivered to the store or the page speed analysis algorithms are updated. It is inevitable because the default Magento 2 frontend framework represented by Luma is becoming more and more deprecated in the world of fastly developing Web technologies and approaches.

Hyvä Themes


As the Hyva themselves say about their product:
“One could say that Hyvä is the version of Luma we wished Magento had built. Or the frontend that Luma potentially could have become.”
It is an alternative to headless PWAs, for those that choose not to venture into the Javascript-only web.”
Hyva is being positioned as just one of the themes for Magento. But unlike all the traditional themes, it has the Magento frontend completely reimagined. It builds it from scratch in a brand new way rather than just inheriting the legacy approaches. So we can call it a theme technically, but in fact, it’s a new frontend.

What’s the difference? The Hyva developers used the best approaches of Luma like the traditional layout and templates system that is well known among the Magento developers and provides the extensibility, and replaced the worst ones. So Javascript frameworks and libraries like jQuery, RequireJS, and KnockoutJS are trashed in favor of AlpineJS, and the Less CSS is replaced by the Tailwind CSS framework.
 All these changes make it more modern which means much simpler to customize and more performant. Another point is - that Hyva requires frontend developers experienced with both, Magento and AlpineJs (or Vue.js which is very similar), which might be not so easy compared to the alternatives listed in the article.

​​​​​​​Also, Hyva provides a possibility to choose a checkout page frontend: use default Luma (or any custom) or Hyva Checkout. The Hyva Checkout is built using React JS library. It is not a full-value replacement for the default checkout but provides a base for building your own custom checkout that should be much easier than doing the same with the Luma.
Hyva PageSpeed Insight gives 100/100 performance score for the same category page:

Google Lighthouse report results also are looking awesome:



Besides the performance and being developer-friendly, another benefit is that Hyvä supports compatibility with numerous popular Magento extensions which are listed here. A side effect is that it becomes much easier to upgrade Magento and Hyvä: Hyvä cares about compatibility with 3rd party vendors, and native Magento frontend-related changes do not affect your store anymore.
At the moment, the Hyvä one-time purchase unlimited license that includes support on a private Slack costs only €1,000.00.


Vue Storefront


Vue Storefront is a standalone headless and backend-agnostic eCommerce Progressive Web App (PWA) written in Vue.js. Available freely via GitHub under the MIT open source license, users can also purchase commercial, cloud-hosted Storefront Cloud plans. PWA then facilitates the development of single, scalable and responsive apps compatible with every device or browser including iOS and Android. Delivering smaller and lighter-weight performance than native apps, Vue Storefront supports native platform functionalities such as push notifications, full-screen views, and home screen access, plus an offline mode that ensures eCommerce stores still function when web connectivity is compromised.
Open source features include a basic storefront template, Slack community access, and the PWA Storefront app, while the subscription-based Storefront Cloud adds cloud hosting, backups, and AMP rendering engine, and open loyalty program.
There is a Vue Storefront 2 that has a wider variety of features and structure, but its Magento integration is still beta and not ready for production, so let’s focus on Vue Storefront 1.
The strongest benefit of the VS except for the full-value PWA which has high scores in the SEO, Accessibility, and Performance best practices measured by Google Lightroom is platform independence. So this way you can upgrade Magento, migrate from Magento 1 to Magento 2 or even change the e-commerce platform without having the frontend affected. 
It is reached due to its architecture. Instead of calling the Magento application directly, it uses Vue Storefront API that responds with the previously indexed data or communicates with the Magento. Magento 2 Vue Indexer provides the data for a NoSQL Data Pump service that converts it and persists it in an ElasticSearch database that the storefront uses. That makes even large catalogs work blazing fast and the frontend to be available at least partially even if the Magento temporary is not.
Such an application would fit a cloud hosting ideally, but a single Virtual Private Server should be enough as well.


So to support and customize such an application it is needed to have a team of NodeJs developers for services communicating between Magento and storefront, and VueJs developers who will develop the frontend. In an ideal case, it should be a team or agency that is experienced in integrating Vue Storefront with Magento 2 because such a process requires a lot of communication between the teams and specialists working on very different pieces of a single complex system.
Vue Storefront provides paid integrations with a variety of headless CMS and payment services such as Adyen, Paypal, Braintree, Stripe, and others.

As we can see from the screenshots, despite all the advantages, the Google PageSpeed Insights scores are not high: 45 on mobile and 81 for desktop on a category page. Google Lighthouse report looks more optimistic:

Magento PWA Studio


Magento PWA Studio is a set of development tools to develop, deploy, and maintain a PWA storefront. It includes the Venia theme - a full-value PWA theme built using the PWA studio. They are being developed and supported by Adobe and Magento Community as an open-source project.


Official PWA Studio documentation recommends using Magento Commerce Cloud and special packages developed specifically to deploy and connect your storefront with Adobe Commerce software on the same server. However, it is also possible to install it on any other solution to host it, as a separate server or on the same one that runs the Magento application.
PWA Studio storefront and Venia theme are built on ReactJS, but it is also possible to develop a custom frontend using any frontend frameworks and libraries. It has a quite wide and strong community, and also it is not complex to work with for React JS developers. Moreover, unlikely Hyva, it is possible to separate the Magento and Storefront teams, so frontend developers are not required to be experienced in Magento at all which makes it easier to find a team of specialists for your storefront.
Since the storefront is a separate application with communicates with the Magento application mainly using GraphQL API, Magento upgrades are not likely to provide backward-incompatible changes and are expected to be smooth and easy, especially for non-major versions. However, if your frontend is based on the Venia theme, updating the PWA Studio itself requires manual changes comparison and updating your own templates making sure they are not conflicting.