
Mobile-friendly website: requirements, target size and checklist
7 min read below · WebYes knowledge base
Last updated:
What a mobile-friendly website needs: viewport, readable text, tap targets of 24 or 44 pixels under WCAG 2.2 and how WebYes measures mobile.
A mobile-friendly website works on every screen without zooming or horizontal scrolling, with readable text and tap targets that are large enough. WCAG 2.2 asks for at least 24 by 24 CSS pixels at level AA and 44 by 44 at AAA. Google indexes sites based on the mobile version.
What makes a website mobile-friendly?
The foundation is responsive design: one URL and one codebase that adapts the layout to the screen width. Columns stack, menus collapse, images scale. Technically it starts with the viewport meta tag. Without it, the phone shows a zoomed-out desktop site where text is unreadably small and buttons become unreachable.
On top of that come the details that separate workable from pleasant. Text large enough to read without zooming. Buttons and links with enough space around them. Forms that open the right keyboard per field, for example digits for a phone number. No content wider than the screen, so you do not have to scroll horizontally.
Mobile-friendliness is no longer a separate 'mobile site'. A separate mobile site, such as m.example.com, means double maintenance and the chance that phone content drifts from desktop. One responsive site on one URL prevents that.
Google judges your site on mobile
Google uses mobile-first indexing: the crawler primarily views and indexes the mobile version of your pages. According to Google only the content shown on the mobile site is used for indexing. A site that looks complete on desktop but stripped-down on mobile is therefore judged on the stripped-down version.
On mobile, connections are often less stable and devices have less processing power. The Core Web Vitals are measured on real visitors. Mobile-friendliness and load speed are two sides of the same job; how to test speed on a phone is covered in testing website speed.
In practice this means: publish the same core content, metadata and links on mobile as on desktop. Do not hide important text behind tabs that only collapse on phones without accessible controls. Test whether your product pages, checkout and contact form work on a real device, not only in your browser's desktop emulator.
Where it goes wrong in practice
Common problems are rarely spectacular, but they are disruptive. Tap targets placed too close together, so you hit the wrong one: a navigation link above a button, two icons touching. Font sizes that are too small to read on a small screen. Tables or wide images that make the page overflow. Pop-ups that occupy a corner on desktop but block the entire screen on mobile without a reachable close button.
For touch targets WCAG 2.2 gives two sizes. Level AA asks for at least 24 by 24 CSS pixels, or enough space around smaller targets (criterion 2.5.8). The stricter level AAA asks for 44 by 44 CSS pixels (criterion 2.5.5). If you want buttons that are comfortable to tap on a phone, aim for those 44 pixels and keep free space between adjacent targets. More on the new criteria in WCAG 2.2 and target size. This is where mobile and digital accessibility meet: what is hard to hit with a thumb is even harder with a tremor or limited vision.
Other classics: sticky headers that consume too much vertical space, cookie banners that cover the CTA, and carousels that only work with a swipe and no buttons. Each of those patterns can hit the mobile pillar and criteria from WCAG. Teams that design for desktop first and then "make it responsive" risk baking these mistakes in.
Mobile and accessibility: the same visitor
On a phone everyone depends equally on clear focus, sufficient contrast and operable buttons. Zoom, voice control and screen readers work better when the HTML is semantic and buttons are real buttons, not clickable divs. The European Accessibility Act (see also the Dutch government overview) enforces for many e-commerce services what good mobile UX already required: nobody should drop out because a checkout only works with a mouse or only on a large screen.
For shops and booking flows that is not abstract compliance. If your order button is too small, your form labels are missing or your error messages are unclear, you can lose conversion with every visitor, not only people with impairments. Mobile-friendliness is therefore also an accessibility investment: you remove measurable barriers that the scan can flag in both pillars.
How to test it, and what WebYes measures
The quickest first check is your own phone, not only the developer view. Open the site on a real device, preferably an older model with a smaller screen, and try the three most important tasks: finding something through the menu, filling in a form, reading a page. Wherever you zoom, misclick or wait, so does your visitor.
For a systematic check, WebYes scans measurable points within the mobile pillar: viewport configuration, readable font sizes, tap targets and content overflowing the screen. The scan covers up to six pages per run; findings are listed per page in the report. Automated WCAG 2.2 AA checks sit under the accessibility pillar, but often overlap with mobile (contrast, labels, target size).
The WebYes quality mark requires an average score of at least 80 and at least 60 per pillar. A strong desktop site with a weak mobile score therefore does not pass. Fix the blockers that hit visitors first, re-scan, then plan the finer improvements. That way you know whether your site is truly mobile-friendly, instead of only looking responsive in a mockup.
Checklist for a real-device test
Open the site on a phone you do not use daily for development. Walk through three tasks: navigation via the menu, a form or checkout step, and reading a long page. Note where you zoom, scroll horizontally or accidentally hit the wrong control. Those notes are often more valuable than an abstract responsive preview.
Check sticky headers and cookie banners: together they should not take up too much of the viewport on a small screen. Test whether buttons stay reachable when the soft keyboard is open. If the primary CTA then disappears behind the bar, the flow fails in practice even if the CSS is called 'responsive'.
Then compare with the WebYes report. Findings about tap targets, font size and overflow should match what you felt on the device. If lab differs from your experience, note the exact URL and re-scan after a fix; the full audit covers up to fifteen pages so deeper templates can be included.
Sources
Frequently asked questions
Is a separate mobile site (m.mysite.com) still a good idea?
No. A separate mobile site means double maintenance and the risk of the two versions drifting apart, while Google uses the mobile version for indexing and ranking. Responsive design on a single URL prevents that.
How large should buttons be on mobile?
Keep at least 24 by 24 CSS pixels (WCAG 2.2, level AA). For comfortable tapping, 44 by 44 (the AAA level) is a good target. More important than the exact size is that adjacent targets do not touch, so a thumb does not accidentally hit the wrong element.
Does mobile-friendliness count in the WebYes score?
Yes. Mobile is one of the four pillars, alongside speed, security and accessibility. The quality mark requires an average of at least 80 and at least 60 per pillar. The free scan checks viewport, font sizes, tap targets and horizontal overflow on up to six pages; the full audit up to fifteen.
Does a mobile-friendly site replace WCAG compliance?
No. Mobile-friendliness and WCAG overlap (for example on button size and readability), but accessibility also covers keyboard use, screen readers, contrast and form logic. Both pillars must be in order separately for the quality mark.
The WebYes scan measures this too
Scan your website for free on speed, security, mobile and accessibility and see where you stand.
Start free scan


