What we look for
These pages scored below 90 out of 100 in Google's PageSpeed Insights test, a lab load of each page that rates its loading speed, but not low enough to rate Poor.
Why it matters
Google rates this range as Needs Improvement. The gains are smaller than on poor pages, but visitors on slow phones still feel them.
How to fix
Open each page in PageSpeed Insights (pagespeed.web.dev) and work through its suggestions, starting with those that save the most time.
What it cannot know
The score comes from one lab test per page and can move a few points between runs.
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_ score_ 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_ score_ needs_ work" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= performance. cwv_ score_ 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_ score_ needs_ work" }