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.
Get more from the Layout Shift Finder
How it works
- 1PASTE
Enter a page URL
Paste the page with a poor CLS score.
- 2SCAN
Find the culprits
Images without dimensions, font swaps, unreserved ad slots and injected headers are flagged.
- 3FIX
Copy the CSS fixes
Each issue comes with copy-paste CSS to reserve space and stop the shift.
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.
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.
- Enter a URL — the homepage or any page that scores badly on CLS.
- Read the culprit list — each finding names the elements involved.
- Apply the CSS fixes — dimensions, min-height guards, font fallback metrics.
- Measure the real number with the Core Web Vitals Checker.
- 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 cause | The fix |
|---|---|
| Images without dimensions | Add width + height attributes (or CSS aspect-ratio) |
| Font swap resizing text | display=optional, or swap + size-adjust fallback (local("Roboto") first — Android has no Arial) |
| JS-injected header/footer | Reserve exact space: #site-header{min-height:65px} — measure, don’t guess |
| Ad slots / embeds | min-height on the slot container matching the ad size |
| Animations moving layout | Animate transform/opacity only — never left/top/width/margin |
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.
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.
Site owners with a poor Core Web Vitals CLS score and developers debugging jumpy layouts.
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:
| Cause | What moves | Fix |
|---|---|---|
| Images or videos without size | Text jumps down when the media loads | Add width and height attributes, or CSS aspect-ratio. |
| Ads and embeds | Content shifts when an ad slot fills | Reserve the slot’s space with a min-height that matches the usual ad size. |
| Web fonts swapping | Lines rewrap when the custom font replaces the fallback | Preload the main font and use a fallback with similar metrics. |
| Banners inserted at the top | The whole page pushes down | Reserve space for cookie or promo bars, or show them as an overlay. |
| Animations using top/left/height | Elements around the animation move | Animate 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.
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.