SEO & PageSpeed
Website Page Jumps While Loading: What Layout Shift Is and How to Fix It

You open your own website on your phone, reach for the button you have tapped a hundred times, and the page lurches. The button slides away under your thumb and you land on something else entirely: a photo, a map, the wrong product. You go back, try again, and this time it works. Annoying. You move on.
Your customers do not move on so politely. That lurch has a name, layout shift, and Google measures it on real visitors' phones as one of its three Core Web Vitals. It is also one of the few speed problems that no amount of server horsepower fixes by itself, which is why I think it deserves its own guide rather than a line in a general WordPress performance guide.
This is a reference piece. It covers what is actually being measured, the five things behind almost all layout shift on small business WordPress sites, how to find which one is moving your pages, and how to fix it without breaking anything else. Skip to whichever section you need.
What Layout Shift Actually Measures
A layout shift happens when something already on the screen moves because something else arrived late. Google's developer guide to Cumulative Layout Shift on web.dev defines it plainly: a shift occurs "any time a visible element changes its position from one rendered frame to the next." The score, known as CLS, adds up how much of the screen moved and how far, grouped into bursts.
Three details matter far more than the maths.
The thresholds Google uses
A CLS of 0.1 or less is good. Anything above 0.25 is poor. Google judges those numbers at the 75th percentile of page loads, separately for mobile and desktop, which in plain terms means roughly three out of every four visits need to be stable before the page counts as good. A page that behaves on your office broadband but jumps for one phone visitor in three does not pass.
Only unexpected movement counts
web.dev puts it neatly: "A layout shift is only bad if the user isn't expecting it." If a visitor taps "Show more reviews" and the page grows, nobody is surprised, so shifts within 500 milliseconds of a tap, click or keypress are excluded. Scrolling is treated differently. It does not count as that kind of input, so content that jumps while someone scrolls still counts against you.
The worst burst sets the score
CLS takes the worst burst of movement during the whole visit, where a burst is a run of shifts less than a second apart, capped at five seconds. One bad lurch as the page loads can set the score for everything that follows.
The practical upshot is reassuring, in a way. This is not a lab number from a test server on another continent. It comes from real people using Chrome on real phones, which makes it one of the more honest numbers in web performance. If yours is poor, your customers genuinely are watching your page move.
Why a Jumping Page Costs More Than a Score
The ranking effect is real but modest, and I would not oversell it. Google's own page experience documentation states that "Core Web Vitals are used by our ranking systems", then adds that good results do not guarantee top rankings, and that Google "always seeks to show the most relevant content, even if the page experience is sub-par." A stable page will not rescue thin content. Where you and a competitor are equally relevant, it can help tip the balance your way.
The bigger cost is the tap that lands in the wrong place.
The tap that lands on next June
Consider a composite case, built from common patterns rather than one business: a kayak hire outfit in Leitrim selling Christmas gift vouchers in late November. Its homepage has a "Buy a Gift Voucher" button near the top. Above it sit a review carousel and a booking calendar, both loaded from outside services. On a phone with patchy signal, the voucher button appears first, and the customer reaches for it. Half a second later the calendar arrives, shoves everything down, and the tap lands on a date next June.
Now they are in a booking form for a trip they never wanted, on a small screen, with a Christmas deadline in their head. Some back out and try again. A few give up and ring. A fair number simply close the tab and buy a voucher from whoever made it easier. Nobody emails the owner to say the page moved. That is the trouble with layout shift: the losses are silent, and the owner, testing on fast Wi-Fi where everything loads at once, never sees it happen.
The same thing plays out in every sector. On a shop, a shift turns "Add to basket" into a tap on the wrong size. A restaurant site with a late banner sees "Call to book" pushed down just as the thumb lands, and the visitor opens the menu instead. Over on a services site, the reader loses their place in your prices every time something loads above them, and eventually stops reading.
The Five Usual Culprits on a Small Business Website
Almost every jumping page on an owner-run WordPress site traces back to one of five things. The table is the map, and each section below takes one row in turn.
| Culprit | What visitors see | The usual fix |
|---|---|---|
| Images without dimensions | Text jumps down as each photo appears | Keep the width and height WordPress sets; never strip them |
| Embeds and widgets | Page lurches when reviews, maps, booking calendars or feeds arrive | Reserve the space, or move the widget lower down |
| Banners and cookie notices at the top | The whole page drops as a notice slides in | Overlay at the bottom of the screen instead of pushing content |
| Web fonts | Lines rewrap a moment after the page appears | Fewer fonts, hosted locally, loaded early |
| Animations and sliders | Content around a slider or animated header twitches | Use effects that move the element, not the layout |
Images without dimensions
A browser that does not know an image's size reserves no space for it. When the photo finally arrives, everything beneath it gets shoved down. Google's guide to optimising CLS says to "always include width and height size attributes on your images and video elements", and points out that even a slightly wrong ratio "still causes less layout shift than the 0x0 default size of an image with no dimensions provided."
WordPress has handled this for uploaded photos since version 5.5. The core team's announcement in July 2020 explained that WordPress "will start back-filling width and height attributes on img tags" where they are missing, so the browser can work out the layout before the image loads. There is small print, though. It only works for images that come from your Media Library. Images pulled in by a theme, set as a page builder background, or pasted in as a link to another site can slip straight through.
How common is the gap? The HTTP Archive's 2025 Web Almanac puts it at roughly six in ten mobile pages leaving at least one image without dimensions, with a median of about two per page. Those figures cover the whole web rather than small business sites specifically, so treat them as a broad signal. On a menu or price list full of photos, every unsized image is another small jolt while your customer is trying to read.
Embeds and widgets
On small business sites this is the big one. Review carousels, social feeds, Google Maps, booking calendars, chat bubbles and newsletter boxes nearly all load from another company's servers after your page has already appeared. Google's guide is blunt that "platforms offering embeds don't always reserve space for their widgets", and it names ads as "one of the largest contributors to layout shifts on the web."
Two fixes cover most cases:
- Reserve the space. A container with a fixed minimum height means the widget fills a gap that already exists instead of forcing everything apart. Many page builders and widget plugins have a height setting for exactly this.
- Move it down. Google's guidance notes that content injected near the top of the screen causes bigger shifts, and recommends placing it later on the page. A review carousel below the main button still builds trust without moving the button.
Reserving space has a limit worth knowing before you rely on it. If a widget's height varies, say a carousel that shows a two-line review one day and a ten-line review the next, a fixed space will either leave an awkward gap or still shift a little. Google's guide also warns that "removing the space set aside for elements can cause just as much CLS as inserting content", so a widget that fails to load and collapses its box creates the very movement you were trying to prevent. Pick a height that fits the typical case, and accept that some widgets are better moved than boxed.

Banners and cookie notices at the top
A notice that slides in from the top, whether a cookie banner, a free delivery strip or a "last order date for Christmas" announcement, pushes the entire page down the moment it appears. Google's best practices for cookie notices say it directly: "Top-of-screen cookie notices are a very common source of layout shift."
The recommended fixes are simple. Either reserve space for the notice from the very start, or show it as a bar fixed to the bottom of the screen or a small pop-up that sits over the content rather than inside it. Footer placement, the same guide says, "typically does not cause CLS."
The legal position does not change with the layout. Your consent obligations are exactly the same whichever edge of the screen the banner sits on. Only the movement changes.
Web fonts
Custom fonts load separately from your text. Until they arrive, the browser shows a fallback font, then swaps, and because the two are rarely the same size, lines rewrap and paragraphs grow or shrink. Google's guide says both common loading approaches "can cause layout shifts", and recommends loading key fonts early and matching the fallback font's size as closely as possible.
My colleague Ian covered the font side in detail, including the GDPR problem with fonts pulled from Google's servers, in his piece on the font on your WordPress homepage. The short version is fewer fonts, hosted on your own site, loaded early. A heading that rewraps from one line to two pushes everything under it down by a full line, including whatever button the visitor was about to tap.
Animations and sliders
Some animations move the element itself. Others change its position in the layout, which drags its neighbours along with it. The Web Almanac found layout-affecting animations of this kind on roughly four in ten mobile pages in 2025. Google's guide advises against animating an element's position and recommends effects built on transforms, because those "can't impact other elements, and so don't count toward CLS."
Homepage sliders that resize between slides of different heights are the classic offender. The text below twitches every few seconds for as long as the visitor stays. You do not need to know what a CSS property is to act on this: if something on your page moves and the content around it moves too, that effect is the conflict. Switch it off, or pick a different style in your theme settings.
How to Find What Is Moving Your Pages
Start with evidence rather than a guess. Three sources, in order:
- Search Console. The Core Web Vitals report groups your pages by status and flags CLS problems separately for mobile and desktop. If a group of pages is marked as having a CLS issue, real visitors are experiencing it.
- PageSpeed Insights. Enter the page address. The top section shows real-user data from the previous 28 days where Google has enough of it, and the lower section is a lab test of the initial load. The lab diagnostics list the elements that shifted, which is usually enough to name the culprit.
- Your own phone, done properly. Open the page in a private window, on mobile data rather than Wi-Fi, and record the screen while it loads. Play it back slowly. Whatever jumps is your answer, and this catches things a lab test misses, like a banner that only appears for first-time visitors.
One caution applies to all three. Lab tests and real-user data often disagree on CLS, because the lab only watches the load and never scrolls or taps. If your lab score looks fine but Search Console says otherwise, believe Search Console. It is counting your customers.
How to Fix Layout Shift in Five Steps
The process is the same whichever culprit you find:
- Verify the culprit. Use the diagnostics and your phone recording to name the exact element that moves before you change anything.
- Clone to staging. Make the change on a staging copy first, so a broken layout never reaches a customer.
- Reserve, move or overlay. Give the late item a fixed space, move it lower on the page, or turn a top banner into a bottom bar.
- Verify on a real phone. Repeat the private window, mobile data recording and confirm nothing jumps.
- Deploy and watch the field data. Push to production, then use the validation option in Search Console's report and expect it to take around four weeks, because the real-user data covers a rolling 28 days.
That last step catches people out. The report will not turn green the morning after a fix, and nothing is wrong when it does not.
What Hosting Can and Cannot Do About Layout Shift
This is where I part company with a lot of hosting marketing.
Fast hosting does not fix layout shift. A server can deliver your page in a fraction of a second and the page can still lurch, because the shift comes from what the page does after it arrives: the widget that turns up late, the image with no size, the banner at the top. Anyone selling you a hosting upgrade as the cure for a poor CLS score is selling you the wrong thing, and I say that as someone who sells hosting.
Speed does help at the edges. When your HTML, images and fonts all arrive quickly, there is less time between the first paint and the last late arrival, so fewer items land after the visitor has started reading. That narrows the gap without closing it. A widget from someone else's server arrives when that server decides.
So the honest criteria for a platform, as far as layout shift goes, look like this:
- A fast base, so your own content lands early and the window for late arrivals stays short.
- A clean starting build, rather than an old theme with years of widgets bolted on.
- Full access, so you can move a widget or a banner yourself the day you spot the problem.
- A safe place to test, and a way to roll back if a layout change goes wrong.

Where Web60 fits
Web60 meets those criteria in a fairly unglamorous way. Sites run on Nginx with PHP-FPM, Redis object caching and FastCGI page caching, on Irish infrastructure built for fast page loads and strong Core Web Vitals scores, so your own pages and images reach the phone quickly. The AI website builder produces a full WordPress site from your own description of the business in under a minute, which means you start from a clean build instead of inheriting someone else's clutter. One-click staging is there for testing a layout change, and automatic nightly backups with one-click restore give you a rollback if a change misbehaves.
The built-in analytics are privacy-first, with no cookie consent required for analytics tracking. That removes one common reason for a banner at the top of the page, although other tools on your site, such as advertising pixels or embedded videos, may still need consent of their own. Because it is full WordPress, every fix in this guide is one you can make yourself, rather than paying an agency €75 to €150 an hour to move a review widget twelve centimetres down a page. All of it sits inside the same €60 a year.
When a different setup genuinely suits better
If your site is funded by display advertising from several ad networks, with ad slots of unpredictable sizes and a CLS score that moves your revenue directly, you are in territory where enterprise managed hosts that bundle front-end performance engineering, or a specialist consultant, genuinely earn their fee. Ad-funded publishers live and die by this metric. That is not a café, a garage or a kayak hire business, and it is not most of the owners I talk to.
What to Do This Week
Layout shift is one of the rare website problems you can diagnose with nothing more than the phone in your pocket. Open your homepage on mobile data, record the screen, and watch it back slowly. Then do the same for the page that matters most to your takings, whether that is bookings, the shop or the contact page.
If something jumps, you now know the five places to look and the three ways to fix it: reserve the space, move it down, or overlay it. Most fixes take an afternoon on a staging copy. The payoff is a page that stays still long enough for your customer to tap the thing they came for.
Frequently Asked Questions
Why does my website jump around when it loads on my phone?
Something on the page is arriving after the rest has already appeared, and it pushes the content around it out of the way. On small business WordPress sites the usual causes are images without a set width and height, widgets loaded from other services such as reviews, maps, booking calendars or social feeds, banners and cookie notices that slide in at the top, web fonts that swap in late, and sliders or animations that change the layout. Phones on mobile data show it far more than a desktop on fast broadband, which is why owners often never see it.
What is a good CLS score?
Google treats a Cumulative Layout Shift score of 0.1 or less as good and anything above 0.25 as poor. It is judged at the 75th percentile of real visits, separately for mobile and desktop, so roughly three out of every four visits to a page need to be stable for the page to count as good. Shifts that happen within half a second of a tap, click or keypress are not counted, because the visitor expected them.
Does layout shift affect my Google ranking?
A little. Google says Core Web Vitals, which include layout shift, are used by its ranking systems, but it also says good scores do not guarantee top rankings and that it will still show the most relevant content even when page experience is poor. Treat a stable page as something that can help when you and a competitor are equally relevant, and as a direct fix for customers tapping the wrong thing, rather than as a ranking shortcut.
Will faster hosting fix layout shift?
Not on its own. Layout shift comes from how the page is built: images with no size, widgets that arrive late, banners that push content down. Fast hosting gets your own pages, images and fonts to the phone sooner, which narrows the window in which late items land, but a widget from another company's server still arrives when that server sends it. You fix layout shift by reserving space, moving late content lower down or overlaying banners, and good hosting makes the rest of the page quick.
Can a cookie banner cause layout shift?
Yes, and it is one of the most common causes. Google's guidance on cookie notices says top-of-screen notices are a very common source of layout shift, because they push the whole page down when they appear. Showing the notice as a bar fixed to the bottom of the screen, or as a small pop-up over the content, usually avoids the shift. Your consent obligations stay exactly the same wherever the banner sits.
Sources
Graeme Conkie founded SmartHost in 2020 and has spent years building hosting infrastructure for Irish businesses. He created Web60 after seeing the same problem repeatedly — Irish SMEs paying too much for hosting that underdelivers. He writes about WordPress infrastructure, server security, developer workflows, managed hosting strategy, and the real cost of hosting decisions for Irish business owners.
More by Graeme Conkie →Ready to get your business online?
Describe your business. AI builds your website in 60 seconds.
Build My Website Free →More from the blog
Changing Your Business Phone Number: Every Place the Old One Still Hides
Changing your business phone number? Find every copy of the old one on your website and Google listing, from call buttons to schema, before calls go missing.
Deleting Old Pages for SEO: The Clear-Out That Cost a Business Its Best Page
Deleting old pages for SEO feels like progress during a Google core update. Google calls it a last resort. How to decide which pages to keep, fix or redirect.
