⚡ CLS · Layout Stability

Layout Shift Finder

CLS killing your score? This scanner reads your page’s HTML and CSS and points at the exact culprits — images without dimensions, font swaps without fallback metrics, unreserved ad slots and JS-injected headers — with copy-paste fixes.

Layout Shift FinderYour tool. Connected workflows.
Free tool guide

Get more from the Layout Shift Finder

By the SocialKit.tools team · Reviewed 4 November 2026 · 100% free, no sign-up

3 quick steps

How it works

  1. 1
    PASTE

    Enter a page URL

    Paste the page with a poor CLS score.

  2. 2
    SCAN

    Find the culprits

    Images without dimensions, font swaps, unreserved ad slots and injected headers are flagged.

  3. 3
    FIX

    Copy the CSS fixes

    Each issue comes with copy-paste CSS to reserve space and stop the shift.

What you get

Key features

  • Finds CLS culprits

    Images and iframes without width/height, late fonts, injected banners and unreserved ad slots.

  • Severity order

    Issues are ranked by how much they are likely to move the page.

  • CSS fixes

    Copy aspect-ratio, min-height and font-display rules for each problem.

  • No account needed

    Paste a URL and get the result.

The complete guide

Layout Shift Finder: everything you need to know

It fetches your page’s HTML plus up to 6 stylesheets (same-origin and cross-origin CDNs) in your browser and runs a source-level audit for every known CLS cause: missing image dimensions, iframes without size, web-font loading strategy, @font-face without font-display, empty JS-injected placeholders with no reserved min-height, and CSS animations that physically move layout.

  1. Enter a URL — the homepage or any page that scores badly on CLS.
  2. Read the culprit list — each finding names the elements involved.
  3. Apply the CSS fixes — dimensions, min-height guards, font fallback metrics.
  4. Measure the real number with the Core Web Vitals Checker.
  5. Repeat until CLS ≤ 0.1 — Google’s “good” threshold.

Five things cause almost all CLS: images and iframes without width/height, web fonts swapping in at a different size, ads or embeds injected without reserved space, JS-built headers and widgets pushing content down, and CSS animations that move layout properties. Each has a one-line CSS fix shown below.

CLS causeThe fix
Images without dimensionsAdd width + height attributes (or CSS aspect-ratio)
Font swap resizing textdisplay=optional, or swap + size-adjust fallback (local("Roboto") first — Android has no Arial)
JS-injected header/footerReserve exact space: #site-header{min-height:65px} — measure, don’t guess
Ad slots / embedsmin-height on the slot container matching the ad size
Animations moving layoutAnimate transform/opacity only — never left/top/width/margin
People also search

CLS checker: common questions

If you searched for a CLS checker or cumulative layout shift checker, you probably saw “CLS issue: more than 0.1” in Search Console. Here is what CLS measures and how to fix the usual causes.

What is cumulative layout shift?

Cumulative Layout Shift (CLS) measures how much visible content moves unexpectedly while a page loads or is used. A score of 0.1 or less is good; above 0.25 is poor. Shifts that happen within 500 ms of a tap or click do not count.

Pro tips

Tips for better results

  • Always set width and height (or aspect-ratio) on images and embeds.
  • Reserve space for ads and cookie banners with a fixed min-height.
  • Use font-display: swap with a matching fallback font size.
  • Avoid inserting content above existing content after the page loads.
Who it’s for

Site owners with a poor Core Web Vitals CLS score and developers debugging jumpy layouts.

Fix guide

The five most common causes of layout shift

Cumulative Layout Shift (CLS) measures how much visible content moves unexpectedly while a page loads. Google’s “good” threshold is 0.1 or less at the 75th percentile of real visits. Most shifts come from a handful of causes:

CauseWhat movesFix
Images or videos without sizeText jumps down when the media loadsAdd width and height attributes, or CSS aspect-ratio.
Ads and embedsContent shifts when an ad slot fillsReserve the slot’s space with a min-height that matches the usual ad size.
Web fonts swappingLines rewrap when the custom font replaces the fallbackPreload the main font and use a fallback with similar metrics.
Banners inserted at the topThe whole page pushes downReserve space for cookie or promo bars, or show them as an overlay.
Animations using top/left/heightElements around the animation moveAnimate transform and opacity instead.

How to confirm the fix

Re-run this finder after deploying, then check the page in PageSpeed Insights. Lab results update immediately, but the field data Google uses for Core Web Vitals is a 28-day rolling average, so the official CLS value improves gradually after the fix goes live.

Privacy

How this tool handles your data

  • Public page fetch. To read a public web page, your browser requests it directly or through a public relay (a CORS proxy) because browsers cannot read other sites on their own. Only the URL you enter is sent; the analysis itself happens in your browser.
  • Google PageSpeed Insights. Speed, Lighthouse and Core Web Vitals checks send the URL you enter to Google’s PageSpeed Insights API. Google’s own privacy policy applies to that request.
  • No account, no tracking of your input. The tool is free with no login. Anonymous usage statistics (Google Analytics) and ads may use cookies only as described in our Privacy & Cookie Policy.
Answers

Frequently asked questions

0.1 or less is Google’s “good” threshold, 0.1–0.25 needs improvement, and above 0.25 is poor. CLS is measured across the whole page lifetime, so even a late-loading widget can ruin an otherwise perfect page.
Mobile is a single narrow column, so one shifting element pushes everything below it — the same 8px header jump that’s harmless on desktop can score 0.15+ on mobile. Media-query values (like a header’s mobile height) also differ and are easy to get wrong.
When the web font finishes loading it replaces the fallback font; if their letter sizes differ, every paragraph reflows. Fix it with font-display:optional (the swap never happens) or a size-adjust fallback @font-face so both fonts occupy identical space.
No — it’s a source-level scanner that finds the causes. For the measured number, run the Core Web Vitals Checker (same Google Lighthouse engine as PageSpeed Insights); use both together: measure, find, fix, re-measure.
Yes — reserve the exact final height in CSS before the JS runs (e.g. min-height on the placeholder). Measure the rendered element including borders; a guessed value that’s off by a few pixels still shifts the page.
Yes — free, no login. Your URL is fetched via public CORS services directly from your browser and nothing is stored.
Yes. Pages that reserve space for every image, embed, ad and font swap often score 0 or close to it. Anything at or below 0.1 already counts as good for Google.