Guide
What is CLS in Core Web Vitals? A plain guide
CLS measures how much a page moves while it loads. A good score is 0.1 or lower. Learn what causes layout shift and how to pass the check.
By Pratik Geet7 min read
CLS stands for Cumulative Layout Shift. It is the Core Web Vitals measure of visual stability, which means it checks how much a page's content moves while it loads. A good CLS score is 0.1 or lower.
If you searched for "CLS web vitals", this guide gives you the plain meaning, the score ranges, the usual causes of layout shift and the steps to pass the check. You do not need to be a developer to follow it. We explain each term as we go and point out where a developer is the right person to ask.
What is CLS in a website?
On a website, CLS is a score for how steady a page feels while it loads. Core Web Vitals are a small set of measures of how a page feels to use, and CLS is the one that covers movement. It looks at how the page moves while content appears on screen.
Here is an everyday picture. You open a shop page on your phone and start reading a product description. An image finishes loading above it and the text drops down the screen. You lose your place and have to find it again. It is irritating, but it is a small problem.
Now picture a worse one. You reach for a button and, at the last moment, a banner appears and pushes the button down. Your thumb lands on a different link instead. This is the kind of experience CLS is built to catch. A page with poor CLS scores creates confusion and frustration, and can even lead people to click on things they did not mean to.
For a business site, this matters because your visitors are often trying to do one simple thing: call you, fill in an enquiry form or book. A page that moves under their finger gets in the way of that. That is our reading of it, not a measured figure, but it is a good reason to treat layout stability as part of a healthy website.
Core Web Vitals definitions: LCP, INP and CLS
The three Core Web Vitals are CLS, LCP and INP. Each one looks at a different part of how a page feels to use.
- CLS (Cumulative Layout Shift) measures visual stability. In plain words: does the page stay still while it loads?
- LCP (Largest Contentful Paint) measures perceived load speed. In plain words: how quickly does the main part of the page seem to appear?
- INP (Interaction to Next Paint) measures page responsiveness. In plain words: when someone taps or clicks, how quickly does the page react?
A simple way to remember them: steady, quick to show and quick to respond. A page can do well on one and badly on another. A fast page can still jump around, and a very stable page can still feel slow. That is why people look at all three together.
The rest of this guide stays with CLS, because it is the one that is easiest to misunderstand. It is not about speed at all.
What is a good CLS score?
CLS scores fall into three ranges:
- 0 to 0.1: good
- Between 0.1 and 0.25: needs improvement
- Above 0.25: poor
Lower is better, because a lower score means less movement on the page.
Here is something that surprises many owners. CLS does not use seconds or milliseconds like the other Core Web Vitals. It is a unitless score, just a plain number. So do not look for "s" or "ms" next to it in a report, and do not read it as a time.
Passing is not about one visit. To pass the CLS assessment, at least 75% of a page's visits must achieve a good score. In plain words, most of the people who open the page need to have a steady experience, not just you on your own laptop with a good connection. A page can look fine to you and still fail if many visitors see it jump.
If a page sits in the needs improvement range, treat it as a to-do. If it sits in the poor range, move it up the list, because those are the pages where visitors are most likely to be put off.
What causes layout shift?
Layout shift happens when something on the page changes size or appears late, and the content around it has to move. The most common causes are:
- Images without set dimensions. If the page does not know how big an image will be, it cannot leave the right amount of room. When the image arrives, everything below it is pushed down.
- Web fonts that load asynchronously. A web font is a custom typeface the page downloads. "Asynchronously" means it arrives after the first text is already on screen. When it lands, the text changes shape and reflows, so lines move.
- Dynamic content like ads and pop-ups that load without reserved space. Banners, cookie notices, chat boxes and ads often appear after the page has started to display. If no room was saved for them, they shove the content aside.
The pattern is the same each time: the page did not know how much space something would need until it was too late. The fix follows the cause. Give images set dimensions, leave room for ads and pop-ups before they appear, and check how text behaves when a web font loads. The exact change depends on how your site is built, so this is usually a job for a developer who can look at the page.
If you are not sure which cause is behind a poor score, do not guess. Look at the pages that fail first, then match what you see to the list above. The Search Console report in the section below helps with that.
How do Core Web Vitals impact SEO rankings?
Core Web Vitals act as page experience signals that can affect how a site ranks in search. A page experience signal is a hint about how pleasant a page is to use.
It helps to keep this in proportion. These measures are one input among many. A page still needs to answer the question the searcher asked, have a clear title and be easy to reach through links on your own site. No one can promise a ranking from fixing CLS alone, and you should be wary of anyone who does.
There is still a good reason to fix it. A page that holds still is kinder to the people who visit, and those people are the reason you want to be found in the first place.
How to pass the Core Web Vitals assessment
Passing means at least 75% of a page's visits get a good score. Here is a practical order of work.
- Open the report. In Google Search Console, go to the Core Web Vitals report. It groups failing URLs by the specific issue, so you can see which problem affects which pages.
- Pick the biggest group first. Fixing one cause across many pages is often quicker than fixing pages one by one.
- Match the pages to the causes. Look for images without set dimensions, late-loading web fonts and ads or pop-ups with no reserved space.
- Make the fix. Give your developer the exact page and the exact cause. A clear task is far easier to finish than "make the site more stable".
- Check again. Once the change is live, look at the report again and keep the pass mark in mind: at least 75% of visits with a good score.
Can someone else make these fixes for you?
If your developer never gets time for the SEO fixes, this is where we can help. Deylaxy provides technical SEO fixes. Safe fixes are applied directly on WordPress or Next.js, and others go to your developer as exact step-by-step tasks, and then we check them live.
Nothing goes live without your approval, or you can choose to let small changes go ahead if you don't reply. We measure each change over 28 days and report results in clicks and enquiries.
If you want to see where your site stands first, the free website visibility audit covers technical issues, content gaps, local presence and the top fixes in priority order. If you would rather talk it through, you can book a demo.
The short version
- CLS is the Core Web Vitals measure of visual stability. It tells you how much a page moves while it loads.
- A good score is 0.1 or lower, and it has no unit.
- The usual causes are images without set dimensions, late-loading web fonts and ads or pop-ups with no reserved space.
- Google Search Console groups failing pages by issue, which tells you where to start.
Further reading: Cumulative Layout Shift explained, how to optimise CLS and a guide to Core Web Vitals and CLS.
Sources
Add Deylaxy as a preferred source on Google
Related on our website
More on this subject from us:
Read Deylaxy first on Google