Website mobile optimization services

Questions to ask a provider

Journeys worth testing

Fix templates, not individual pages

Many mobile problems come from templates and shared components: the header, menu, buttons, forms and content blocks used across the site. Fixing these once improves every page that uses them and prevents the same problems reappearing when new pages are added. Page-by-page patches are slower, cost more and tend to be undone by later edits.

Ask any provider how their changes will apply to future pages.

Warning signs

• Separate mobile site

  A second version to maintain, with content drifting apart.

• Hiding content on mobile

  Visitors and search engines miss information.

• Desktop-only testing

  Real phone problems go unnoticed.

• Pop-ups covering content

  Frustrating on small screens; often dismissed instantly.

A typical engagement

1. 01

   Journey testing

   Key tasks attempted on several phones.

   Output: Findings with screenshots

2. 02

   Plan

   Template and component fixes prioritised.

   Output: Agreed changes

3. 03

   Implementation

   Changes made and checked on staging.

   Output: Improved templates

4. 04

   Verification

   Journeys retested on the same devices.

   Output: Before-and-after evidence

Mobile and accessibility overlap

Many mobile improvements also help accessibility: larger tap targets, readable text, clear labels and good contrast. WCAG 2.2 includes a minimum target size of 24 by 24 CSS pixels, with exceptions such as adequate spacing. A provider who considers accessibility while improving mobile layouts delivers more benefit for the same work.

Using your own data

Analytics can show what share of visitors use phones, which devices are common and where mobile visitors leave. Sharing this with the provider helps target the most important journeys and devices. If mobile visitors abandon the contact form or checkout much more than desktop visitors, that is a clear place to start.

Without analytics, testing the main enquiry path on a couple of typical phones is still a good starting point.

Content guidance

Some mobile problems come from content rather than code: very long paragraphs, wide tables pasted from spreadsheets, images with text inside them. A good provider explains how to write and format future content so it works well on phones, which keeps the site in good shape after the project ends.

Choosing between providers

Ask to see examples of mobile improvements they have made, with before-and-after screenshots on phones. Ask how they test, which devices they use and whether their changes are made in templates. A provider who talks about journeys and evidence, rather than only about responsive frameworks, is more likely to improve real outcomes.

The on-screen keyboard

When a form field is selected on a phone, the keyboard can cover half the screen, hiding the next field, error messages or the submit button. Testing forms with the keyboard open, and making sure the page scrolls sensibly, is a detail that separates careful mobile work from a quick layout adjustment.

Keeping it mobile-friendly

Ask the provider for a short checklist to use when adding new content or features, so mobile problems are not reintroduced.

Agreeing the limits

Agree which templates, components and journeys are in scope, and how issues found outside that scope will be handled. Mobile reviews often uncover related problems, such as slow images or outdated plugins; a clear process for deciding whether to address them avoids scope creep and surprises.