Skip to main content
Best Web Developer logo
Language and currency EN £ GBP

Language

Currency

Prices on this site are shown in the currency you choose.

Insight

Cumulative Layout Shift: 12 Causes and Their Fixes

The 12 most common causes of cumulative layout shift and how to fix each one, with a diagnosis process, a priority table and Saudi-specific culprits such as Arabic font swaps and BNPL widgets.

  • 22 November 2026
  • 12 min read
  • Performance

Last updated: September 2026 · Reading time: 13 min · By the Best Web Developer team

Page elements jumping during load, illustrating cumulative layout shift causes and fixes
Most layout shifts come from content that arrives without reserved space. The fix is almost always to reserve it.

Quick answer

Cumulative Layout Shift measures how much visible content moves unexpectedly while a page is used. A good score is 0.1 or less. The most common causes are images and ads without reserved space, late-loading fonts, injected banners, layout animations and client-side rendering. Fix them by setting dimensions, reserving slots, matching font metrics and animating only transform and opacity.

Key takeaways

  • Good CLS is 0.1 or less at the 75th percentile of real visits; above 0.25 is poor.
  • Shifts within 500 ms of a tap, click or key press do not count, so user-triggered expansions are usually safe.
  • Four causes explain most problems we find: missing image dimensions, ad or widget slots, font swaps and injected banners.
  • Lab tools only see load; field data from real users captures shifts that happen later while people scroll.
  • Arabic web fonts and BNPL price widgets are frequent CLS sources on Saudi e-commerce sites.

What cumulative layout shift measures

Cumulative layout shift measures visual stability: how far and how much of the visible page moves without the user asking it to. It is one of Google’s three Core Web Vitals, alongside Largest Contentful Paint and Interaction to Next Paint.

A layout shift is any change in the start position of a visible element between two rendered frames. Each shift is scored as its impact fraction (how much of the viewport the moving content affects) multiplied by its distance fraction (how far it moved relative to the viewport). A banner that pushes 60% of the screen down by 25% of the viewport height scores about 0.15 on its own.

Shifts are grouped into session windows. A window closes after one second with no shifts or after five seconds in total, and the page’s score is the largest window. According to Google’s CLS documentation, a good score is 0.1 or less and a poor score is above 0.25, measured at the 75th percentile of page loads.

Why care? Unexpected movement causes mis-taps on the wrong button, lost reading position and a general feeling that a site is broken. On a checkout page, one shift at the wrong moment can mean an accidental order or an abandoned basket.


Causes 1 to 4: media, ads and embeds

Media that loads without reserved space is the most common source of cumulative layout shift. The browser draws the page, the file arrives, and everything below it jumps down.

1. Images without width and height

Without dimensions, the browser gives an image zero height until it downloads. Fix: add width and height attributes to every image, and keep height: auto in CSS. Modern browsers use the two values to calculate an aspect ratio and reserve the correct space at any screen width.

2. Responsive images with mismatched ratios

Art direction with a picture element often serves a 4:5 crop on mobile and a 16:9 crop on desktop, while the HTML declares only one ratio. Fix: set width and height on each source element, or use the CSS aspect-ratio property per breakpoint so the reserved box always matches the file that loads.

3. Ads and promo slots without reserved space

Ad networks fill slots at different sizes, and empty slots often collapse. Fix: give each slot a min-height equal to the most common creative size, keep the space when no ad is returned (show a house ad or a neutral placeholder), and avoid placing ad slots near the top of the viewport where a shift affects the most content.

4. Iframes and third-party embeds

YouTube videos, Google Maps, Instagram posts and review widgets usually resize after their script runs. Fix: wrap each embed in a container with a fixed aspect ratio, such as 16:9 for video, or a known height for review carousels. For heavy embeds, show a static preview image of the same size and load the real embed on tap.

Pro tip

Not sure what size an image really is? Drop it into our free Image Inspector to read its true pixel dimensions and aspect ratio, then copy those numbers into the width and height attributes. It takes seconds and removes the most common CLS cause on content pages.


Causes 5 to 8: fonts, CSS, banners and animation

The second group of causes comes from styling that arrives late or changes size. These shifts are often small individually but add up across a page.

5. Web font swaps

When a custom font replaces the fallback, text can change width and line height, reflowing whole paragraphs. Fix: preload the one or two fonts used above the fold, use a metric-matched fallback with the CSS size-adjust, ascent-override and descent-override descriptors, and consider font-display: optional for body text. Self-hosting fonts also removes a third-party connection.

6. Late or split CSS

If critical CSS is inlined but misses a component, that component renders unstyled and then jumps when the full stylesheet loads. Fix: generate critical CSS per template, not once for the whole site, and test it on the longest page of each type. Avoid loading layout-defining CSS through JavaScript.

7. Injected banners and notices

Promo bars, cookie notices, app-install prompts and “free delivery” strips inserted at the top push the entire page down. Fix: render them in the initial HTML with reserved height, or show them as overlays fixed to the bottom of the screen, which do not move other content. Never insert content above existing content unless the user asked for it.

8. Animating layout properties

Animations that change top, left, height, width or margin move surrounding elements and count as shifts. Fix: animate only transform and opacity. For expanding panels, animate a transform or clip effect inside a container whose final size is already reserved.

Chrome DevTools highlighting layout shift regions caused by a web font swap and injected banner
The Performance panel in Chrome DevTools marks each shift and the elements that moved, which makes diagnosis much faster.

Highlight: the banner rule that fixes most shifts

If a message can appear on a page, its space must exist in the first HTML response. That single rule covers promo bars, consent notices, stock alerts and instalment messages. In our audits, applying it across a theme often removes more than half of the measured layout shift in one release.

Causes 9 to 12: JavaScript and interaction

The last group comes from scripts that change the page after it first renders. These are the hardest to spot in lab tests because they often happen after load or during scrolling.

9. Client-side rendering, personalisation and A/B tests

When a framework hydrates, or a testing tool swaps a headline, content can change size after first paint. Fix: render the final variant on the server or at the edge, keep variants the same size, and avoid anti-flicker snippets that hide and then reveal the page. Personalised blocks should reserve the height of their largest version.

10. Lazy-loaded content and wrong-sized skeletons

Product grids, reviews and “related items” often load when they scroll into view. If the placeholder is shorter than the real content, the page jumps as the visitor scrolls. Fix: size skeletons to the real component, using the known number of items and card height, and start loading slightly before the section enters the viewport.

11. Carousels and sticky headers that resize

Sliders built with JavaScript often show all slides stacked before the script runs, then collapse to one. Sticky headers that shrink on scroll can also move content. Fix: style the carousel’s initial state in CSS so only the first slide shows, move slides with transform, and keep sticky headers at a constant height or use transform to shrink them.

12. Slow responses to user actions

Shifts within 500 ms of a tap are excluded, but if an accordion or “load more” button waits for a slow network request, the shift lands later and counts. Fix: expand the container immediately with a loading state of the right size, then fill it when data arrives. Keep interaction handlers fast, which also improves INP.

Highlight: our cumulative layout shift diagnosis process

1) Check field data in Search Console and PageSpeed Insights to find affected templates. 2) Reproduce in Chrome DevTools with a mobile profile and throttled network, recording while you scroll. 3) Read the layout shift entries to see which elements moved. 4) Add attribution with the web-vitals library to capture real-user culprits. 5) Fix, deploy, and wait 28 days for field data to confirm.


Key benefits of a stable layout

A stable page is easier to use, converts better and supports search performance. Most CLS fixes are cheap compared with their effect.

  • Fewer mis-taps: buttons stay where visitors expect them, especially on phones.
  • Better Core Web Vitals: passing CLS contributes to Google’s page experience signals.
  • Higher trust: a page that does not jump feels professional and safe for payment.
  • Easier reading: long Arabic or English articles keep the reader’s place.
  • Accessibility gains: users with screen magnifiers or motor difficulties lose their position less often.
  • Low cost: many fixes are a few lines of HTML or CSS per template.
“Every layout shift is a promise the page broke. Reserve the space first, and fill it when the content arrives.”
— Best Web Developer strategy team

Layout shift on Saudi Arabia websites

Saudi sites share the global causes but add three local ones: Arabic font behaviour, buy-now-pay-later widgets and seasonal campaign banners.

  • Arabic web fonts: Arabic typefaces often have taller ascenders and descenders than Latin fallbacks, so a swap changes line height across the page. Pick a system Arabic fallback with similar metrics and tune it with size-adjust.
  • Tabby and Tamara widgets: instalment messages under the price often load after the product page renders. Reserve a fixed height for the widget container on product and cart pages.
  • Ramadan, White Friday and National Day banners: campaign strips added through a theme app can push the whole page. Build a reserved banner slot into the theme.
  • Consent notices: PDPL-driven consent banners should be bottom overlays rather than top inserts.
  • Salla, Zid and Shopify apps: each installed app can inject content. Audit apps quarterly and remove those you no longer use.

Illustrative case: a Riyadh fashion store fixes its product pages

Challenge: A bilingual fashion store had a field CLS of 0.34 on mobile product pages. Search Console flagged 1,900 URLs as poor, and customers complained about tapping “add to wishlist” instead of “add to cart”.

What we did: Over three weeks and SAR 14,500, we added dimensions to gallery images, reserved 48 pixels for the Tabby widget, moved the free-delivery strip into the initial HTML, tuned the Arabic font fallback and replaced a JavaScript size selector that re-rendered after load.

Result: Field CLS fell from 0.34 to 0.04 within 28 days, all product URLs moved to “good”, and the mobile add-to-cart rate rose from 6.1% to 7.4% with no other changes.

Our technical SEO services include a Core Web Vitals audit with template-level fixes for Arabic and English pages.


All 12 cumulative layout shift causes compared

Start with the fixes that are cheap and high-impact. The table ranks each cause by how often we see it in audits and how much effort it takes to fix.

CauseHow often we see itFix effortCore fix
1. Images without dimensionsVery commonLowWidth and height attributes
2. Mismatched responsive ratiosCommonLowaspect-ratio per breakpoint
3. Ad and promo slotsCommon on publishersMediummin-height, keep empty slots
4. Embeds and iframesCommonLowFixed-ratio wrapper, facade
5. Font swapsVery commonMediumPreload, metric overrides
6. Late or split CSSOccasionalMediumPer-template critical CSS
7. Injected bannersVery commonLowReserved slot or bottom overlay
8. Layout animationsOccasionalLowTransform and opacity only
9. Hydration and A/B testsCommon on appsHighServer-render final variant
10. Lazy content and skeletonsCommonMediumCorrectly sized placeholders
11. Carousels and sticky headersCommonMediumCSS initial state, fixed height
12. Slow interaction responsesOccasionalMediumExpand instantly, fill later

Note: lab and field scores will differ

Lighthouse measures a single load without scrolling, so it misses shifts caused by lazy content, sticky headers and late widgets. Field data from the Chrome UX Report covers the full visit. Judge success by the 28-day field value in Search Console, not by a single lab run.


Frequently Asked Questions about CLS

What is a good cumulative layout shift score?

A good score is 0.1 or less, measured at the 75th percentile of real page loads on mobile and desktop separately. Scores between 0.1 and 0.25 need improvement, and anything above 0.25 is rated poor. Check the field value in Google Search Console or PageSpeed Insights rather than relying on a single Lighthouse test.

What causes high CLS most often?

The most common causes are images without width and height, ad or widget slots with no reserved space, web font swaps that change text size, and banners inserted at the top of the page after it renders. Together these explain most of the layout shift problems we find in audits, and each has a simple fix.

Why is my CLS good in Lighthouse but poor in Search Console?

Lighthouse records a single page load without scrolling or interaction, while Search Console uses field data from real Chrome users over 28 days. Shifts caused by lazy-loaded sections, sticky headers, late widgets or slow responses to taps only appear in the field. Record a DevTools trace while scrolling, or add web-vitals attribution, to find them.

Do layout shifts after a click count toward CLS?

Shifts that happen within 500 milliseconds of a tap, click or key press are excluded, because the user expects the page to change. Scrolling does not count as an input for this rule. If a click triggers a slow network request and the content shifts after 500 milliseconds, that shift is counted, so expand containers immediately.

How do Arabic fonts affect CLS on Saudi websites?

Arabic typefaces often have different line heights and widths from the fallback fonts shown while they load, so the swap can reflow whole paragraphs and move buttons. Preload the main Arabic font, choose a fallback with similar metrics, and tune it with size-adjust and ascent-override so the swap in Saudi Arabian bilingual sites causes little or no movement.

How long does it take for CLS fixes to show in Search Console?

Field data in Search Console and the Chrome UX Report uses a rolling 28-day window, so improvements appear gradually and are fully reflected about four weeks after deployment. You can confirm the fix sooner with lab tests and your own real-user monitoring, then use the validation feature in Search Console to track the affected URL groups.

Fixing cumulative layout shift for good

Cumulative layout shift comes down to one principle: reserve space for everything before it arrives, and move things only with transform and opacity. Work through the 12 causes in order of frequency, starting with images, widgets, fonts and banners.

For Saudi sites, add Arabic font tuning, BNPL widget slots and campaign banner slots to your theme. If you want a template-by-template audit, our Riyadh web design team can run one on your Arabic and English pages.

Stop your pages jumping

Send us your worst template. We will return a Core Web Vitals audit with the exact CLS culprits, fixes and a SAR estimate.

Get a free consultation See pricing
Tags: cumulative layout shift, CLS fixes, Core Web Vitals, page speed, web fonts, image optimisation, technical SEO, Arabic web fonts, Saudi e-commerce, Vision 2030

Want this handled for you?

We build and optimise sites like this every week. Book a free 30-minute call and we will tell you exactly what we would change on yours.

Get a free site review

Keep reading

Free strategy session

Let’s build something worth finding.

Tell us where you want the business to be in twelve months. We will come back with a costed plan, a realistic timeline, and the numbers we expect to move — no obligation, no jargon.

  • 30-minute call, no pitch deck
  • Fixed-price proposal in 48 hours
  • You own everything we build

Talk to a developer

Not a sales team

Response time
Within 1 business hour
Where we work
UK, USA & the Gulf
Contracts
No lock-in, monthly rolling
Working since
2023
infobestwebdeveloper.org
Free consultation

show prices in USD?

Get a free quoteWe reply within 1 business hour