Magento Core Web Vitals: How to Hit Sub-1s LCP | AgenticEcom
Magento Core Web Vitals: How to Hit Sub-1s LCP
Headless & Performance

Magento Core Web Vitals: How to Hit Sub-1s LCP

• 3 min read • 0 views

Magento Core Web Vitals: how to hit a sub-1-second LCP

Core Web Vitals are Google's measurement of how a page actually feels to load and use — and they're a confirmed ranking input. Default Magento, with its heavy Luma theme, rarely passes them. Here are the targets, what breaks them on Magento, and the fixes in priority order — ending with the one that gets you to a 1-second LCP.

The three metrics and the thresholds

  • LCP (Largest Contentful Paint) — how fast the main content appears. Good: under 2.5s. Great: under 1s.
  • INP (Interaction to Next Paint) — how responsive the page is to taps and clicks. Good: under 200ms.
  • CLS (Cumulative Layout Shift) — how much the layout jumps around. Good: under 0.1.

What blows them on default Magento

The usual culprits: a slow server response (TTFB) before anything even starts; a heavy theme shipping render-blocking CSS and JavaScript; large, unoptimised images that dominate LCP; and content that loads in late and shoves the page around (CLS). Each is fixable; together they're why a stock Magento store often sits in the red.

The fixes, in priority order

  1. Cut TTFB. Full-page cache (Varnish), Redis for sessions and cache, and decent hosting. Nothing else matters until the server responds fast.
  2. Optimise images. Modern formats (WebP/AVIF), correct dimensions, and explicit width/height so they don't shift the layout. Images are usually the LCP element — fix them and LCP drops hard.
  3. Tame CSS and JavaScript. Inline critical CSS, defer the rest, and strip JavaScript you don't need. This is where INP is won or lost.
  4. Lazy-load below the fold and reserve space for anything that loads late, so CLS stays near zero.
  5. Go headless when you want to stop fighting the theme and start fast.

The shortcut: a front end that's fast by design

You can tune Luma for months and land somewhere decent. Or you can change the architecture. A headless Astro front end ships almost no JavaScript and serves pre-rendered HTML from the edge — which is how our live storefront returns a cold 96 Lighthouse and a 1.1-second LCP on a 1,000-product catalogue. Speed stops being a project and becomes the default.

Why this is worth the effort

Core Web Vitals feed three things at once: Google rankings, conversion rate, and how readable your store is to AI agents. It's the rare investment where SEO, sales and the future of commerce all agree — the case is laid out in the 2026 Magento SEO checklist.

96 Lighthouse, out of the box. The AgenticEcom Suite includes the headless Astro storefront and image optimisation that hit those numbers without the months of tuning — from £4,995 a year. See the Suite →

Frequently asked questions

What are good Core Web Vitals scores for a Magento store?

LCP under 2.5 seconds (ideally under 1s), INP under 200ms, and CLS under 0.1. Default Magento with the Luma theme often misses these without optimisation.

Why is my Magento store failing Core Web Vitals?

Usually slow server response, a heavy theme with render-blocking CSS/JS, unoptimised images, and late-loading content causing layout shift. Fixing caching, images and JavaScript — or going headless — resolves it.

Can Magento really hit a sub-1-second LCP?

Yes, with a headless architecture. Our live storefront scores a cold 96 Lighthouse with a 1.1-second LCP by serving pre-rendered HTML with near-zero JavaScript from the edge.