What we look for
In Google's PageSpeed Insights test (one lab load of each page), these pages took more than 2.5 seconds to show their largest image or text block (LCP, Largest Contentful Paint), but not long enough to rate Poor.
Why it matters
LCP is one of Google's Core Web Vitals (page experience scores), and this range is rated Needs Improvement. The sooner the main image or headline shows, the sooner the page feels ready.
How to fix
Make the largest element load sooner: compress and resize the main image, serve it in a modern format such as WebP, and remove scripts and styles that hold up drawing. A faster server response helps too.
What it cannot know
This is one lab load per page, run on Google's servers. Real visitors' times can differ.
Where you’ll see it
The id is stable, and every surface uses it, so it’s the thing to search for or hand to an agent.
- Terminal
- When it is one of the five findings under Fix first,
raptor crawlprints the id under it.Check: performance.
cwv_ lcp_ needs_ work - crawl.json and the CSV
- The crawl JSON names the finding by this id, and so do the CSV and
raptor_query."check_
id": "performance. cwv_ lcp_ needs_ work" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= performance. cwv_ lcp_ needs_ work - MCP
raptor_findingswith thischeck_idreturns the finding in full, with a fix brief ready to paste into a task. If it didn’t fire, it says why.raptor_
findings { "job_ id": ". . . ", "check_ id": "performance. cwv_ lcp_ needs_ work" }