Mobile website redesign services

Ask to see the problems on a phone

A credible provider starts by trying your site on real phones and recording what goes wrong: a button hard to tap, a form field hidden by the keyboard, a menu that is slow to open. Screenshots or short recordings make the problems concrete and give a baseline for later comparison.

Providers who only describe mobile issues in general terms may not have looked closely.

Proof of improvement to ask for

Questions to ask

Not forgetting desktop visitors

Mobile improvements change shared layouts, so desktop pages change too. A careful provider checks desktop layouts at each step, making sure that reordering content for phones does not leave large screens awkward or empty.

The goal is one site that works well everywhere, not a mobile site with a neglected desktop version.

Warning signs

• Testing only in a desktop browser

  Simulation misses real-phone issues such as keyboards and touch.

• Separate mobile site proposed

  Two sites to maintain, usually unnecessary today.

• No baseline recorded

  Without before evidence, improvement cannot be shown.

Mobile and accessibility together

Many mobile fixes, such as larger tap targets, readable text, clear focus and forms that work with assistive tools, also improve accessibility. A provider who considers both together delivers a site that works for more people, including those using screen readers or enlarged text on their phones.

Why a baseline matters

Before any change, record how the site performs on phones: screenshots of key pages, the time it takes to find contact details, whether forms can be completed and how quickly pages load on mobile data. This baseline turns "it feels better" into evidence, and it protects you from paying for changes that look different but do not help.

A provider who suggests recording the baseline unprompted usually has a disciplined process.

How an engagement runs

1. 01

   Baseline

   Phone tests and screenshots recorded.

   Output: Before evidence

2. 02

   Plan

   Changes prioritised by impact on phone visitors.

   Output: Agreed scope

3. 03

   Redesign

   Components and templates updated on staging.

   Output: Reviewed changes

4. 04

   Compare

   Same tests repeated after launch.

   Output: After evidence

Your input matters

You know which questions customers ask on the phone and which pages they mention. Sharing that helps a provider decide what mobile visitors need first. A short conversation with whoever handles enquiries often reveals the most important mobile fixes faster than any analysis.

Forms on phones deserve special attention

Phone forms fail in ways desktop testing rarely reveals: a keyboard that covers the submit button, a date picker that is hard to use, an error message that appears off-screen. Ask a provider to show a form being completed on a real phone, including a deliberate mistake, so you can see how errors are handled.