Mobile website design best practices come down to a few habits: a correct viewport, generous tap targets, readable text and simple navigation. If your site feels fiddly on a phone, start there.
This guide supports the wider topic of mobile website development, so read that page for the bigger picture.
| Item | Value |
|---|---|
| Minimum recommended tap target (web.dev) | About 48 device independent pixels |
| Space between tap targets (web.dev) | About 8 pixels |
| Apple’s minimum tappable area (Uxcel lesson) | 44x44pt |
| Body text size on mobile | At least 16px |
| Contrast ratio for small text | At least 4.5:1 |
| Line length on mobile | 30-40 characters per line |
These figures come from web.dev’s tap target guide (last updated 2020-03-31) and a Uxcel mobile layout lesson (updated Mar 4, 2025). Guidance can change, so check the sources before you rely on the numbers.
Mobile website design best practices start with the viewport
Phones are where many of your visitors are. One 2026 DEV Community post states that in 2026, mobile accounts for over 60% of global web traffic. Treat that as one developer’s claim rather than a census.
Before any CSS, add the viewport tag. According to the same post, mobile browsers otherwise simulate a desktop screen and reduce zoom, which makes responsive CSS useless. The value it uses is width=device-width, initial-scale=1.
Leave zoom switched on. The post warns against user-scalable=no because it stops visually impaired users from zooming, and notes that Apple removed the effect of user-scalable=no in iOS 10.
Then write your CSS mobile-first. The post gives these reasons:
- Base CSS applies to mobile devices without overriding media queries.
- You build on your mobile styles instead of overriding them with desktop ones.
- Mobile browsers parse fewer conditional rules, which the post describes as slightly better performance.
Older codebases often mix both approaches. The post’s advice is to stay consistent within a component and not mix them in the same rules (source).
Size and space your tap targets
Fingers are blunter than cursors. The web.dev guide says a minimum recommended touch target is around 48 device independent pixels on a site with a properly set mobile viewport. An icon that is only 24px wide can reach 48px with extra padding, and the 48×48 area is around 9mm, about the size of a finger pad (web.dev).
Leave breathing room as well. The same guide suggests spacing targets about 8 pixels apart, horizontally and vertically, so that pressing one does not touch another. That page was last updated 2020-03-31, so compare it with current platform documentation before you finalise a design.
Platform guidance differs a little. The Uxcel lesson, updated Mar 4, 2025, gives three reference points:
- Apple’s iPhone Human Interface Guidelines suggest a minimum tappable area of 44x44pt for all controls.
- Google’s Material Design states that touch targets should be at least 48x48px.
- The lesson itself advises aiming for controls that measure 7-10mm.
Adapt to the input type, not the screen size. A coarse pointer indicates a touchscreen of any size or type, and web.dev recommends testing for it (any-pointer: coarse) so every touchscreen user gets the larger targets (web.dev).

Keep text readable on small screens
The Uxcel lesson says to set body text to at least 16px so it is legible at a typical viewing distance without zooming. For line length on mobile it suggests 30-40 characters per line (Uxcel).
Form fields have their own rule. Safari on iOS automatically zooms into a form field when the font size is below 16px, which can throw off your layout, so keep input text at 16px or more (DEV Community).
For headings, the CSS clamp() function lets one rule scale smoothly and avoids writing media queries for every heading. The same post lists support as Chrome 79+, Firefox 75+ and Safari 13.1+ (DEV Community).
Keep paragraphs left-aligned. The post calls justified text on mobile a bad idea in almost all cases, because narrow columns create uneven gaps between words.
Simplify layout, navigation and thumb reach
Clutter costs you on a small screen. The Uxcel lesson suggests one primary action per screen, and points to Airbnb as an example: its users’ goal is to book accommodation, so the main screen centres on a search field (Uxcel).
The lesson is about mobile interfaces broadly, but its navigation advice carries over to websites:
- Show the name of the current page so people can tell where they are.
- Break long tasks into steps, such as a checkout spread over multiple screens.
- Use common navigation patterns, for example a Back button that returns to the previous screen.
- Keep global navigation controls consistent across all screens.
Think about thumb reach too. The lesson recommends placing primary content at the centre of the screen, secondary actions along the top and bottom edges, and tertiary functions behind menus.
It also suggests at least 7mm for central touch targets and 12mm for corner targets (Uxcel). Corners are harder to reach, so make those controls bigger.
Finally, give content side padding. The DEV Community post gives 16px as the minimum lateral padding to keep content off the edge, and says 20px is more comfortable (source).
Contrast, forms and horizontal scroll
Phones are used on trains, in daylight and in poor light. The Uxcel lesson cites the Web Content Accessibility Guidelines, which recommend a contrast ratio of at least 4.5:1 for small text and 3:1 for large text, with 3:1 or higher for icons (Uxcel).
Accidental sideways scrolling is a common bug. The DEV Community post lists these typical causes:
- An element with a fixed width larger than the viewport.
- A forgotten white-space: nowrap rule.
- A translate that pushes an element off-screen.
- An image with no width constraint.
For wide tables, let the table wrapper scroll instead of breaking the whole layout. The post also warns that overflow-x: hidden on the body can interfere with sticky elements, so apply it to a specific wrapper if you need it (DEV Community).
How do you check your mobile design?
Test on real conditions, not just a narrowed desktop window. A short routine covers the basics:
- Inspect your links and buttons. In Chrome DevTools, the Computed pane shows what pixel size each part of the box resolves to, and Firefox has a Layout panel for the same job (web.dev).
- Tap through every form on an iPhone and watch for automatic zoom.
- Scroll each page sideways and look for anything that overflows.
- Check text and icon contrast against the ratios above.
Layout is only one part of a good mobile site. For speed on phones, see the guide to core web vitals mobile. For how search engines treat mobile pages, read about mobile seo.
Frequently asked questions
What is the minimum tap target size?
Show answer
web.dev recommends around 48 device independent pixels, with about 8 pixels between targets. Apple’s guidelines suggest 44x44pt and Material Design says at least 48x48px, as reported by Uxcel.
Should I disable pinch zoom on my mobile site?
Show answer
No. The DEV Community post says user-scalable=no prevents visually impaired users from zooming, and that Apple removed its effect in iOS 10.
What font size should body text be on mobile?
Show answer
At least 16px, according to the Uxcel lesson. Keep form inputs at 16px or more too, because Safari on iOS zooms into fields with smaller text.
Is mobile-first better than desktop-first?
Show answer
The DEV Community post says mobile-first wins, since base CSS applies to mobile without overriding media queries. Whatever you choose, stay consistent within each component.



