Explainers · Explainer
What Is LCP? A Plain Explanation
Short answer
LCP, or Largest Contentful Paint, is the time it takes for the largest image, text block or video in view to finish rendering on a page. It marks the moment the main content has likely loaded, which is why Google uses it as a Core Web Vital. A good LCP is 2.5 seconds or less, and slow servers and large hero images are the most common causes of a bad score.
Key takeaways
- LCP measures when the largest visible image, text block or video finishes rendering.
- A good LCP is 2.5 seconds or less, and a poor one is over 4.0 seconds, as of November 2026.
- The largest element is often a hero image or a headline, not the whole page.
- LCP is judged at the 75th percentile of real page loads, split by mobile and desktop.
- Slow server response time is the first thing to fix, because LCP cannot beat TTFB.
What is LCP?
Largest Contentful Paint (LCP) is the time it takes for the largest image, text block or video in view to finish rendering.
It marks the point in the load when the page's main content has likely loaded. Older metrics such as load or DOMContentLoaded do not match what the visitor sees, and First Contentful Paint only captures the very first paint.
LCP was built to answer the question visitors actually ask: when can I read this page? The clock starts when the visitor first navigates to the page. It stops when the largest element renders, even if smaller pieces are still loading.
What counts as the largest element?
Google counts five kinds of elements for LCP: images, images inside SVG, videos, elements with a background image, and block-level elements that hold text.
| Element | When it counts |
|---|---|
| Image | When the image finishes rendering |
| Video | When the poster image or first frame shows |
| Text block | When the text renders with its web font |
| Background image | When the image loaded with url() renders |
The browser ignores some elements on purpose. Invisible elements with an opacity of zero do not count, and neither do images that cover the full viewport as a background. Placeholder images with little detail are also left out.
Size is measured by what the visitor can see. Parts of an element outside the viewport do not count, and margins, padding and borders are left out. For a resized image, the smaller of the visible size and the real size is used.
What is a good LCP score?
A good LCP is 2.5 seconds or less, and Google judges it at the 75th percentile of page loads, split by mobile and desktop.
| LCP | Rating | What it means |
|---|---|---|
| 2.5 seconds or less | Good | Main content appears quickly |
| 2.5 to 4.0 seconds | Needs improvement | Visitors wait longer than they should |
| Over 4.0 seconds | Poor | Main content is slow to appear |
The 75th percentile rule means three out of four visits must hit the target. A fast load on your own computer does not prove the page is fast for everyone. Check the field data in PageSpeed Insights, which comes from real Chrome users in the Chrome User Experience Report.
Mobile scores are usually worse than desktop scores, because phones are slower and often on weaker networks. If you can only fix one list, fix mobile first.
What slows down LCP on a WordPress site?
Four things cause most slow LCP scores: a slow server response, render-blocking scripts and styles, slow resource loading, and slow rendering of the largest element itself.
- Slow server response: the server takes too long to send the first byte, often from no caching or a weak host.
- Render-blocking CSS and JavaScript: the browser waits for files it does not need before it can paint.
- Large hero images: a 2 MB banner image takes far longer to load than a 200 KB one.
- Web fonts: text cannot count as the largest element until its font finishes loading.
- Too many plugins: each one can add scripts, styles and database queries to every page.
On WordPress, the server is often the first suspect. A page with no cache forces WordPress to build the page from the database on every visit, which takes time. A caching plugin serves a ready-made page instead, and that alone can cut LCP by seconds.
How do you check LCP on your WordPress site?
Run a URL through PageSpeed Insights and read the LCP value in the field data at the top.
The report also names the LCP element, so you can see whether it is an image, a video or a text block. That tells you what to fix first. If the element is an image, shrink it; if it is text, look at your fonts and your server.
Search Console groups your URLs into good, needs improvement and poor in its Core Web Vitals report. It uses the same field data, so it matches what Google sees. Use Lighthouse in Chrome DevTools when you need the cause of a single slow page.
Our guide to passing Core Web Vitals in WordPress walks through these checks in order, starting with the ones that take five minutes.
How do you improve LCP in WordPress?
Fix the server first, because LCP cannot be faster than the time to first byte. A caching plugin and a faster host give the biggest gain for the least work.
- Turn on page caching so the server sends a ready-made page instead of building one each time.
- Shrink the hero image and serve it in a modern format such as WebP.
- Preload the LCP image so the browser fetches it before anything else.
- Remove render-blocking CSS and JavaScript, or delay scripts the page does not need at once.
- Use a CDN so static files load from a server near each visitor.
For images, see our guide to serving images in next-gen formats.
For hosting, read whether hosting affects WordPress speed before you pay for an upgrade.
Check your result after each change with Lighthouse, which shows the new lab LCP at once. Field data takes up to 28 days to catch up, so do not wait for it to confirm a fix you already measured.
What mistakes should you avoid?
Do not optimize a small image while a huge hero image sits above it, because only the largest element sets the score.
- Preloading every image instead of just the LCP image, which slows the page down.
- Adding a caching plugin and skipping the hero image, which is often the real problem.
- Judging LCP from one Lighthouse run on a fast connection.
- Hiding the largest element to game the score, which only moves the problem to the next element.
Also avoid chasing a perfect score on pages that already pass. An LCP of 2.0 seconds is already good, and the time is better spent on pages that score over 4.0 seconds.
Does LCP affect Google rankings?
Yes, LCP is one of the three Core Web Vitals, and Google's ranking systems use Core Web Vitals. Its page experience guide says there is no single page experience signal, so LCP is one factor among many.
Relevance still decides most rankings. A fast page with thin content will not outrank a slower page that answers the query well. But when several pages answer it well, the faster page has the edge.
LCP also matters for visitors. People leave slow pages, and a page that shows its main content in under 2.5 seconds feels ready to read. That is worth fixing even if rankings never change.
If you want the full picture, read how fast a WordPress site should load and compare your LCP with typical load times.
Frequently asked questions
What is usually the LCP element on a WordPress post?
It is often the featured image or the main headline, whichever covers more of the screen. On pages with a large hero image, the image is usually the LCP element. PageSpeed Insights names the element, so you never have to guess.
Why does my LCP change between runs?
LCP depends on network speed, server load and cache state, so each run sees slightly different conditions. A cold cache and a busy server can add seconds. Compare the field data in PageSpeed Insights, which averages real visits over 28 days, rather than single lab runs.
Can LCP be faster than First Contentful Paint?
It can look that way in lab tools, because cross-origin images without a timing header report their load time instead of their render time. Google fixed this for Chrome 133, which now reports a slightly blurred render time even without the header, so the odd result is rarer now.
Does a CDN improve LCP?
Yes, if the LCP element is a file the CDN can serve, such as an image or a font. A CDN puts that file on servers near your visitors, so it arrives sooner. It does not help if the slow part is your WordPress server building the page, which needs caching instead.
Is 2.5 seconds a strict limit?
It is the line Google uses for a good score at the 75th percentile, not a hard limit for every visit. A page can have some visits above 2.5 seconds and still pass, as long as three out of four visits meet the target.
Sources
- Largest Contentful Paint (LCP) web.dev
- Web Vitals web.dev
- Time to First Byte (TTFB) web.dev
- Understanding Core Web Vitals and Google search results Google Search Central
- Optimization WordPress Developer Resources
- Overview of CrUX Chrome for Developers
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
