2.2Intermediate8 min

LCP Optimization: The Hardest Core Web Vital

Lucas Blochberger·16 June 2026·Updated 11 June 2026

Definition

Largest Contentful Paint (LCP) measures the time until the largest visible content block is fully rendered. With only 62 percent mobile pass rate, LCP is the hardest Core Web Vital and the primary bottleneck.

Key Takeaways

✓LCP target is under 2.5 seconds, measured at the 75th percentile of real user data (CrUX); 2.5 to 4.0 seconds is considered needs improvement, over 4.0 seconds is poor.
✓LCP is the hardest Core Web Vitals metric to pass: only 62 percent of mobile pages achieve a good score, compared to 77 percent for INP and 81 percent for CLS.
✓On around 85 percent of desktop and 76 percent of mobile pages, an image is the LCP element; the most common LCP elements are hero images, large text blocks, and videos.
✓LCP breaks down into four subparts: Time to First Byte, Resource Load Delay, Resource Load Time, and Element Render Delay. Diagnostics show where time is actually lost.
✓The LCP image must never be lazy-loaded; modern formats (WebP/AVIF), fetchpriority=high and preload, plus a fast server (TTFB) are the most effective levers.
✓Field and lab data complement each other: Lighthouse shows the cause, CrUX/PageSpeed/Search Console show whether real users are affected. An optimization only counts once it shows up in field data.
✓Fast LCP measurably contributes to conversion and revenue and acts as a ranking tiebreaker; for Austria with around 44 percent mobile traffic, mobile LCP is the most important focus.

LCP is often the easiest Core Web Vital to improve, as optimizations are clearly defined.

The Four LCP Sub-Categories

Google divides LCP into four phases: Time to First Byte (TTFB, server response time), Resource Load Delay (delay until the LCP resource download starts), Resource Load Duration (download time of the LCP resource), and Element Render Delay (time to render after download).

Optimization Strategies

Server optimization: Bring TTFB below 800ms. Upgrade hosting, enable caching, use a CDN. A CDN can improve LCP by 30-50 percent.

Image optimization: AVIF as primary format (50% smaller than JPEG), responsive images with srcset, preload for the LCP image via link rel=preload, lazy loading only for images below the fold.

Render optimization: Inline critical CSS, eliminate or defer render-blocking JavaScript, preload fonts with link rel=preload.

LCP and AI Crawlers

AI crawlers typically wait only 1-5 seconds for a page. An LCP above 2.5 seconds means AI systems may see an incompletely loaded version of the page.

Data & Statistics

62 Prozent der mobilen und 74 Prozent der Desktop-Seiten erreichen einen guten LCP-Wert (unter 2,5 s); mobil zeigt mit 13 Prozent gegenueber 7 Prozent fast doppelt so viele schlechte LCP-Werte. LCP hat mit 62 Prozent die niedrigste mobile Bestehensquote der drei CWV (INP 77 %, CLS 81 %).

HTTP Archive Web Almanac 2025, Performance chapter (CrUX-Daten Juli 2025) [international] (2025)

Nur 48 Prozent der mobilen und 56 Prozent der Desktop-Origins bestehen alle drei Core Web Vitals; LCP ist die limitierende Metrik.

HTTP Archive Web Almanac 2025, Performance chapter [international] (2025)

Bei 85,3 Prozent der Desktop- und 76 Prozent der mobilen Seiten ist ein Bild das LCP-Element; text-basierte LCP-Elemente liegen mobil bei 23,7 Prozent.

HTTP Archive Web Almanac 2025, Performance chapter (LCP content types) [international] (2025)

Rund 16 bis 17 Prozent der Seiten lazy-loaden ihr LCP-Bild (seit 2024 stabil); native loading=lazy-Nutzung stieg auf Mobile von 9,5 auf 10,4 Prozent.

HTTP Archive Web Almanac 2025, Performance chapter (LCP lazy loading) [international] (2025)

JPG ist mit rund 57 Prozent das haeufigste LCP-Bildformat (minus 4 Prozentpunkte gegenueber 2024), WebP folgt mit 11 Prozent (plus 4 PP), AVIF erreicht 0,7 Prozent, PNG 26 Prozent.

HTTP Archive Web Almanac 2025, Performance chapter (LCP image formats) [international] (2025)

Eine 31 Prozent bessere LCP fuehrte zu 8 Prozent mehr Verkaeufen, einer um 15 Prozent besseren Lead-to-Visit-Rate und einer um 11 Prozent besseren Cart-to-Visit-Rate (A/B-Test, optimierte Seite 5,7 s vs. 8,3 s).

web.dev (Google) - Vodafone case study [international] (2021)

Im Retail-Segment steigerte eine um 0,1 Sekunden schnellere mobile Ladezeit die Conversion-Rate um 8,4 Prozent, den durchschnittlichen Bestellwert um 9,2 Prozent und die Page Views pro Session um 5,2 Prozent.

Deloitte Digital / Fifty-Five fuer Google - 'Milliseconds Make Millions' report (S. 17, Retail) [international] (2020)

Im September 2025 entfielen rund 44,4 Prozent aller Internet-Seitenaufrufe in Oesterreich auf mobile Endgeraete wie Smartphones (ohne Tablets, rund 1,9 %).

Statista (Daten von StatCounter) - Anteil mobiler Endgeraete an allen Seitenaufrufen in Oesterreich [Oesterreich] (2025)

FAQ

What is a good LCP value?

A good LCP value is under 2.5 seconds. Google defines three thresholds: good (under 2.5 s), needs improvement (2.5 to 4.0 s), and poor (over 4.0 s). What matters is the 75th percentile of real user data (CrUX), meaning 75 percent of actual page loads must meet the threshold. A good lab value alone is not enough if slower devices and connections push the percentile upward.

How can I optimize LCP?

Address the four subparts. Lower TTFB through server-side rendering, caching, CDN, HTTP/3, and Brotli. Deliver the LCP image in modern formats (WebP/AVIF) with correct dimensions, srcset/sizes, fetchpriority=high and preload, and never lazy-load it. Eliminate render-blocking CSS and JavaScript through critical inline CSS, defer/async, and font-display: swap with preload for web fonts.

What is the LCP element on a page?

The LCP element is the largest visible content block in the viewport. Typically these are hero images, large text blocks, or videos. In practice, images dominate: according to the HTTP Archive Web Almanac 2025, an image is the LCP element on around 85 percent of desktop and 76 percent of mobile pages. Which element specifically counts is shown by tools like PageSpeed Insights or Chrome DevTools.

Why is my LCP poor despite a fast image?

Because LCP consists of four subparts and the image affects only one of them. Often the bottleneck is at the server (high TTFB), in late discovery of the image (Resource Load Delay), or in delayed rendering due to JavaScript and CSS (Element Render Delay). In modern frameworks, the LCP element may be fully loaded but delayed in rendering by hydration. A subpart analysis shows where time is actually lost.

What is the difference between field and lab data for LCP?

Field data comes from real users and determines the official 75th percentile. Sources are CrUX, PageSpeed Insights, and Google Search Console. Lab data is generated synthetically under controlled conditions, such as with Lighthouse, and is suitable for testing before deployment and isolating causes. Both are necessary: lab data shows the cause, field data shows whether real users are affected. An optimization only counts once it shows up in field data.

Should the LCP image be lazy-loaded?

No. The LCP image must never be lazy-loaded, because this delays the start of loading and worsens the LCP score. According to the HTTP Archive Web Almanac 2025, around 16 to 17 percent of pages incorrectly lazy-load their LCP image. loading=lazy belongs exclusively on images below the fold. The LCP image should instead receive fetchpriority=high and a preload; in Next.js, the priority prop of next/image does exactly that.

How does LCP help for AI crawlers and GEO?

Fast server-side rendering, low TTFB, and minimal render-blocking JavaScript make content reliably accessible to AI crawlers and search engine bots as well. The same architecture that improves LCP facilitates delivery to AI crawlers. Important is the distinction: LCP is a performance metric for user experience, not a direct GEO factor. Generative Engine Optimization is determined by content, structure, and citability, not by load time. LCP improves accessibility but does not replace GEO measures.

How does your website perform?

Get a free, AI-powered SEO report of your website by email: technical SEO, on-page, keywords & competitors. No obligation.

Get a free SEO audit →

Previous← Core Web Vitals: LCP, INP and CLS Explained NextINP Optimization: Measuring and Improving Interactivity →