CLS (Cumulative Layout Shift)
Cumulative Layout Shift (CLS) measures how much visible content unexpectedly moves around while a page is open. It is the Core Web Vital for visual stability; a good CLS is 0.1 or less for at least 75% of visits.
You start reading an article, an ad loads above the text and the paragraph jumps down. Or you go to tap a link and a banner pushes it away at the last moment, so you tap something else. That is a layout shift, and Cumulative Layout Shift is the metric that measures it.
How it is calculated. For every unexpected shift, the browser multiplies two numbers: how much of the viewport was affected (impact fraction) and how far the elements moved (distance fraction). Shifts that happen close together are grouped into a session window: a burst of shifts with less than one second between them, lasting at most five seconds. CLS is the score of the worst window during the visit. Good is 0.1 or less, needs improvement is up to 0.25, and poor is more than 0.25, measured at the 75th percentile of visits.
Expected shifts do not count. Movement within 500 milliseconds after a click, tap or key press is excluded, because the user caused it. Opening an accordion is fine. Animations using CSS transform also do not trigger layout shifts.
Common causes:
- Images and videos without dimensions. The browser does not know how much space to reserve until the file arrives.
- Ads, embeds and iframes that load late and push content down, very common on publisher sites.
- Content injected above existing content, such as cookie bars, promo banners or "related articles" blocks inserted by scripts.
- Web fonts that swap in with different sizes than the fallback font.
- Lazy-loaded elements without placeholders.
How to fix it:
- Add width and height attributes to every image and video, or use the CSS aspect-ratio property, so the browser reserves the right space.
- Reserve a fixed slot for each ad position with a minimum height, even if the ad does not fill.
- Show cookie and promo banners as overlays at the bottom of the screen instead of pushing content down.
- Use font-display settings and size-adjusted fallback fonts to limit text reflow, and preload key fonts.
- Avoid inserting content above what the user is already reading, unless it is in response to their action.
- Animate with transform and opacity rather than properties that change layout, such as top or height.
Measuring it. Lab tools only capture shifts during the initial load. Real users scroll, wait and interact, so field data from Google Search Console, PageSpeed Insights or your own monitoring often shows a higher CLS than Lighthouse. The Performance panel in Chrome DevTools highlights which elements moved, which makes it much easier to find the culprit.
For publishers, CLS is often the hardest Core Web Vital, because ad slots and embedded content load at unpredictable moments. Reserving space for each slot and keeping the article column stable is good for rankings, for readers and for the advertisers whose content sits on the page.
Questions about CLS (Cumulative Layout Shift)
What is a good CLS score?
0.1 or less at the 75th percentile of visits. Between 0.1 and 0.25 needs improvement, and above 0.25 is poor.
Why is my CLS worse in field data than in Lighthouse?
Lighthouse only measures the initial page load. Real visitors scroll and stay longer, so shifts from late ads, embeds and lazy-loaded content are captured in field data but not in the lab test.
Do layout shifts after a click count towards CLS?
No. Shifts within 500 milliseconds after a user interaction are treated as expected and excluded from the score.