There's a particular kind of irony that plays out in web design studios across Britain every single day. A designer opens their 27-inch iMac, pulls up a client's new website, and grins. It looks immaculate. The typography breathes, the animations are silky smooth, the hero image fills the screen like a cinema poster. Everyone in the room nods approvingly.
Then it goes live — and the customers who actually matter are squinting at it on a Samsung Galaxy A34.
This is the device disconnect. And it's one of the most expensive, least-discussed problems in UK digital right now.
What the Data Actually Says
Let's start with the numbers, because they're more sobering than most agencies want to admit. Mobile traffic across UK websites consistently accounts for more than 60% of all sessions — and that figure climbs significantly for retail, hospitality, and local services. But here's the part that gets glossed over: the devices driving that traffic aren't iPhones 15s or Samsung Galaxy S24 Ultras.
Statcounter data consistently shows that mid-range Android handsets dominate British browsing habits. Devices with screens between 360px and 390px wide, older processors, limited RAM, and browsers that haven't been updated since the owner bought the phone two Christmases ago. These are real devices. These are your customers.
And yet, when agencies build and test websites, the go-to preview is Chrome DevTools set to iPhone 14 Pro — a device that represents a fairly affluent, Apple-loyal slice of the population. It looks great in the emulator. It may well fall apart on the actual device sitting in a Coventry living room.
The Portfolio Problem
Part of this is structural. Agencies, understandably, want their work to look impressive in award submissions and on their own showcase pages. Stunning full-screen imagery, complex parallax scrolling, and heavyweight animations photograph beautifully on a high-resolution display. They're considerably less impressive when they're causing a three-second render delay on a Motorola Moto G.
This creates a quiet conflict of interest that rarely gets discussed openly in client meetings. The website that wins a Webby Award and the website that converts a plumber's leads in Preston are not always the same website. When creative ambition outpaces device reality, the business pays the price — not the agency.
It's not that agencies are deliberately building inaccessible sites. Most genuinely believe their work is responsive. The problem is that "responsive" has become a checkbox rather than a philosophy. A site can technically reflow at mobile breakpoints and still perform terribly on the devices most people are actually using.
The Resolution Illusion
One of the most common traps is designing for screen resolutions that sound sensible in a brief but don't reflect reality. "Mobile-first design" has become a mantra, but many teams interpret it as designing for a 375px-wide iPhone viewport — which is a reasonable starting point, but misses a substantial chunk of Android users browsing at 360px or even narrower.
Beyond width, there's the question of pixel density, font rendering, and touch target sizing. What appears as a generous 16px button on a Retina display can shrink to something fingernail-unfriendly on a lower-density Android screen. Navigation menus that feel elegant on iOS can become a tapping nightmare on a device where touch response is slightly less precise.
And then there's performance. Google's Core Web Vitals have made page speed a ranking factor, but the conversation still tends to focus on scores rather than real-world experience. A score of 78 on PageSpeed Insights might still mean a four-second load time on a 4G connection in rural Yorkshire. That's a bounce waiting to happen.
What Designing for Reality Actually Looks Like
The good news is that designing for the actual device landscape isn't about dumbing things down. It's about being smarter with every decision.
Start with your own analytics. If you have an existing website, pull the device and browser data before writing a single word of a new brief. Segment by device category, operating system, and screen resolution. You might be surprised — or alarmed — by what you find. If you're launching fresh without historical data, look at industry benchmarks for your sector. A fashion retailer and a B2B software firm will see very different device splits.
Test on physical devices, not just emulators. There's no substitute for actually picking up a three-year-old Android handset and navigating your own website. Many agencies maintain a small device library for exactly this reason. If yours doesn't, it probably should.
Rethink your performance budget. Every design element — every font file, every image, every animation — has a cost. On a powerful machine with a fast connection, those costs are invisible. On a mid-range device with inconsistent mobile data, they accumulate fast. Establish a performance budget early in the project and treat it as a creative constraint rather than a limitation.
Prioritise touch usability over visual elegance. Buttons need to be large enough to tap confidently. Spacing between interactive elements needs to account for fingers, not cursors. Forms need to trigger the correct keyboard type. These aren't glamorous considerations, but they're the difference between a conversion and an abandoned session.
The Bigger Picture
There's a cultural shift required here, and it starts with how businesses and agencies talk about success. If the measure of a great website is how it looks on the designer's monitor at the project review, the incentive structure is wrong from the start.
The measure of a great website is whether it works — genuinely, reliably, smoothly — for the actual people using it. In Britain in 2024, a significant proportion of those people are on affordable Android devices, browsing during a commute or a lunch break, with one eye on the screen and limited patience for slow loads or clunky interfaces.
Building for them isn't a compromise. It's the whole point.
