Skip to content
Visibl

Magento 2 + Hyvä development

Magento stores that load fast and sell more.

We build and rebuild Magento 2 stores on Hyvä, the lightweight frontend that replaces Luma's heavy JavaScript. The result is a store that passes Core Web Vitals, converts better and is cheaper to maintain.

Sound familiar?

Signs it is time to talk about Magento 2 + Hyvä

What we do

Magento work, from first commit to long-term support

Magento is powerful when it is built cleanly. We keep custom code to what the business really needs and lean on well-supported modules for the rest.

01

New Magento 2 builds

Catalogue structure, checkout, B2B features and multi-store set-ups, designed around how your team actually runs the shop.

02

Hyvä theme development

Custom Hyvä themes built with Tailwind CSS and Alpine.js. Far less JavaScript, faster pages and a frontend developers enjoy working in.

03

Luma to Hyvä migrations

We move existing stores to Hyvä step by step, including compatibility work for third-party modules, without losing SEO equity.

04

Performance and Core Web Vitals

Profiling, caching (Varnish, Redis), image pipelines and database tuning, with before and after measurements on real devices.

05

Integrations

ERP, PIM, payment, shipping, marketplaces and marketing tools connected through clean, monitored integrations.

06

Upgrades and support

Security patches, version upgrades, monitoring and a retained team that knows your codebase when something needs fixing fast.

In depth

How we approach it, in detail

01

What Hyvä actually changes in a Magento store

The default Luma theme loads RequireJS, Knockout.js and jQuery, plus a large set of UI components, on almost every page. Much of that code is downloaded and executed even when the page does not need it. Hyvä replaces the whole frontend layer with Tailwind CSS for styling and Alpine.js for interactivity, while the Magento backend, catalogue, admin and business logic stay exactly as they are.

Because Tailwind only ships the CSS classes a template uses and Alpine.js is a small library, the browser has far less to download, parse and run. Templates are plain PHTML with readable markup, so developers can follow what a page does without tracing layers of Knockout bindings. That also makes reviews, debugging and onboarding new developers quicker.

Hyvä Checkout is a separate product that replaces the standard Luma checkout with a server-driven checkout built on Magewire. It is designed to work alongside a Hyvä theme and gives us more control over steps, fields and payment integrations. We decide in discovery whether it fits your payment and shipping set-up, or whether a compatible alternative makes more sense.

  • Tailwind CSS and Alpine.js replace RequireJS, Knockout and most jQuery
  • Backend, admin and catalogue logic stay unchanged
  • Readable PHTML templates instead of nested UI components
  • Hyvä Checkout available as a separate, server-driven checkout
02

Core Web Vitals in plain words

Google measures page experience with three Core Web Vitals, collected from real Chrome users. Largest Contentful Paint (LCP) is how long it takes for the main content, usually the hero image or product photo, to appear. Interaction to Next Paint (INP) is how quickly the page responds when someone taps a button, opens a filter or adds to basket. Cumulative Layout Shift (CLS) measures how much the layout jumps while loading.

On Magento, poor LCP usually comes from slow server responses, oversized images and render-blocking assets. Poor INP comes from heavy JavaScript keeping the main thread busy, which is exactly where Luma struggles. CLS often comes from images without set dimensions, late-loading banners and fonts that swap after the page has drawn.

We look at both field data from Search Console and the Chrome UX Report, and lab tests in tools like WebPageTest. Field data tells us what customers experience; lab data tells us why. Fixes are measured on the same templates before and after, so you can see which change made the difference.

03

The performance architecture behind a fast store

A fast frontend still needs a well-configured server stack. Varnish serves full-page cache for anonymous visitors, so category and product pages do not hit PHP on every request. Redis or Valkey stores the Magento cache and sessions in memory. OpenSearch handles catalogue search and layered navigation, which keeps MySQL or MariaDB free for orders and stock updates.

In front of that we usually place a CDN for static assets and images, serve modern formats such as WebP or AVIF with correct sizing, and preload only the resources that matter for the first view. Cache invalidation is tuned so price or stock changes appear quickly without clearing everything at once.

We profile slow requests with tools such as Blackfire and New Relic, find the expensive queries, observers and plugins, and fix them at the source rather than hiding them behind more cache. The aim is a store that stays fast on uncached pages too, such as the basket, customer account and checkout.

  • Varnish full-page cache with sensible invalidation
  • Redis or Valkey for cache and sessions
  • OpenSearch for search and layered navigation
  • CDN, WebP or AVIF images and correct sizing
04

Integrations, B2B features and keeping Magento current

Most Magento stores sit in the middle of other systems. We connect ERP, PIM, warehouse, accounting and marketplace platforms through the Magento REST or GraphQL APIs and message queues, so heavy imports run in the background instead of slowing the storefront. Each integration gets logging and alerts, so a failed sync is noticed before customers see wrong prices or stock.

For B2B, Adobe Commerce includes company accounts, shared catalogues, negotiable quotes and requisition lists. On Magento Open Source, similar features can be built or added with established modules. We map your real buying process first: who orders, who approves, which prices apply, and how invoices and credit terms work. Only then do we choose between native features, a module and custom development.

Adobe releases security patches and version updates for Magento on a regular schedule, and newer releases raise the minimum supported PHP and service versions. We plan upgrades on staging with automated checks, test extensions and integrations, and deploy with a rollback plan. Staying current is cheaper than catching up after several missed releases.

Compared

Hyvä vs Luma

Both run on the same Magento backend. The difference is the frontend your customers download and your developers maintain.

CriterionHyväLuma
Frontend stackTailwind CSS and Alpine.jsRequireJS, Knockout.js, jQuery and LESS
JavaScript on page loadSmall, loaded only where neededLarge bundle on most pages
Core Web VitalsMuch easier to pass on mobileHard to pass without heavy tuning
Template codeReadable PHTML with utility classesLayered UI components and bindings
Frontend change effortUsually quick and predictableOften slow and fragile
Extension compatibilityNeeds Hyvä-compatible modules or adaptersWorks with most extensions out of the box
CheckoutHyvä Checkout or a compatible optionDefault Knockout-based checkout

Process

How a Magento project runs

  1. 1

    Discovery

    Workshops, audit of the current store and a scoped plan with timeline and budget.

  2. 2

    Design

    UX and UI for key templates, tested on mobile first, in your brand.

  3. 3

    Build

    Two-week sprints on staging, with demos so you see progress as it happens.

  4. 4

    Launch and grow

    Careful go-live with SEO checks, then ongoing support and optimisation.

What to expect

How results build up over time

  1. Weeks 1-2

    Discovery and audit

    We review the current store, extensions, integrations and analytics, list Hyvä compatibility gaps and agree a written scope and plan.

  2. Build phase

    Sprints on staging

    Templates, modules and integrations are built in short sprints. You review progress on staging and SEO checks run in parallel.

  3. Launch

    Careful go-live

    Load testing, redirect checks and tracking validation before switching over, then close monitoring of errors, orders and rankings.

  4. After launch

    Measure and optimise

    We compare field Core Web Vitals and conversion data with the old store and keep improving the templates that matter most.

Platforms

Our Magento stack

  • Magento Open Source
  • Adobe Commerce
  • Hyvä Theme
  • Hyvä Checkout
  • Varnish
  • Redis
  • OpenSearch
  • PHP 8
  • MySQL / MariaDB
  • Docker

Tools

The stack we work with

  • Blackfire
  • New Relic
  • PageSpeed Insights
  • WebPageTest
  • Chrome DevTools
  • Sentry
  • GitHub
  • GitLab
  • Screaming Frog

Deliverables

Part of every Magento project

  • Technical discovery and written specification
  • Hyvä-compatible module selection
  • Staging environment and version control
  • SEO-safe URL and redirect plan
  • Structured data on product and category pages
  • Analytics and ecommerce tracking
  • Load and performance testing before launch
  • Handover documentation and training

Working together

Pick the format that fits

Every engagement starts with a free first read of your site and goals. Then we agree on the format, scope and price in writing.

New build or Hyvä rebuild

New stores and Luma stores moving to Hyvä

A fixed-scope project from discovery to launch, with a written specification, sprint demos on staging and an SEO-safe go-live.

  • Technical discovery and specification
  • Hyvä theme and module compatibility work
  • Integrations and data migration
  • Launch support and post-launch fixes

Audit and rescue

Stores with performance, stability or upgrade problems

A focused review of code, extensions, server stack and Core Web Vitals, followed by a prioritised list of fixes we can carry out.

  • Code and extension review
  • Performance profiling and caching review
  • Security patch and upgrade assessment
  • Prioritised action plan

Support and development retainer

Live stores that need a steady, reliable team

A monthly plan with reserved development time, patching, monitoring and a team that already knows your codebase.

  • Security patches and version upgrades
  • Uptime and error monitoring
  • Reserved monthly development hours
  • Regular performance and SEO checks

FAQ

Questions we get

Why Hyvä instead of the default Luma theme?

Luma ships a lot of JavaScript that slows pages down, especially on mobile. Hyvä rebuilds the frontend with a fraction of the code, which usually means better Core Web Vitals, higher conversion and simpler maintenance.

Will our extensions work with Hyvä?

Many popular extensions have official Hyvä compatibility modules. For the rest we write the compatibility layer or suggest a better-supported alternative. We check this in discovery, before you commit.

Do you support Adobe Commerce as well as Magento Open Source?

Yes. We work on both editions, hosted on your infrastructure or on managed Magento hosting.

Will a rebuild hurt our rankings?

Not if it is planned properly. Our SEO team maps every URL, sets redirects, checks templates on staging and monitors the launch closely, so traffic is protected.

Can we move to Hyvä without redesigning the whole store?

Yes. A Hyvä migration can keep your current design, rebuilt on the new frontend. Many clients use the migration to fix known UX issues at the same time, but a full redesign is not required.

Does Hyvä work with Magento's GraphQL or a headless set-up?

Hyvä is a server-rendered frontend, not a headless one, so it does not depend on GraphQL for the storefront. It gives many of the speed benefits people look for in headless, with less complexity and fewer moving parts.

What do you need from us to start an audit?

Read access to the code repository, a copy of the database or a staging environment, admin access, and access to Search Console and analytics. We sign an NDA if needed and work on a copy, not on the live store.

Can you work with our in-house developers or current host?

Yes. We can work alongside an internal team, review their code, or take on specific parts of the project. We also work with your existing hosting provider and advise on configuration where it affects performance.

Related

Works well together

Let's look at your site together.

Tell us where you are and where you want to be. You get an honest first read, usually within one business day.