Magento performance benchmark, realistic 2026 ranges
What good looks like on a Magento store: the Core Web Vitals, server response and Lighthouse numbers I hold builds to, and what moves each one.
The live benchmark run is being rebuilt. Send a brief and the answer comes back written, with the workings.
Frequently asked questions
What's a good Lighthouse score for a Magento store in 2026?
Mobile 90+ is achievable on Hyvä with disciplined third-party JS management. Mobile 75+ is realistic on Mage-OS Breeze. Mobile 60+ is realistic on tuned Luma. Anything below 50 on mobile means there is an obvious win on the table, usually third-party JS or webfont configuration.
Are Core Web Vitals thresholds changing in 2026?
The three core metrics (LCP, INP, CLS) and their thresholds are unchanged in 2026. INP replaced FID as a Core Web Vital in March 2024; the threshold is ≤ 200ms for "Good". Google has not announced a fourth Core Web Vital for 2026, though TTFB, FCP and TBT are still measured as supplementary metrics.
Is Hyvä always faster than Luma?
In raw frontend-JS terms, yes, Hyvä ships roughly 10x less JavaScript than Luma. But "faster store" is a different question. If your bottleneck is TTFB, database joins, or third-party tags, Hyvä alone will not move the number. See the B2B case on the case studies page.
Should I move to Mage-OS Breeze instead of Hyvä?
Mage-OS Breeze is fine if your team prefers a Luma-like authoring workflow and you can live with a smaller compatible-module ecosystem. Hyvä is the safer commercial bet, wider module compatibility, larger Marketplace, more partners. The performance gap between them is real but smaller than the gap between either of them and Luma.
How accurate are Lighthouse lab scores vs CrUX field data?
Lighthouse is a deterministic lab measurement on a synthetic device profile; CrUX is real-user data over a 28-day window from Chrome users who opted in. They almost never agree perfectly. CrUX is the source of truth for Google ranking purposes. Use Lighthouse for fast iteration during development and CrUX to confirm the population-level shift after deploy.
Do these numbers include third-party tag impact?
The matrix ranges assume a "median" third-party load, Google Analytics, Meta Pixel, one chat widget. They do not assume an "extreme" load (30+ GTM tags, AB-test platforms, video pixels). With an extreme third-party load, all four theme stacks will fail Core Web Vitals.
What hosting do you recommend?
For a typical store: single-tenant VPS at 8 vCPU / 16GB RAM with NVMe storage, Varnish + Redis + MariaDB co-located, Cloudflare in front, PHP 8.3 with OPcache + APCu. Adobe Commerce on Cloud has its own constraints. Shared hosting is not viable for Magento 2, you will not hit the TTFB targets above.
How often should I re-benchmark?
Monthly Lighthouse + CrUX pull is enough for stable stores. Re-benchmark immediately after any deploy that touches the theme, head tags, third-party tags, FPC config, or the indexer. The number you care about is the trend over time, not the single-day reading.
Can you guarantee a specific Lighthouse score?
No, and any developer who guarantees a Lighthouse score is lying. I will commit to Core Web Vitals targets (LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1) in writing when the scope is right. Lighthouse scores fluctuate run-to-run and depend on factors outside any single developer's control (network, third-party vendors, Chrome version updates).
Send a brief. Get a written quote in 24 hours.
Two paragraphs is enough: scope, price and timeline come back in writing.