What we look for
In Google's PageSpeed Insights test (one lab load of each page), these pages scored more than 0.1 for CLS (Cumulative Layout Shift, how much the content moves while loading), but not enough to rate Poor.
Why it matters
CLS is one of Google's Core Web Vitals (page experience scores), and this range is rated Needs Improvement. Even small jumps can make visitors lose their place.
How to fix
Give images, videos, ads and embeds a fixed width and height or reserved space in the page template, and avoid adding banners or content above what has already loaded.
What it cannot know
This is one lab load per page. Shifts caused by scrolling or tapping, which real visitors see, are not included.
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_ cls_ 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_ cls_ needs_ work" - The HTML report
- This link opens the finding in the report, and each finding shows its id.
crawl.
html# finding= performance. cwv_ cls_ 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_ cls_ needs_ work" }