A Maldon estate agency proudly told us their site had "passed Google's mobile test" and couldn't understand why enquiries from phones still lagged well behind desktop. Passing the test and actually working well on a phone, it turns out, are two genuinely different things, and conflating them is one of the most common mistakes we see.
What the mobile-friendly test is actually checking
Google's mobile-friendly test, and the broader mobile usability checks that feed into Search Console, look at a fairly narrow, specific set of technical criteria: is text readable without a visitor needing to zoom in, are clickable elements spaced far enough apart that a thumb won't accidentally tap the wrong one, does content fit the screen width without horizontal scrolling, and is the viewport configured correctly in the page's code so the browser knows how to scale everything properly in the first place.
That's genuinely useful information, and worth checking regularly. It is not, however, a judgement on whether your site is actually pleasant, fast, or effective to use on a phone. A site can tick every one of those specific boxes and still be a genuinely frustrating experience for a real human holding a real phone with one hand on a train.
Think of the test as a basic MOT, not a full service history. It confirms the car starts, the lights work, the tyres aren't bald. It says nothing about whether the clutch bites smoothly or the seats are comfortable on a long motorway drive. Both matter enormously to the person actually driving the thing. Only one of them gets formally checked, certified, and handed back to you with a pass sticker.
The Maldon agency's actual problem
Their site passed the formal test cleanly, text readable, buttons spaced sensibly, viewport configured correctly, every box ticked. What the test doesn't check is whether your property search filter requires nine separate taps to narrow down a search, or whether a map widget takes up the entire screen and pushes the actual listing information two full scrolls further down than it needs to be.
We watched someone unfamiliar with the site attempt to find a two-bedroom property under £300,000 in Maldon itself. It took them over ninety seconds and eleven taps, genuinely counted, to narrow the search down to something usable, by which point plenty of real visitors would have simply given up and gone to a competitor's site instead, one with a faster, simpler filter.
The agency's own staff never noticed, because none of them used the search filter the way a genuine stranger would. They knew the shortcuts, the exact dropdown order, which boxes to skip. That's a common blind spot. The people best placed to notice a clumsy mobile experience are almost always the least likely to ever encounter it, because they've long since learned to work around it without thinking.
Technical pass, practical fail: a common gap
We see this gap constantly. A site is technically mobile-friendly by every measure Google's test checks for, and genuinely unpleasant to actually use on a phone in practice. Forms with tiny input boxes that are technically tappable but genuinely fiddly. Navigation menus that open correctly but bury the one page a visitor actually came looking for three sub-menus deep. Pop-ups that are dismissible, technically, but cover the entire screen and require hunting for a tiny close button hidden in a corner.
None of this fails Google's formal mobile-friendly test. All of it fails the much more important test: does a real customer, in a hurry, on a real phone, actually manage to do what they came to do without giving up partway through out of frustration. A quick phone audit, something we build into every technical SEO engagement we run, catches most of this within the first hour of looking properly.
We've started asking new clients a simple question before we even open a laptop: when did you last use your own website on your phone, start to finish, as if you were a genuinely new customer walking in off the street? More often than not, the honest answer is "ages ago," which tells us a great deal before we've even run a single formal test or opened a single report on anything at all.
Things worth checking that the automated test won't catch
- Can you complete your own contact or booking form on a phone without any noticeable friction, start to finish?
- Do images and galleries load quickly, or does scrolling feel genuinely jerky and sluggish on a mid-range phone?
- Is your most important call to action visible without scrolling, on a typical phone screen, without having to search for it?
- Does anything important get hidden behind a "read more" tap that a visitor in a hurry simply won't bother clicking?
Why Core Web Vitals matter more than the pass/fail badge
Beyond the binary mobile-friendly check, Google also measures Core Web Vitals: how quickly the main content loads, how stable the layout is as elements shift into place while the page finishes rendering, and how quickly the page responds when someone actually taps something on it. A site can be formally "mobile-friendly" and still score poorly here, because these measure real-world performance and experience, not just structural compliance against a checklist.
A Billericay dental practice's booking page was mobile-friendly by every formal measure, yet had a layout shift problem that moved the booking button noticeably downward a full second after the page appeared to finish loading, because a late-loading image above it pushed everything else down the page unexpectedly. Visitors who tapped where the button had briefly appeared ended up tapping something else entirely, often the wrong thing, by accident. It took a developer barely twenty minutes to reserve the right amount of space for that image before it loaded, and the layout shift problem disappeared completely.
The practice manager had no idea this was happening until we showed her a screen recording of it in slow motion, the button visibly jumping down the page mid-load. Her reaction summed up why this kind of thing survives undetected for so long: "I've looked at that page a hundred times and never once seen it move." She hadn't, because her connection was fast enough, and her eyes already knew roughly where the button would land before it did, which is precisely the problem with judging your own site's usability from inside your own office on your own equipment.
What we actually test, beyond the automated checkers
We run the formal test, obviously, it's quick and free and worth doing regularly as a baseline. But we also sit down with an actual phone and attempt to complete the core task the site exists to achieve: book an appointment, request a quote, find opening hours, whatever that specific business's version of a conversion actually is. If it's clumsy for us, someone who already knows exactly where everything is because we built or audited the site ourselves, it's going to be considerably worse for a first-time visitor who's never seen the layout before in their life.
This hands-on testing forms part of every technical review we carry out for Essex businesses, because the automated test is a genuinely useful starting point, not a finish line, and treating it as the final word leaves real, costly problems sitting there completely unaddressed, invisible to any dashboard.
The Bottom Line
Passing Google's mobile-friendly test tells you your site meets a baseline technical standard. It tells you nothing about whether a real customer can actually accomplish what they came to do on their phone without giving up halfway through. Test the formal criteria, yes, but then hand your own site to a real phone and try to use it the way a genuinely impatient stranger would. That's where the problems costing you actual customers tend to be hiding.
Looking for SEO agency in Essex?
Let's talk about what your business actually needs
Digital Impact Ventures provides SEO, AI visibility and digital marketing support for businesses across Colchester and Essex. Get in touch and we will talk through where your business is now and where it needs to go.