ZPages All articles
Conversion

Seven Things Can't All Be Important: Rationing the Floating Layer on UK Service Sites

ZPages
Seven Things Can't All Be Important: Rationing the Floating Layer on UK Service Sites

Every floating element on your website was added by somebody with a good reason. That's the trouble. The promo bar was a marketing push. The sticky header was a navigation fix. The cookie notice was compliance, the chat bubble was a customer service initiative, the WhatsApp button came from the sales team, and the sticky "Book now" bar was the result of a very sensible conversation about mobile conversions. Six good reasons, one small screen, and a mess nobody actually approved.

On a mid-range Android phone held in one hand, the visible viewport is roughly 360 by 800 CSS pixels. Stack a promo bar, a header and a consent notice and you can cheerfully hand over a third of that before a visitor has read a single word about what you do. The politics of who gets to sit on top isn't a technical question. It's an editorial one, and it's usually settled by whoever asked most recently.

The archaeology of the floating layer

It's worth doing the audit properly before you touch anything. Open your own site on a phone and screenshot the first three seconds, then scroll a bit and screenshot again. Count the fixed elements. Most UK service firms land somewhere between five and eight, and the reaction is nearly always the same: who signed off on all this?

Nobody did. That's the point. Each layer was approved in isolation, on its own merits, by someone imagining the site with only that one addition. Nobody was ever shown the seventh version.

What actually earns altitude

There are only four categories of thing that deserve to leave the document flow, and the list is shorter than most people expect.

One navigation element. A sticky header or a sticky menu bar — pick one, not both. If your header is thin and honest, it can stay. If it's carrying a logo, a phone number, a search box and a five-item menu, it needs to shrink or it needs to go.

One consent notice. Legally necessary, and it should stop appearing the moment someone makes a choice. If it follows people to page two, it's not a consent notice any more, it's harassment.

One conversion action. Call, book, or enquire — whichever your actual enquiry data says wins on mobile. Not all three. Pick the one that pays and let the others live inline where the content supports them.

One transient, user-triggered thing. A modal that opens because someone clicked "view our accreditations", or a confirmation toast. These don't occupy space until asked, which is exactly what makes them acceptable.

Everything else — the promo bar, the newsletter nudge, the exit-intent pop-up, the back-to-top arrow nobody has ever pressed — is a candidate for the bin or for a quiet, non-floating home lower down the page.

Set a cap and write it down

Three floating layers at once. That's the ceiling. Two is better. One legal, one converting, one navigational, and if you need a fourth you're trading content for furniture.

Writing the number down matters more than the number itself. A documented cap turns every future request into a conversation about trade-offs rather than a fresh exception. "We can add it, but the chat bubble comes off — which one do you want?" is a very different sentence from "sure, I'll stick it in".

It also gives you something defensible when an agency, a new marketing hire or a keen sales director arrives with a widget and a deadline.

Ten minutes on a phone that isn't yours

Testing this on a desktop browser resized to 360px tells you almost nothing. Desktop Chrome on a fast connection with a trackpad is not the experience your customers are having on a three-year-old Moto G in a car park in Leeds.

Do this instead:

While you're there, check tap targets. Anything under about 44 pixels is a nuisance, and a row of three tiny floating icons down the right edge is a nuisance three times over.

Winning the conversation without a fight

When someone asks for a new floating element, don't argue about screen real estate — argue about the question it answers. What is it for? If the honest answer is "to make sure people see the offer", ask which page the offer applies to. Nine times out of ten it's one page, and a banner can live at the top of that page as normal content, scrolling away like everything else.

If the answer is "to capture leads", ask what happens to those leads after they're captured — because a chat bubble that goes unanswered until Monday lunchtime is doing more damage than its absence would.

Keep the intent. Cut the count. The person who asked for the WhatsApp button was trying to help a customer get through, and that instinct is worth protecting. It just doesn't need to live on top of five other things that were also trying to help.

All Articles

Related Articles

The Accent Your Website Didn't Mean to Have

The Accent Your Website Didn't Mean to Have

Your Homepage Is Not a Slideshow: Deciding What Deserves Permanent Space

Your Homepage Is Not a Slideshow: Deciding What Deserves Permanent Space

The Form Is Not a Questionnaire: Cutting Enquiry Fields That Cost You Jobs

The Form Is Not a Questionnaire: Cutting Enquiry Fields That Cost You Jobs