LCP — loading
Largest Contentful Paint measures when the page's main visible content is rendered; a good experience is 2.5 seconds or less at the 75th percentile.
Core Web Vitals
Google's real-world page-experience metrics for loading speed, interaction responsiveness, and visual stability.
In plain language
Core Web Vitals describe three parts of a page experience: how soon the main content appears, how quickly the page responds to an interaction, and whether the layout unexpectedly moves. They are measured with real-user field data when enough data is available.
Core Web Vitals are useful performance signals, not a complete verdict on quality or a guarantee of search ranking. Lab tools help diagnose likely causes, while field data shows how eligible real visits behaved across devices and networks.
The foundation
What matters in Core Web Vitals
INP — responsiveness
Interaction to Next Paint reflects the delay across user interactions; a good experience is 200 milliseconds or less at the 75th percentile.
CLS — stability
Cumulative Layout Shift measures unexpected movement; a good experience is a score of 0.1 or less at the 75th percentile.
Applied by The Forge
How we put it into practice
We design performance budgets and production monitoring around the user experience behind the metrics—not around chasing a synthetic score in isolation.
Deliver the important content early
Server rendering, caching, optimized images and fonts, and deliberate loading priority reduce the wait for meaningful content.
Keep interactions responsive
Small JavaScript payloads, focused hydration, short tasks, and efficient handlers leave the main thread available for input.
Reserve visual space
Explicit media dimensions, stable components, and controlled font loading prevent content from shifting after it appears.
Measure lab and field data
Repeatable diagnostics catch regressions before release; real-user monitoring shows the experience across actual devices and networks.
A useful boundary
What it is not
- Core Web Vitals are not the same thing as a Lighthouse performance score.
- Passing the thresholds does not guarantee rankings, conversions, or a satisfying overall experience.
- A single local test cannot represent the range of real devices, networks, pages, and visitors.
A concrete example
A stable service landing page
The server sends the useful heading and hero content immediately, the image has reserved dimensions, and the contact button responds without a long JavaScript task. Field monitoring then confirms whether real visitors receive the same experience.
Further reading
Primary sources
These explanations are grounded in standards, primary research, and current platform guidance. The field will continue to evolve.
Related concept
Analytics & conversions: Analytics and Conversions
Using consent-aware measurement to understand website interactions and whether visitors complete outcomes that matter to the organization.