LCP discovery
How the browser found the LCP resource: HTML, CSS, JS, preload, or an early-hints header.
At a glance the headline numbers for LCP discovery
How the browser found the LCP resource: HTML, CSS, JS, preload, or an early-hints header.
The browser finds 68.4% of LCP images straight in the HTML. 0.8% hide behind JavaScript.
LCP discovery who uses what, and how fast each group loads
Little daylight between the groups: every variant sits near 48ms median INP. computed
Passing INP per LCP discovery which group passes the INP most often
No variant stands out: pass rates sit between 99% and 100%. computed
Why this matters for the Core Web Vitals, and where to start fixing it
The browser can only download what it has discovered, and the LCP's load delay is mostly discovery time. An image in the HTML markup is found by the preload scanner in the first bytes of the document. A CSS background image stays invisible until the stylesheet downloads and applies. An image injected by JavaScript stays invisible until that script downloads, parses and runs.
That order is the fix list. Get the LCP image into the markup, or preload it when it cannot be. Discovery through JavaScript is the slowest possible path for the most important pixels on the page.
How does this affect the Core Web Vitals?
LCP discovery correlates with the LCP. With HTML, 87% of sites pass the LCP. With JS, 75% do.
Chrome field data from 94,910 sites, representing millions of real page loads. How we measured.