What Is a Good LCP Score and Why Does It Matter for Your Website?

What is a good LCP score?

A good LCP score is 2.5 seconds or less. Google measures this at the 75th percentile of page loads, split by mobile and desktop, so at least three out of every four visits need to hit that mark for your site to count as "good." This threshold comes from Google's own Core Web Vitals documentation and is one of the signals Google Search uses when it looks at page experience.

What does LCP actually measure?

LCP stands for Largest Contentful Paint. It tracks the render time of the biggest image, text block or video that appears in the visible part of the screen, timed from the moment someone opens the page. In plain terms, it answers the question a visitor is actually asking: how long until the main thing on this page shows up?

It is not the same as a page feeling "loaded" in the browser tab. A page can finish loading in the background while the visitor is still staring at a blank space waiting for the hero image or headline to appear. LCP measures that wait.

What are the official LCP thresholds?

Google (via web.dev) sets three bands:

| Band | LCP time |

|---|---|

| Good | 2.5 seconds or less |

| Needs improvement | 2.5 to 4.0 seconds |

| Poor | more than 4.0 seconds |

Anything past 4 seconds is flagged as poor, both in Google's own tools and in the Chrome User Experience Report (CrUX) that feeds real-world data back into PageSpeed Insights.

How many websites actually hit a good LCP score?

Fewer than you'd expect. According to the May 2026 CrUX dataset, which tracks roughly 18.4 million origins, about 68.6% of websites achieve a good LCP score overall. LCP is the hardest of the three Core Web Vitals to pass: 68.6% of origins are good on LCP, against 81.3% on CLS and 86.6% on INP.

We saw the same pattern up close. In our own measurement of 125 law firm, solicitor and advocate websites (24-27 September 2026, Google PageSpeed Insights, mobile, one run per site), the median LCP was 10.1 seconds. The best site in the sample loaded its largest element in 0.8 seconds; the worst took 89.6 seconds. Of the 125 sites, 122 were over 2.5 seconds and 64 were over 10 seconds. Only a handful were in the "good" band at all.

Why does LCP matter for a small business website?

Two reasons, and they reinforce each other.

First, it is a ranking signal. Google folds Core Web Vitals into how it evaluates page experience, so a site stuck in "poor" territory is working against itself in search, on top of whatever content and backlink issues it may already have.

Second, and more immediately, it affects whether a visitor stays. Most small business traffic now arrives on a phone, often on a slower connection than a desktop user at home or in an office. If the main heading or hero image takes ten seconds to show up, a chunk of visitors will leave before they ever see what the business does. That is lost enquiries, not just a technical score.

Is a good LCP score enough on its own?

No. LCP is necessary but not sufficient. Google tracks two other Core Web Vitals alongside it:

• INP (Interaction to Next Paint): how quickly the page responds when someone taps or clicks. Good is 200 milliseconds or less.

• CLS (Cumulative Layout Shift): how much the page jumps around as it loads. Good is 0.1 or less.

Across the same May 2026 CrUX data, only 55.9% of tracked origins pass all three Core Web Vitals together. A site can nail LCP and still lose visitors to buttons that shift under their thumb or forms that take too long to respond to a tap. If you are checking your own site, look at all three, not just LCP.

What actually drives a slow LCP?

In our law firm sample, the median page weight was 3,468 KiB, with the heaviest page at 41,981 KiB. Heavy, uncompressed images and render-blocking scripts that load before the main content are the usual culprits. The fix is rarely exotic: compress and correctly size images, serve the page from hosting that responds quickly, and stop scripts from holding up the content the visitor actually came to see.

This is also why we build a year of hosting, SSL and support into every website we deliver, rather than leaving a client to figure out hosting speed on their own after the fact. A template website starts from GBP 500 and most go live within a week of us receiving the content, but the ongoing speed of the site depends on decisions made at build time: image handling, script loading order and the hosting underneath it.

How do you check your own LCP score?

Run your homepage and your two or three most-visited pages through Google PageSpeed Insights or the Chrome DevTools Lighthouse panel, on mobile. Look at the LCP number specifically, not just the overall performance score, since the overall score blends several metrics together. If LCP comes back over 2.5 seconds, start with the image at the top of the page; in our experience that single element is usually the biggest single lever.

Frequently asked questions

**Is LCP the same as page load time?**

No. LCP measures when the largest visible element has rendered, not when every resource on the page has finished loading in the background.

**Does a good LCP score guarantee good SEO?**

No. LCP is one of three Core Web Vitals, and Google also weighs content, links and many other factors; a fast page with thin content will not outrank a slower page with better content on its own.

**What LCP time counts as poor?**

Anything above 4.0 seconds is classed as poor by Google's own thresholds; between 2.5 and 4.0 seconds is "needs improvement."

**Why do so many small business sites fail LCP on mobile?**

Phones are the harder case, largely because mobile networks are slower and sites often serve the same heavy images and scripts to phones as to desktops.

**Can I improve LCP without rebuilding the whole site?**

Often yes. Compressing and resizing the largest image, removing unnecessary scripts from the page's initial load, and moving to faster hosting can bring meaningful gains without a full rebuild, though a badly structured site may need more than quick fixes.

Sources

• https://web.dev/articles/lcp

• https://developers.google.com/speed/docs/insights/v5/about

• https://developer.chrome.com/docs/crux/guides/pagespeed-insights

• https://developer.chrome.com/docs/crux/release-notes

• https://web.dev/articles/inp

• https://web.dev/articles/cls

• https://wepstech.com/blog/law-firm-website-speed-study