At a glance the headline numbers for Layout shift count
How many layout shifts were captured during load.
The typical page shifts 1 time while loading.
Distribution & median INP site count and median INP at each level of layout shift count
Passing INP by layout shift count which level passes the INP most often
Layout shift count 1. p75 3. p99 39. At the low end (0): INP 48ms. At the high end (>p98): INP 50ms. computed
Why this matters for the Core Web Vitals, and where to start fixing it
The count says how often the page moves, not how far. A page with two shifts has two causes to find. A page with dozens shifts as a habit: lazy content arriving without reserved space, animations that run through layout properties, widgets that resize themselves after load.
CLS sums every shift inside a session window, so many small movements fail the threshold even when no single jump looks bad. When the count is high and the largest shift is small, stop hunting for one bug. Audit the patterns instead.
How does this affect the Core Web Vitals?
Layout shifts is part of the CLS itself, so this is arithmetic, not correlation. With few layout shifts, 83% of sites pass the CLS. With many, 65% do. The decline is gradual. There is no point where sites suddenly start failing.
Chrome field data from 189,915 sites, representing millions of real page loads. How we measured.