A responsive website is one that actually adjusts to the screen it's being viewed on, rather than a desktop site that gets awkwardly squeezed onto a phone. Mobile friendly is a slightly bigger idea sitting next to it, it's not just about the layout resizing, it's about whether the site was actually designed with a phone in mind from the start, tap targets, form keyboards, page weight, and everything else that only shows up once you're actually holding a phone rather than looking at a resized browser window. In practice the two go hand in hand, and we build for both together, not one after the other.
Why this still needs saying
Most visitors to a typical business website are on mobile, often browsing on a train, between meetings, or from a phone with a cracked screen and patchy signal, not sitting at a desk with a mouse. If the site fights them at every tap, a menu button that's impossible to hit, a form field that triggers the wrong keyboard, they leave and call the next business on the list instead. We've had clients come to us convinced their website just wasn't generating enquiries, when the real issue was that the contact form simply didn't work properly on the phone their customers were actually using.
We design for the smallest screen first, then build up to tablet and desktop, rather than designing for a large monitor and hoping the mobile version holds together afterward. That single decision changes how the whole layout gets structured, what gets prioritised at the top of the page, and what gets tucked away behind a tap.
What we actually check before calling a site responsive and mobile friendly
- Buttons and links are large enough to tap accurately without needing to zoom in first
- Forms trigger the right keyboard automatically, a numeric keypad for phone numbers, an email keyboard for email fields
- Images resize and compress properly instead of loading a full desktop sized file on a phone and slowing everything down
- Navigation collapses into something usable and thumb friendly, not a tiny unreadable menu bar or a dropdown built only for a mouse hover
- Page weight stays low, since mobile data connections are often slower than the office wifi a site typically gets tested on
- Text stays readable without the visitor needing to pinch and zoom on every paragraph
Where this usually breaks down
In our experience, these failures aren't dramatic, they're small annoyances that add up quickly. A table that was fine on desktop turning into an unreadable horizontal scroll on mobile. A sticky header that eats up half the screen on a smaller phone. A popup or cookie banner that's genuinely difficult to close because the close button is one pixel too small to tap reliably. A dropdown menu that worked fine with a mouse hover and becomes nearly unusable on a touchscreen where there's no hover state at all. None of these show up in a quick glance at a desktop preview, which is exactly why they get missed so often, and exactly why we test on real devices rather than just a resized browser window.
Our process
We build and test on actual phones, not simulators, because a browser simulation and a real device in someone's hand behave differently in ways that matter, load times over real mobile data, tap accuracy, how a sticky header behaves when you scroll fast with your thumb. Once a design is approved, we check it across a handful of common screen sizes before it goes anywhere near launch, and we come back to it periodically afterward, since a site that was responsive and mobile friendly at launch can quietly stop being so once new content or features get bolted on later.
What breaks without this, and how we fix it
| Problem | What visitors experience | What we fix |
|---|---|---|
| Small tap targets | Buttons and links get missed or mistapped | Sized and spaced properly for thumbs |
| Fixed width layout | Horizontal scrolling on phones | A fluid layout that adapts to screen width |
| Wrong keyboard on forms | Typing a phone number on a full text keyboard | Correct input types set for each field |
| Menu built only for mouse hover | Navigation unusable on touch | Touch first navigation design |
| Oversized images and assets | Slow loading on mobile data | Compressed and resized per device |
Why this matters for how you get found, not just how you look
Since search engines largely judge your site based on how it performs on mobile now, not the desktop version, none of this is really optional anymore for most businesses. A site that looks great on a laptop but frustrates mobile visitors is quietly costing you both rankings and actual customers, often without anyone on your team realising why enquiries have slowed down.
If you already have a site and just want a second opinion on whether it's genuinely responsive and mobile friendly, or only looks fine on your own phone, we're happy to take a quick look and tell you honestly, even if the answer is that it's mostly fine and doesn't need much. Want the fuller picture on what goes into a build like this? Our website development services page covers the whole process, and if speed is your bigger concern right now, our performance focused development page is worth a look too.
