Book a Demo
MageDemo/About Luma

About Luma

Luma is the official reference theme for Magento 2, shipped by Adobe with every installation. It is the most widely-deployed Magento frontend in the world and the baseline against which all other themes are measured.

// the official magento theme

What Luma is

Luma was released with Magento 2.0 in 2015 as Adobe's showcase of what a Magento storefront should look like. It ships with every Magento installation and is used as the reference implementation by most third-party extension developers when they build frontend templates.

Its strongest attribute is ecosystem compatibility. Because most Magento extensions ship Luma-compatible frontend templates, a store running Luma can install almost any extension without additional frontend work. This makes it the safest choice for merchants with complex, extension-heavy configurations.

2015
Initial release
shipped with Magento 2.0
4.33MB
Average page size
vs ~0.67 MB for Hyvä
~30/100
Mobile Lighthouse
typical out-of-the-box score
// under the hood

The stack

KnockoutJSReactivity

A JavaScript MVVM framework used to bind UI components to Magento data. Powerful for its time but no longer actively developed, adding significant JS weight to every page.

RequireJSModule loading

An asynchronous JavaScript module loader. Luma relies heavily on RequireJS to manage its large number of frontend dependencies, resulting in large bundles and slow load times.

Less CSSStyling

A CSS pre-processor used for Luma's styles. Theming is managed through a deeply nested variable system, which is powerful but can be complex to override in child themes.

PHTMLTemplating

Magento's native templating format. Luma spreads logic across Layout XML files and PHTML templates, which adds flexibility but can make tracing rendering behaviour difficult.

// history

How Luma evolved

2015

Magento 2.0 is released alongside Luma as its official reference theme. Luma represents a complete rewrite of the Magento 1 frontend architecture.

2016–2018

Luma becomes the baseline for most Magento 2 agency builds. A large ecosystem of extensions with Luma-compatible frontend templates grows around it.

2019

Performance concerns begin to surface as Core Web Vitals gain importance. Luma's heavy JavaScript footprint consistently produces poor mobile Lighthouse scores.

2021

Hyvä launches as a performance-focused alternative. Luma remains the default and most widely installed theme, particularly for extension-heavy stores.

2022–2024

Adobe continues to ship Luma with Magento Open Source and Adobe Commerce. It remains the safest choice for stores that require broad third-party extension compatibility.

2025

Luma is still included with Magento and actively used in production stores worldwide. It remains the reference for extension developers and the standard fallback for complex builds.

// when to use it

When Luma is the right choice

Extension-heavy stores

If your store relies on many third-party extensions that include frontend output, Luma is the lowest-risk choice. Almost every Magento extension ships a Luma-compatible frontend template.

Existing Luma builds

For stores already running Luma with significant custom frontend work, a like-for-like Luma rebuild may be more cost-effective than a Hyvä migration — depending on the scope.

Large developer pools

The number of developers who know Luma is larger than those who know Hyvä. For teams without Hyvä experience, Luma has more available talent and documentation.

Reference and prototyping

Luma is Adobe's reference theme. Extension developers use it to test compatibility, and it remains the standard environment for Magento development and debugging.

// common questions

FAQ

Is Luma still a good choice for a new Magento store?

For stores with complex extension requirements or limited frontend development capacity, Luma remains viable. For new performance-focused builds, Hyvä is now the recommended default. Luma's full extension ecosystem is its key advantage.

Why does Luma score poorly on Core Web Vitals?

Luma loads a large amount of JavaScript through RequireJS — often 400–600 KB or more on a typical storefront. KnockoutJS adds further runtime overhead. The combined effect produces slow LCP, high JavaScript parse time, and frequent layout shifts, all of which hurt Core Web Vitals.

Can I improve a Luma store's performance without switching themes?

Partially. Techniques like full-page caching, CDN configuration, and image optimisation help at the infrastructure level. However, Luma's JavaScript architecture is the primary bottleneck and cannot be meaningfully addressed without replacing the frontend stack.

Will my Luma store stop working at some point?

Adobe continues to ship Luma with Magento. It will not suddenly stop working. However, KnockoutJS is no longer actively maintained, and the gap between Luma's performance and modern web standards will continue to widen over time.

Is migrating from Luma to Hyvä difficult?

The complexity depends on how much custom frontend work your store has. A standard Luma build with a few extensions can often be migrated to Hyvä within a few weeks. Stores with heavy custom UI work require more effort. Limely can scope a migration for your specific store.

See Luma for yourself

Browse a fully functional Luma storefront — and compare it directly with Hyvä.