Mobile-first design plans a service page around what a visitor needs to do on a small phone screen, then adapts that content for larger screens. Put the service, proof and main action where visitors can find them, keep forms easy to complete, and test the full enquiry path on real devices.

Reviewed 6 November 2026. Google uses the mobile version of a page for indexing; this guide distinguishes that from layout choices and includes a phone-testing checklist.

For a service business, mobile-first design starts with the task a visitor came to complete: understand the service, check that it fits, then call, message or request a quote. Responsive design adapts a page to different screen sizes. Mobile-first describes the order in which you plan that experience.

Start with the phone task, then expand

web.dev recommends starting with a small screen and adding breakpoints, the screen widths where a layout changes, when the content needs a different arrangement. Google recommends responsive design because it uses the same page URL and content across devices and is easier to maintain.

Design approach What you do What to check
Desktop-first adaptation Start with the wide page and compress or rearrange it for phones. Check that the main task, content and controls still work at narrow widths.
Mobile-first responsive design Prioritise the phone task, then add space and layout changes for wider screens. Check that larger layouts use the extra space without hiding or changing important content.

Both approaches can create a responsive website. A mobile-first starting point gives you a clear constraint for prioritising content; it still needs testing on desktop and tablet screens.

On the first phone screen, show the service, the customer problem it addresses and the main action. Add a location or availability when it affects the decision. Avoid a full-screen animation that delays the explanation.

Make the main action easy to find and tap

Give the main action a clear label and enough space around it. Check its contrast, position and meaning after the visitor scrolls. A link labelled “WhatsApp us about website redesign” explains more than an unlabeled chat icon.

If you use a phone link, write the business or branch name beside the number. A tel: link tells a phone browser to open its calling app with that number. Check that the visible number and the linked number match.

Keep fixed controls from covering the page

A cookie notice, navigation bar, WhatsApp button and sticky contact bar can crowd a phone screen. Test them together, including when a visitor opens the keyboard or reaches the form submit button.

Use a fixed control only when it gives visitors a useful action. If a contact bar stays on screen as visitors scroll, include a close button. Account for the safe area around modern phone screens. Pass the check only when the close button and the page’s important controls remain visible and usable while scrolling and while the keyboard is open.

Keep text readable and information available

Use readable type, clear line spacing, short paragraphs and headings that explain what each section covers. Let visitors scroll instead of shrinking text to fit the part of the page visible before scrolling.

Google uses the mobile version of a page for indexing. Its guidance says the primary content and meaningful headings should remain equivalent on mobile and desktop. Reorder or collapse content when useful, but keep important service details, pricing and proof available.

Make forms fit the first enquiry

Ask only for information your team needs to respond. Use email and telephone input types, autocomplete where appropriate, visible labels and helpful error messages. Keep values after an error and show a clear sending state.

Show a success message after the server confirms the form submission. If the network or server fails, show an error that assistive technology can announce, keep the entered values on the page so the visitor can retry, and explain how to retry or use another contact route. Disable repeat submission while a request is in progress; if it fails, let the visitor try again without re-entering everything. Ask a developer to test the failure and retry on a staging form. Pass when the error is announced, the entered values remain available, and exactly one enquiry appears in the receiving inbox or system after the retry. Avoid two-column forms on narrow screens. Do not ask visitors to repeat information the page already knows, such as the service they are viewing.

Give WhatsApp visitors a clear handoff

Label the WhatsApp link clearly, test it on a phone and keep another contact route easy to find for visitors who cannot or prefer not to use WhatsApp. For prefilled messages and response expectations, see the WhatsApp-first enquiry guide.

Keep mobile navigation short and predictable

Put the main routes near the top of the menu: services, published pricing, work or case studies, and contact. Group less-used pages rather than placing every link at the first level.

Make the menu keyboard accessible: show a visible focus indicator, let visitors reach and use every menu item with the keyboard, close the menu with Escape, and return focus to the menu trigger after it closes. Keep its open and closed states clear so visitors can return to the page without guessing.

Check performance on a mobile connection

A page can feel fast on office fibre and load slowly on a weaker mobile connection. Check image sizes, video loading, font files, third-party scripts, animation libraries, chat widgets and render-blocking resources, such as scripts or stylesheets that delay the browser from displaying the page.

Use responsive image sizes and lazy-load below-the-fold images where appropriate. Avoid automatically loading a large hero video when it delays the service information or uses data before the visitor chooses to play it.

Use motion only when it helps

Motion can show a menu change, confirm a form action or demonstrate a product. It can also delay content or make a page difficult to follow.

Respect the prefers-reduced-motion setting, a device or browser preference that reduces animation for people who request less motion. Keep essential service details readable without animation, and avoid scroll effects that make text hard to track.

Test common phone failure states

Do more than resize a desktop browser. Test the same page on a phone using mobile data and, where possible, a weaker connection. Use the same device and browser for both checks when practical, then record the device, browser, connection, page and what happened. Agree any load-time target with the developer before deciding whether speed passes; without an agreed target, record the observed delay and whether it prevented the visitor from seeing or using the service details and main action. Check:

  • the page on mobile data and in portrait orientation;
  • larger text or browser zoom;
  • a slow form submission, an invalid entry and the success message;
  • the form failure and retry path described above;
  • the phone link and WhatsApp handoff;
  • whether the keyboard covers the active field or button.

Record the device and exact failure so someone can reproduce it. For tel: links and reduced-motion preferences, see MDN’s HTML anchor element reference and prefers-reduced-motion reference.

Measure enquiry outcomes with care

Where your analytics tools and privacy choices allow, compare mobile page visits with call-to-action link clicks, form starts, completed forms, calls, WhatsApp conversations and qualified enquiries. A qualified enquiry fits the services and locations your business supports. Prefer aggregate counts, and do not collect message contents or personal details you do not need. Check recorded actions against the enquiries your team receives.

Choose the next step for your site

Ask a colleague to try this without help: “Find the service you need, decide whether it fits, then show me how you would contact us.” Note where they pause, what they cannot find, any error, and whether the call, message or form works. Mark a blocker when the person cannot find essential service information or complete the contact task; mark a preference when the task succeeds but they would choose a different look or wording. Fix blockers before preferences, starting with the point that stops the task. Record the device, browser, page and what happened so the team can repeat the check. Add a sticky bar or animation only after the main task works.

For related guidance, see the service-page structure guide, the WhatsApp enquiry journey and the Core Web Vitals guide.

Google’s mobile-first indexing guidance explains how Google uses mobile content. web.dev’s responsive web design guide covers small-screen-first layouts, flexible content and breakpoints.

IDJoy includes mobile enquiry actions in its website design and redesign work.