Skip to content
Back to the blog

Business websites

Why your website should be designed for phones first

Updated

Why your website should be designed for phones first

Many websites are designed on a large screen, approved on a large screen and then squeezed to fit a phone. Nothing is missing from the result, but the phone version is the awkward one. Designing for phones first reverses the order: get the small screen right, then use the extra room on larger ones.

Why the phone version counts

There are two reasons that do not depend on guessing how your customers browse. The first is search. Google states that it uses the mobile version of a site’s content for indexing and ranking, and recommends that the mobile site contains the same content as the desktop one. Content left out of the phone layout may not be found through search.

The second is the situation people are in. Someone looking for a plumber, a table or an opening time on a phone is often standing up, on mobile data, with one hand free. If the page is slow or the number is hard to tap, going back to the search results is easy.

Test your own site

Use your own phone and mobile data, and try to do what a customer would:

  • Find what you do and where you work without zooming or scrolling sideways.
  • Open the menu and reach a service page with your thumb.
  • Tap the phone number. It should offer to call.
  • Fill in the contact form. Check that the right keyboard appears for email and phone fields, and that an error message tells you what to fix.
  • Read a full page of text outdoors to check its size and contrast.

Then ask someone who does not know the business to do the same, and watch where they hesitate. Our guide to checking your website’s speed covers the loading side.

What phones first changes in the design

A small screen forces decisions that a large one lets you put off. There is room for one main message and one main action, so you have to choose them. Navigation has to be short. Buttons and links need to be large enough to tap: the accessibility standard WCAG 2.2 sets a minimum target size of 24 by 24 CSS pixels, with some exceptions, and primary buttons are usually larger.

Forms get shorter, because every field is typed with a thumb. Tables and comparison grids need a different arrangement, since a five-column table does not fit. These choices tend to improve the desktop version too, because the priorities have already been settled.

What to ask for in a proposal

  • Will designs be shown at phone width first, or only as desktop layouts?
  • Which phone sizes and browsers will the finished site be checked on?
  • Does the phone version have the same content as the desktop one?
  • How will forms, menus and any booking or checkout steps be tested with touch and with a keyboard?
  • Who checks the phone layout when you add new pages after launch?

Digital Marvels checks layouts on smaller screens, with readable text, keyboard controls and clear form feedback, as part of a business website. To have a phone-first design set out in a written scope, request a quote.

MobileWebsite planningAccessibility

Want a price for your project?

Every project is quoted individually. Tell us what you need and you’ll get a written quote.

Request a quote