Slow main content
Usually a slow server response, a late-discovered hero image, or render-blocking CSS and JavaScript.
How to improve LCPFree SEO tool · Chrome UX Report data
Test a page with the same real-user data Google uses for Core Web Vitals. See LCP, INP and CLS for real Chrome visitors over the last 28 days, and whether the page passes.
Enter a page URL or a domain. Pages without enough Chrome traffic fall back to the whole site, like PageSpeed Insights.
Real-user results
This page doesn't have enough Chrome traffic on its own, so you're seeing data for the whole site, as PageSpeed Insights does.
FCP and TTFB aren't Core Web Vitals, but a slow server or first paint usually explains a slow LCP.
Thresholds
Google rates each metric at the 75th percentile of page loads, separately for mobile and desktop. A page passes when LCP, INP and CLS are all good; without enough INP data, LCP and CLS decide.
| Metric | Measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCPLargest Contentful Paint | Loading: when the largest image or text block appears | ≤ 2.5 s | 2.5 s – 4.0 s | > 4.0 s |
| INPInteraction to Next Paint | Responsiveness: delay from a tap, click or key press to the next frame | ≤ 200 ms | 200 ms – 500 ms | > 500 ms |
| CLSCumulative Layout Shift | Visual stability: how much content moves unexpectedly | ≤ 0.10 | 0.10 – 0.25 | > 0.25 |
| FCPFirst Contentful Paint | When the first text or image appears | ≤ 1.8 s | 1.8 s – 3.0 s | > 3.0 s |
| TTFBTime to First Byte | Server response, including redirects and connection setup | ≤ 800 ms | 800 ms – 1.8 s | > 1.8 s |
Thresholds: PageSpeed Insights documentation. Data: Chrome UX Report, the public dataset of real Chrome user experiences that PageSpeed Insights and the Search Console Core Web Vitals report also use.
Next step
Each metric has different causes. Start with the one rated poor, on the device with the most traffic.
Usually a slow server response, a late-discovered hero image, or render-blocking CSS and JavaScript.
How to improve LCPUsually long JavaScript tasks on the main thread, heavy event handlers, or third-party scripts.
How to improve INPUsually images and embeds without dimensions, late banners or ads, and web fonts that swap.
How to fix CLSNew to the metrics? Read the Core Web Vitals guide, or follow the Core Web Vitals audit process to check a whole site.
Good to know
Sources: Google Search Central and the Chrome UX Report methodology.
At the 75th percentile of page loads, LCP should be 2.5 seconds or less, INP 200 milliseconds or less, and CLS 0.1 or less. A page passes the assessment when all three are good.
The Chrome UX Report only includes pages and sites that are publicly discoverable and have enough visits from eligible Chrome users. Low-traffic pages, new pages and noindexed pages often have none. Try the domain instead, or measure the page with a lab test in PageSpeed Insights.
This checker shows field data: what real visitors experienced over 28 days, on their own devices and networks. Lighthouse is a single lab test on a simulated device. Core Web Vitals are assessed on field data, so use the lab test to find causes and the field data to confirm the result.
The Chrome UX Report covers the previous 28 days, so a fix appears gradually. Expect the full effect about four weeks after the change goes live, once the old page loads have left the window.
Google says Core Web Vitals align with what its core ranking systems seek to reward, and recommends achieving good Core Web Vitals for success with Search. They are one signal among many: relevant, helpful content still matters more.
Crawlens crawls your site, fetches real-user Chrome UX Report data for every indexable page, and runs Lighthouse tests on your key pages. Pages with poor LCP, INP or CLS show up as audit issues next to everything else.
Download free for Windows