LCP issue: longer than 2.5s
Where you see it: Search Console → Experience → Core Web Vitals → Mobile or Desktop → Why URLs aren’t considered good
On a group of similar pages, more than a quarter of real Chrome visits in the last 28 days waited over 2.5 seconds for the largest image or text block to appear. Search Console adds (mobile) or (desktop) to the label, and this page covers both. Past 4 seconds, the group moves to Poor as LCP issue: longer than 4s.
Worth fixing on the templates people land on; Google still ranks the best answer.
Google’s ranking systems use Core Web Vitals, yet Google says a good report guarantees no top position, and the most relevant page still shows when its experience is poor. Fix the template the group shares, since one change there can move every URL in it.
Why it happens on WordPress
Find the LCP element first: an image and a block of text slow down for different reasons.
A hero or featured image bigger than the screen needs
The full-width homepage photo, or a featured image above the post title, often ends up as the LCP element. WordPress scales uploads over 2,560 pixels down to that size, which is still more than a phone displays, and a heavy file downloads slowly on mobile.
The LCP image is lazy-loaded
Core has lazy-loaded images since WordPress 5.5. Since 5.9 it loads the first content image, featured image included, at once; 6.3 counts classic-theme header images, doesn’t lazy-load the first three, and gives the first large image a fetchpriority of high. Core never overrides an attribute already set, so a theme or plugin that hard-codes lazy loading on the hero wins.
A hero the browser can’t see in the HTML
Some optimisation plugins move the image address into a data-src attribute and load it with JavaScript, and some theme headers set the photo as a CSS background. The browser finds the image late, and core’s attributes never reach it.
Slow server response
The wait for the first byte of HTML is part of LCP. Without a page cache, WordPress runs PHP and database queries on every visit; its handbook recommends a caching plugin that stores pages as static files, plus a CDN. Redirect hops add to the wait.
Render-blocking CSS and scripts
The browser won’t paint the LCP element until stylesheets in the head load, and synchronous scripts there hold it back. Themes, page builders and plugins that load their files on every page lengthen that queue.
Web fonts on a text LCP
Without a large image near the top, the LCP element can be the title or first paragraph. If that text stays hidden until a web font downloads, the font joins the LCP.
Sliders at the top of the page
A large slider above the fold often holds the LCP element. Sliders that build their slides with JavaScript start the first image late, and with autoplay any slide can become the LCP element.
How to fix it
Work one URL group at a time, logged out in a private window, on the device the row names.
1. Find the template behind the group
Open Experience → Core Web Vitals, click Open report next to Mobile or Desktop, and click the LCP row under Why URLs aren’t considered good. Each example URL stands for a group; click one to see others in it. All posts, or all products, means one template to fix.
2. Name the LCP element in PageSpeed Insights
Run an example URL at pagespeed.web.dev. Read the field data at the top first: Chrome UX Report data for the previous 28 days, for that URL or, if it has too few visits, the whole origin. Then filter the lab diagnostics to LCP to see the element and how its time splits between server response, load delay, download and render.
- For a second view, the Performance panel in Chrome DevTools can show your own LCP beside the field value and names the element. Turn on CPU and network throttling for a phone-like test.
3. Let the LCP image load at once
The LCP image tag should have no loading attribute set to lazy, and fetchpriority set to high. Inspect it in the DevTools Elements panel; if core set both, move on.
- An optimisation or caching plugin with lazy loading: exclude the hero image.
- A theme or builder setting that lazy-loads every image: turn it off for the hero.
- A CSS background hero: use an Image block instead, or preload the file through your theme or optimisation plugin.
4. Send a smaller file
Compress the hero and export it at the width your layout shows, in a lighter format such as WebP, then choose the new upload in the Image block or the Featured image panel. Where the block shows the image smaller than the file, pick a smaller Resolution in its settings.
5. Cache pages and cut the server wait
If most of the time comes before the first byte, turn on full-page caching: your host’s cache, or a plugin such as WP Super Cache or W3 Total Cache. Add a CDN once caching works, point internal links at final URLs, and ask your host about PHP and database speed if uncached pages stay slow.
6. Trim what loads before the LCP element
Deactivate plugins you no longer use, testing after each. In your optimisation plugin, defer JavaScript the first screen doesn’t need and minify CSS, then check menus and forms still work.
7. Replace the slider and settle the fonts
Replace a homepage slider with one static image or a Cover block; if it stays, turn off autoplay and pick a slider that puts the first slide in the page’s HTML. For a text LCP, load fonts with a font-display value such as swap, so text shows before the font arrives.
- WordPress 7.0 and later: Appearance → Fonts lists every font and variant. Clear the variants you don’t use and click Update.
What the 2.5s and 4s rows mean
The report reads the Chrome UX Report: field data from real visits. Group LCP is the time by which 75% of visits to a group’s URLs had shown their largest element. Groups short of data are folded into one group for the whole origin, such as https://www.example.com.
Each device is scored separately, and a group takes the slowest status among its metrics, so the same pages can be Good on desktop and Need improvement on mobile.
| Group LCP | Status | Row in the report |
|---|---|---|
| 2.5 seconds or less | Good | No LCP row |
| Over 2.5 seconds, up to 4 | Need improvement | LCP issue: longer than 2.5s |
| Over 4 seconds | Poor | LCP issue: longer than 4s |
Check the fix in Search Console
The report watches field data, so prove the fix in a test, then let real visits catch up.
- Rerun two or three example URLs in PageSpeed Insights. Lab LCP should now be under 2.5 seconds; the field numbers lag, since they cover the previous 28 days.
- In the report for that device, click the LCP issue: longer than 2.5s row, then Start tracking, which parts of Google’s help still call Validate fix.
- That opens a 28-day monitoring session and triggers no recrawl. The status goes from Started to Looking good, then Passed if no URL shows the issue for all 28 days.
- Failed means a URL still had the issue. Fix what is left, then click Start new validation.
If you never start tracking, the row can still clear as new data arrives; validation then shows N/A.
Can RankHive fix this?
No. LCP depends on your theme, page builder, images, cache and hosting, none of which RankHive changes. It can read your pages’ Chrome UX Report field data during an analysis, but the fix stays with you.
What it can’t do here
- Compress, resize or convert images, or change a post’s featured image.
- Change the loading or fetchpriority attributes your theme, page builder or plugins print.
- Change hosting, page cache, CDN or server settings.
- Edit theme files, page builder layouts, sliders or fonts.
- Click Start tracking in the Core Web Vitals report; its Search Console access is read-only.
Every change is drafted next to the current value and waits for your approval. Each one written is logged in the Change Log, with Revert.
Check the rest of your site while you’re here
The free site check reads your public pages for titles, meta descriptions, headings, canonical tags and schema, and shows what needs fixing. If you sign up, RankHive reads your Google Search Console data every week, drafts the fixes, and writes the ones you approve to WordPress. Nothing changes on your site until you say yes.
Common questions
Is LCP issue: longer than 2.5s bad for SEO?
Google’s ranking systems use Core Web Vitals, but Google says a passing report guarantees no top ranking and relevance comes first. Fix it for visitors first, on the templates search traffic lands on.
Why does PageSpeed Insights pass a page that Search Console flags?
Its score and lab numbers come from one simulated load on a mid-tier phone. Search Console uses 28 days of real visits on your visitors’ own devices and networks. Compare with the field data at the top of PageSpeed Insights, which shares that source.
Why is the issue only on mobile?
Each device is scored on its own, so a group can pass on desktop and fail on phones. The fixes are the same; test with throttling on, and check whether the mobile layout loads a different hero image.
Read next
Sources
Checked against these pages on .
- Google Search Console Help: Core Web Vitals report
- Google Search Central: Understanding Core Web Vitals and Google search results
- Google Search Central: Understanding page experience in Google Search results
- web.dev: Largest Contentful Paint (LCP)
- web.dev: Optimize Largest Contentful Paint
- web.dev: Best practices for carousels
- PageSpeed Insights: About PageSpeed Insights
- Make WordPress Core: Lazy-loading images in 5.5
- Make WordPress Core: Enhanced lazy-loading performance in 5.9
- Make WordPress Core: Image performance enhancements in WordPress 6.3
- Make WordPress Core: Introducing handling of big images in WordPress 5.3
- WordPress Advanced Administration: Optimization
- WordPress Advanced Administration: Cache
- WordPress Documentation: The Font Library