Largest Contentful Paint (LCP) Explained for Business Owners
Quick answer
Largest Contentful Paint (LCP) is the time it takes for the biggest visible element on a page, usually the hero image or main headline, to appear on screen. Google considers 2.5 seconds or less “good”, 2.5 to 4 seconds “needs improvement”, and over 4 seconds “poor”. The most common fixes are compressing and resizing the hero image, not lazy-loading it, improving server response time, and removing code that blocks the page from rendering.
If someone asked you, “How fast does your website load?”, what would you measure? The moment the first pixel appears? When everything has finished downloading?
Google’s answer is LCP. It’s the moment a visitor sees the main thing they came for. And because it tracks so closely with how fast a page feels, it’s the loading metric worth caring about most.
What is Largest Contentful Paint?
LCP measures, in seconds, how long it takes from when a visitor starts loading your page until the largest image or block of text in the visible area is fully displayed.
On most business websites, that largest element is one of these:
- A hero image or banner at the top of the page
- A large background image
- The main headline or opening paragraph, if there’s no big image
- A video’s poster image
LCP is one of Google’s three Core Web Vitals, alongside Cumulative Layout Shift and Interaction to Next Paint. Together they’re Google’s way of measuring real-world page experience.
What is a good LCP score?
| LCP time | Google’s rating | What visitors feel |
|---|---|---|
| 2.5 seconds or less | Good | The page feels quick |
| 2.5 to 4 seconds | Needs improvement | Noticeable wait, some people leave |
| Over 4 seconds | Poor | Feels broken on mobile; many visitors bounce |
When Google assesses real-user data, it looks at the 75th percentile. In plain English: at least three out of four visits need to hit the threshold for your page to pass. A fast experience on your office Wi-Fi doesn’t count for much if most customers visit on mobile data.
Why does LCP matter for your business?
There are two reasons, and the second is bigger than the first.
First, LCP is part of Google’s page experience signals. It isn’t the most important ranking factor (relevance and helpful content come first), but when two pages are similarly useful, a better experience can help.
Second, and more directly, slow pages lose people. Every second someone stares at a blank or half-loaded screen is a second they might hit “back” and tap the next result. If you’re paying for that click through Google Ads, you’ve paid for nothing.
Picture someone in Bellville searching “accountant near me” on their lunch break, on a patchy connection. Your page takes five seconds to show its headline. The competitor’s shows in two. Who gets the call?
How do you find your LCP?
Run your page through our free foundation checker or PageSpeed Insights. LCP is listed in the metrics section. In the full Google report, the “Largest Contentful Paint element” diagnostic tells you exactly which element is your LCP, which is gold, because it tells you what to fix.
Not sure how to read the rest of the report? Our plain-English guide to PageSpeed Insights walks through it.
What causes a slow LCP?
Google breaks LCP into four stages, and a slow result is almost always caused by one or more of them:
1. Slow server response. Before anything can load, your server has to respond. Cheap or overloaded hosting, no caching, or a server on another continent all add delay. Our article on whether your hosting is slowing you down covers this.
2. Late discovery of the LCP element. If your hero image is loaded by JavaScript, set as a CSS background, or lazy-loaded, the browser finds it late and starts downloading it late.
3. Slow download of the element. A 3 MB photo straight from a camera takes a long time on mobile. This is the most common problem we see on small business sites.
4. Render delay. Even after the image arrives, heavy CSS or JavaScript can stop the browser from painting it.
How to improve LCP: the fixes that usually matter most
Compress and resize your hero image
Serve the image at the size it’s actually displayed, not at 4000 pixels wide. Convert it to WebP or AVIF. This alone often takes seconds off mobile LCP. Our image optimisation guide has the details.
Don’t lazy-load the LCP image
Lazy-loading is great for images further down the page. For the main hero image, it’s counterproductive, because it tells the browser to wait. Many WordPress setups lazy-load everything by default, so check this.
Tell the browser it’s important
Adding fetchpriority="high" to the hero image, or preloading it, helps the browser fetch it first.
Improve server response time
Good hosting, page caching and a content delivery network (CDN) reduce the time before anything starts loading. For South African businesses with local customers, a server or CDN edge close to your visitors makes a real difference.
Reduce render-blocking code
Remove unused plugins, defer non-essential scripts, and avoid loading entire libraries for one small feature.
Rethink the slider
Homepage sliders with five large images are LCP killers, and visitors rarely click past slide one anyway. One strong, optimised image almost always performs better.
Common LCP mistakes
Fixing desktop and forgetting mobile. Desktop LCP is usually fine. Mobile is where it hurts.
Adding a speed plugin and assuming it’s solved. Caching plugins help, but they can’t fix a 4 MB hero image or a slow host on their own.
Optimising the homepage only. Landing pages for ads often have the worst LCP because they were built quickly with big visuals.
When to get help
Image compression and removing a slider are DIY-friendly. Server-level fixes, theme code and render-blocking issues usually need a developer. If your LCP is stuck above 4 seconds, it’s often a sign the site needs a proper performance rebuild rather than more plugins. That’s foundation work we do as part of our website design service.
Key takeaways
- LCP measures when the main content becomes visible.
- Good is 2.5 seconds or less, measured across at least 75% of real visits.
- The hero image is the usual culprit: compress it, resize it, don’t lazy-load it.
- Server response time and render-blocking code are the next places to look.
- Always prioritise mobile LCP.
Frequently asked questions
What does LCP stand for?
Largest Contentful Paint. It’s the time until the largest visible image or text block on a page is displayed.
What is a good LCP time?
2.5 seconds or less is good. Between 2.5 and 4 seconds needs improvement, and over 4 seconds is poor.
Does LCP affect SEO?
It’s one of Google’s Core Web Vitals, which form part of page experience signals. Content relevance matters more, but poor LCP can hold a page back and lowers conversions.
Why is my LCP fine on desktop but slow on mobile?
Mobile tests simulate a slower device and network. Large images and heavy scripts hurt much more under those conditions.
Should I lazy-load my hero image?
No. Lazy-load images further down the page, but load the main above-the-fold image immediately.
Test any page in about a minute with our free foundation checker.
Check my foundation