LCP: what it is and how to improve this Core Web Vitals metric
LCP measures how long it takes for the largest element on your page to load. Google wants it under 2.5 seconds. If you exceed that, your ranking pays the price.
Published on · Updated on · 11 min read
LCP (Largest Contentful Paint) is the time it takes for the largest element on your page to load. It can be an image, a video or a block of text. Google wants that time to be under 2.5 seconds.
If your site exceeds that limit, you have a problem. And it’s not a small one. Because LCP is one of the three Core Web Vitals Google uses to evaluate user experience. If you fail, your ranking pays the price. If you’re starting from scratch, begin with what Core Web Vitals are.
Here’s what actually works to improve this metric, on WordPress and on any other platform.
LCP on WordPress: practical solutions
If you use WordPress, your LCP usually depends on three things: hosting, images and plugins. Attack those.
- Switch to quality hosting. TTFB (time to first byte) should be under 200 ms. Hosts like Kinsta, WP Engine or SiteGround make a real difference.
- Optimize the largest image on the page. That’s your LCP. Convert it to WebP, compress it without losing quality and reduce dimensions where you can.
- Use lazy loading. Images that aren’t LCP should load later. It’s an order you shouldn’t skip.
-
Minimize the CSS and JavaScript that blocks rendering.
Plugins like WP Rocket or Asset CleanUp help you move critical CSS
into the
<head>and defer JS that isn’t needed for the first render.
Improvements aren’t immediate. But within weeks you’ll see LCP drop and your site breathe easier. If your WordPress needs care, check out why your WordPress needs maintenance.
LCP on Shopify: what you can do (and what you can’t)
On Shopify, your control is limited. But you’re not tied hand and foot.
- Choose a lightweight theme. Themes like Dawn or Sense are better optimized out of the box.
- Review the size of the first product image or the banner. That’s usually your LCP. Upload it in WebP with the exact dimensions you need.
- Limit frontend apps. Every app adds JS and CSS. Load only the ones you really need.
- Compress images and use lazy loading. Shopify already has native lazy loading, but checking that it’s enabled is free.
- Don’t overload the homepage. The fewer blocks and sections the page has, the faster the LCP will load.
If the problem persists, consider changing theme or reducing the number of active apps. Sometimes simplifying beats overloading.
How to audit your LCP step by step
Don’t guess. Measure and act on data.
- Use PageSpeed Insights. It gives you the LCP of each URL and tells you what’s failing. It’s the starting point.
- Open the Core Web Vitals report in Google Search Console. Identify which pages have issues. Prioritize the ones with the most traffic.
- Use Chrome DevTools: in the «Performance» tab, reload the page with «Reload and record coverage» and check the timeline. The LCP will appear marked.
- Try WebPageTest. Configure the test from real locations. It’s more detailed than PageSpeed Insights and gives you a visual breakdown of LCP.
The workflow is simple: measure, identify the element, optimize and measure again. If you don’t measure, you don’t improve.
| Tool | What it measures |
|---|---|
| PageSpeed Insights | LCP of each URL with lab and field data (CrUX) |
| Google Search Console | URLs with LCP issues based on real Chrome data |
| Chrome DevTools | LCP marked on the performance timeline |
| WebPageTest | Visual breakdown of LCP from real locations |
Tools to measure LCP (free and with real data)
- Google PageSpeed Insights (free): lab and field data (CrUX). Good for a first diagnosis.
- Google Search Console (free): it tells you which URLs have LCP issues based on real Chrome data.
- WebPageTest (free): advanced tests from multiple locations. Ideal for seeing CDN impact.
- Lighthouse in Chrome DevTools (free): measures the page locally and gives you recommendations.
- DebugBear (freemium): Core Web Vitals monitoring with historical data.
- Calibre (freemium): similar to DebugBear, with integrations for teams.
- GTmetrix (freemium): offers LCP metrics and recommendations.
Use more than one tool. What you see in PageSpeed doesn’t always match what your users experience. Cross-reference data. And if you want a broader list, check out free SEO tools in 2026.
LCP isn’t a number, it’s a symptom
Optimizing LCP isn’t a whim. It’s a signal that your site is well built, that the server responds, that images weigh just enough and that the code doesn’t drag.
If you improve LCP, user experience, conversion rate and ranking improve too. It’s not magic. It’s doing things right.
Start with what hurts most: hosting and the LCP image. Then go cleaning up what’s left over. Step by step.
And if you want to complete the strategy, check out how to improve INP, how to improve CLS and the complete Core Web Vitals guide: what they are and how to improve them.
If you want a specialist to audit and fix your LCP, I analyze your site, detect which element is penalizing your loading and give you a clear action plan with priorities. Tell me about your project and I’ll reply in less than 48 hours.
Want your site to load in under 2.5 seconds?
I audit your LCP, optimize your site’s loading and help you make Google and your users notice.