Magento frontend performance

Magento Performance Optimisation — Before You Consider a New Theme

Considering Hyvä for a faster Magento store? You might not need a new theme.

For established Magento Open Source and Adobe Commerce merchants, targeted improvements to a Blank or Luma-based frontend may be a sensible first step. Gerrard SBS investigates what slows your store down, then helps you choose between improving the theme you have and investing in a different frontend.

An evidence-led decision

Improve your existing theme or choose a new frontend?

Hyvä can be a good choice for a Magento store. The decision should reflect your business requirements, existing functionality and measured bottlenecks, rather than a Lighthouse score alone.

When Blank or Luma optimisation makes sense

Your current design and customer journeys still serve the business, but pages load assets they do not need or delay important content. A focused audit can establish whether page-specific delivery and rendering improvements offer a useful next step while retaining your existing frontend.

When Hyvä or a frontend rebuild may fit

A new design, different frontend architecture or substantial changes to customer journeys may justify a rebuild. Hyvä can be an appropriate option, with extension and checkout compatibility assessed against your particular store. An audit can also identify limitations that targeted optimisation will not resolve.

What gets investigated

Follow the critical rendering path

Investigate what the browser downloads, processes and waits for before useful content appears. Which files should load or change depends on the actual theme, Magento layout and installed extensions.

LESS-generated CSS and page-specific delivery

Measure the CSS used by representative pages, including unnecessary payload and delivery of styles-m.css and styles-l.css. Review LESS entry points, layout dependencies and page-specific assets before changing bundles. Required responsive and extension styles must remain available.

Render-blocking CSS and JavaScript

Assess critical CSS, deferred styles and the effect of CSS merging on page-specific delivery and caching. Merging is not automatically an improvement. Examine JavaScript overhead, third-party scripts and main-thread work before changing load order or removing dependencies.

Responsive images and LCP

Identify the Largest Contentful Paint (LCP) element on each page type. Review image sizing, srcset, modern formats and fallbacks, early discovery and appropriate loading priority. Preload only where measurements support it; avoid lazy-loading an image needed for the initial view.

Caching and hosting

Check full-page caching, Varnish or CDN behaviour where used, static asset delivery and server response times. Hosting capacity and backend delays can constrain frontend results. Distinguish cached catalogue requests from personalised and checkout journeys before recommending changes.

Measured changes, managed risk

Audit, improve, test and validate

  1. Establish a baseline

    Measure representative homepage, category, product, basket and checkout journeys. Record device, network and cache conditions so comparisons have context.

  2. Audit dependencies

    Trace theme, Magento core and extension assets to the features that use them. Prioritise changes by observed bottlenecks and business relevance.

  3. Make scoped improvements

    Agree a focused set of changes, implement them in a suitable test environment and keep a clear route to reverting changes if needed.

  4. Run regression testing

    Check responsive layouts, navigation, product options, extension interactions, basket and checkout behaviour. Preserve required functionality as asset delivery changes.

  5. Validate before and after

    Repeat measurements under comparable conditions, check for regressions and document improvements alongside remaining constraints.

Understand the measurements

Core Web Vitals and Lighthouse need context

Core Web Vitals cover loading (LCP), responsiveness (Interaction to Next Paint, or INP) and visual stability (Cumulative Layout Shift, or CLS). Field data describes real visits across devices and networks; CrUX data, where available, reflects an aggregated reporting window and will not immediately reflect a release.

Lighthouse provides controlled lab diagnostics that help investigate a page. A single lab run does not establish real-user Core Web Vitals or represent every page and device. Compare repeated mobile and desktop measurements, and monitor field data as it becomes available.

No specific Lighthouse score or Core Web Vitals result is guaranteed. Outcomes depend on the theme, extensions, content, hosting and customer conditions.

Protect your investment

Keep the functionality your store depends on

Optimisation should retain required Magento core, extension, responsive and checkout functionality. A file that appears unused on one page may support a product option, a different viewport or a later interaction.

Changes should respect the theme's dependency structure and Magento's static asset deployment, with documented decisions and upgrade compatibility checks. Future Magento, theme and extension updates need regression testing so performance improvements remain maintainable.

Published project evidence

Page-specific assets on a Magento store

The existing Magento performance case study describes dedicated category and product LESS entry points, prioritised critical category CSS and deferred non-critical CSS with a noscript fallback. Responsive product-image preloading and srcset improved early discovery of the likely LCP image, with WebP and AVIF used where available alongside fallbacks.

The published outcome is a more relevant frontend asset strategy and fewer unnecessary render-blocking dependencies. The case study does not publish quantified before-and-after scores.

Read the Magento performance case study

Plan the next step

Find out what your existing frontend can do

Discuss a focused performance audit and improvement project, or ongoing technical support. Share your store URL, Magento version if known and the journeys that feel slow.

Discuss your Magento performance

For broader maintenance and development, explore Magento support.