Mobile Usability Problems a Responsive Layout Doesn't Solve
A responsive layout makes a page fit the width of a phone. It does not make the page easy to use with a thumb, on a small screen, on a patchy connection, with an on-screen keyboard covering half the view. The problems that cost mobile customers often survive a responsive redesign: buttons and links too small to tap accurately, navigation hidden behind an icon nobody notices, pop-ups that cover the content, forms that bring up the wrong keyboard, and content quietly dropped from the mobile version. Each of them has to be designed and tested for on purpose.
Fitting the screen is not the same as working on it
Responsive design rearranges columns, scales images and changes font sizes at certain screen widths. Google recommends it as the easiest pattern to implement and maintain, and it is the right foundation. But a layout system answers the question "where does this go on a narrow screen?". It does not answer "can someone complete this task one-handed on the bus?". That takes decisions about size, priority, input and content.
1. Tap targets that are too small or too close
A mouse pointer is a point; a fingertip is not. web.dev recommends interactive elements of at least about 48×48 device-independent pixels – roughly 9 mm, about the size of a fingertip – with about 8 pixels of space between them. The Web Content Accessibility Guidelines set a lower floor: success criterion 2.5.8 in WCAG 2.2 (Level AA) requires targets of at least 24×24 CSS pixels, with exceptions such as links inside a sentence or small targets with enough empty space around them.
Typical offenders: icon-only buttons in the header, social media icons packed together, "×" buttons for closing banners, pagination numbers, footer links stacked with no spacing, and checkboxes in forms. Padding can turn a small icon into a large target without making it look any bigger.
2. Navigation nobody finds
On phones, the menu is often hidden behind an icon. Nielsen Norman Group's research shows that hidden navigation is less discoverable. In a mobile study they published in 2016, a site that combined visible links with a hidden menu had its navigation used in 89% of cases, compared with 44% on a site that hid its navigation behind a visually weak menu icon. Their recommendations:
- if you have only four or five top-level sections, show them instead of hiding them;
- otherwise show the most important ones and put the rest in the menu;
- if you must hide everything, make the menu icon stand out from the logo, look clearly tappable, and label it "Menu".
For a service business, the most important links on mobile are usually the main services, the phone number and the contact page. They should be visible without opening anything.
3. Pop-ups and banners covering the content
On a large screen a pop-up covers part of the page; on a phone it covers all of it. Google's guidance on interstitials and dialogs describes intrusive ones as elements that obstruct the user's view of the content, usually for promotional purposes, and recommends banners that take up only a small fraction of the screen instead. Google also warns that intrusive dialogs can make it hard for search engines to understand your content, which may lead to poor search performance.
In practice: no newsletter pop-up on the first page view; a cookie consent banner that is compact and easy to close on a small screen; chat bubbles that don't sit on top of the "Call" or "Send" button; and sticky headers that don't take up a quarter of the screen.
4. Forms that fight the phone keyboard
Forms are harder on a phone: people type on glass, with a keyboard covering half the screen. web.dev's guidance on forms covers the details that responsive CSS never touches:
- Use the right input type.
type="email"andtype="tel"bring up the matching keyboard and basic browser validation. - For numbers that aren't quantities – postcodes, card or ID numbers – web.dev recommends
type="text"withinputmode="numeric"rather thantype="number". - Add autocomplete attributes for name, email, phone and address fields, so the browser can fill in saved details.
- Give every field a visible label. Placeholder text inside the field disappears as soon as people start typing.
- Ask for the name in one field, unless you have a real reason to split it.
- Keep the submit button visible on small screens, and disable it after the first tap to avoid double submissions.
Then test on real devices: web.dev stresses testing forms on the platforms your users actually use.
5. Content that disappears on mobile
To save space, mobile versions sometimes drop text, tables or whole sections. That hurts twice. Phone visitors lose information, and Google uses the mobile version of a site's content for indexing and ranking – so what isn't on mobile effectively isn't on the site. Google's mobile-first indexing guidance asks for the same content, the same clear headings, the same structured data and the same image alt text on mobile as on desktop. Accordions and tabs are fine for saving space; removing content isn't. Google also advises against lazy-loading primary content only when the user swipes, clicks or types, because Google won't perform those actions.
6. Things that only work with a mouse
- menus and tooltips that open on hover;
- wide tables that make the whole page scroll sideways instead of just the table;
- embedded maps that capture the scroll gesture and trap the visitor;
- phone numbers that aren't links, or are part of an image;
- important information available only in PDF downloads;
- zoom disabled in the page's viewport settings – people with low vision rely on pinch-to-zoom.
7. Real phones, real networks
The mobile version is often checked by narrowing a desktop browser window. That tests the layout and nothing else. A mid-range phone on mobile data shows how heavy the page really is and how long the main content takes to appear. Check speed using field data for mobile, not just desktop.
A 20-minute mobile test
- Use a real phone, ideally not the newest model, with Wi-Fi turned off.
- Open your most visited page from a Google search, the way a customer would.
- Without scrolling: is it clear what you do, and where to call or write?
- Use one hand only. Tap every button and link in the header, menu and footer.
- Find a specific service through the menu.
- Fill in and send the contact form, including one mistake, and see what happens.
- Tap the phone number. Does it start a call?
- Rotate the phone, and pinch-zoom into a paragraph.
- Close every banner and pop-up. Count how many there were.
Write down every moment of hesitation. Those are your fixes, and most of them are small.
If your site is responsive but mobile visitors still don't become customers, we can test it on real devices, list what gets in the way and fix it – or plan a mobile-first website if the problems run deeper. If you are also considering an app, read website or mobile app: where to start. Contact us.
Sources
- Accessible tap targets – web.dev (Google)
- Understanding Success Criterion 2.5.8: Target Size (Minimum) – W3C Web Accessibility Initiative
- How to Make Navigation (Even a Hamburger) Discoverable on Mobile – Nielsen Norman Group
- Interstitials and dialogs – Google Search Central
- Mobile site and mobile-first indexing best practices – Google Search Central
- Payment and address form best practices – web.dev (Google)