MetricRaven

Performance

What is CLS (Cumulative Layout Shift)?

CLS (Cumulative Layout Shift) measures how much visible content moves unexpectedly while a page is open, scored as the largest burst of layout shifts. Google rates a CLS of 0.1 or less as good and over 0.25 as poor.

Updated

What CLS measures

CLS is the Core Web Vital for visual stability. You've seen the problem: you go to tap a button, an image or banner loads above it, the page jumps, and you tap something else. CLS puts a number on that. Movement that follows a click or tap within a short time doesn't count, because the visitor expected it.

Unlike LCP and INP, CLS is a score without a unit, not a time.

How CLS is calculated

Layout shift score = impact fraction × distance fraction

  • Impact fraction: the share of the viewport covered by the unstable elements, before and after they moved.
  • Distance fraction: the greatest distance any unstable element moved, as a share of the viewport's largest dimension.

Shifts are grouped into session windows: shifts less than 1 second apart, in a window of at most 5 seconds. CLS is the total of the window with the largest score, the largest burst, not the sum over the whole visit.

Good, needs improvement and poor

RatingCLS
Good0.1 or less
Needs improvementOver 0.1, up to 0.25
PoorOver 0.25

Judge it at the 75th percentile of real page loads, split by mobile and desktop.

Worked example

A cookie banner loads at the top of a product page and pushes the content down. The moved content covered 60% of the viewport before and after the move (impact fraction 0.6), and it moved by 25% of the viewport height (distance fraction 0.25).

Layout shift score = 0.6 × 0.25 = 0.15

Half a second later, a late font swap nudges the text again for 0.03. Both shifts fall in one session window, so CLS = 0.15 + 0.03 = 0.18: needs improvement. Showing the banner as an overlay instead of pushing the page removes the big shift.

How to measure and fix CLS

Measure it from real visitors, because many shifts only happen on slow networks or after scrolling. Lab tools like Lighthouse only see shifts during the initial load. The usual causes: images and embeds without width and height, ads and banners injected above content, web fonts that swap in at a different size, and content loaded late into the top of the page. Reserve space for anything that loads late.

Common CLS mistakes

  • Testing only the first load. Shifts after scrolling or late-loading widgets count too.
  • Forgetting consent and promo banners. They are a frequent source of big shifts.
  • Treating CLS as a time. A CLS of 0.2 is a score, not 0.2 seconds.

How MetricRaven measures CLS

With Page speed on (Settings, off by default, on every plan), MetricRaven's add-on built on Google's web-vitals library sends CLS with LCP, INP, FCP and TTFB in one snapshot per page load. In Pages → view all, hover a page's LCP or INP value to see its CLS at the 75th percentile, along with FCP, TTFB and how many loads it is based on. The Reports API returns the p50, p75 and p90 of CLS per page with include=speed.

CLS is not part of the slow-versus-fast buyer comparison, which uses LCP and INP only. See Page speed vs conversion.

Questions

What is a good CLS score?
0.1 or less at the 75th percentile of page loads. Between 0.1 and 0.25 needs improvement, and over 0.25 is poor.
What causes layout shift?
Images and embeds without set dimensions, ads or banners inserted above existing content, web fonts that load at a different size, and content injected late at the top of the page.
Is CLS the sum of all layout shifts?
No. Shifts are grouped into session windows (less than 1 second apart, at most 5 seconds long), and CLS is the score of the largest window.
Full glossary

Measure page stability from real visitors

MetricRaven records CLS, LCP and INP from real page loads and shows them next to each page's purchase rate.

14-day free trial, no card required.