Mobile redesign
A mobile redesign reworks the pages of an existing site so they are comfortable to read and use on a phone, starting with the pages people visit most.
Short answer
A mobile redesign suits a site that technically shrinks to fit a phone but is awkward to use on one. We redesign the key page types for small screens first, fix tap targets, forms and content order, then check the result on real devices.
Shrinking is not the same as working
Many older sites are described as "responsive" because their layout narrows to fit a phone. That is a start, but it does not mean the site is pleasant to use. Common problems include text that is too small to read without zooming, buttons placed so close together that people tap the wrong one, menus that cover the whole screen and cannot be closed easily, and long pages where the useful part sits below several screens of large images.
A mobile redesign fixes those problems by treating the phone as the main screen, not an afterthought. We design for the smallest common screen first, then let the layout grow for tablets and desktops.
What we look at
Content order
On a desktop, content sits side by side. On a phone, it stacks. The order it stacks in matters, because people may never scroll past the first two screens. We decide what each page type should show first, usually what the business does, where it works and how to get in touch, and make sure the layout delivers it in that order.
Reading comfort
We set body text at a size that can be read without zooming, keep line lengths comfortable and make sure text has enough contrast against its background. We also check that pages still work when someone has increased the text size on their phone.
Tap targets
Fingers are less precise than a mouse pointer. WCAG 2.2 introduced a minimum target size criterion for exactly this reason1. We make sure buttons, links and form controls are large enough and spaced well enough to be tapped reliably. Our WCAG 2.2 guide lists the other criteria that version added.
Forms
Forms are where mobile visitors most often give up. We cut fields you do not need, use the right keyboard for each field so phone numbers bring up a number pad, label every field clearly and make error messages say what went wrong and how to fix it.
Navigation
We design a menu that opens and closes predictably, can be used with one hand and does not trap keyboard or screen reader users. Your phone number and main call to action stay easy to reach without opening the menu.
Speed
Phones are often on slower connections than office computers. A mobile redesign includes basic speed work: images sized for the screen they appear on, fewer scripts and fonts that load without blocking the page. For deeper speed work, see the performance clean-up service.
How Google measures mobile experience
Google's Core Web Vitals measure loading, responsiveness and visual stability. A page counts as "good" when its largest element shows within 2.5 seconds, it reacts to input within 200 milliseconds and its layout shift score stays at 0.1 or lower, with phones and desktops scored separately at the 75th percentile2. We record your current figures before starting, where enough data exists, and compare afterwards. Our guide to Core Web Vitals explains what each measure means in plain terms.
Testing on real devices
Phone emulators built into desktop browsers catch plenty, yet they miss things. We test on real iPhones and Android phones of different sizes, and we aim to include an older, slower model too, because that is what many of your customers carry. Where the project includes it, we also check the main journeys with each phone's built-in screen reader.
Platform and design
A mobile redesign usually stays on your current platform. If your theme cannot be adapted without fighting it at every step, we will explain the options. Sometimes the most economical route is a new theme on the same platform. Occasionally a full redesign costs less over time.
The visual design changes as much as it needs to. Some sites only need new layouts for small screens. Others need a lighter design overall, because heavy decoration that looks fine on a large monitor gets in the way on a phone.
What you receive
- Mobile-first designs for each key page type, approved before build
- The rebuilt layouts on your current site, tested on real devices
- Before-and-after Core Web Vitals figures where data is available
- Notes for your team on keeping new content mobile-friendly, such as image sizes to use
Mobile redesign questions
Should we build a separate mobile site?
No. A separate mobile site means two sets of pages to maintain and extra work for search engines. One site whose layout adapts to the screen is simpler and is what we build.
Will the desktop version change too?
Usually a little. Designing for small screens first tends to tidy up the desktop layout as well. We show both versions in the designs before any build work.
Can you fix only the pages that matter most?
Yes. A sensible order is the home page, the main service or product pages and the contact page, then the rest over time.
Sources
Each source was opened and checked against the sentence it supports on 3 November 2026.
- What's New in WCAG 2.2 Standards body
- Web Vitals Platform documentation
Ready to plan your redesign?
Tell us what your current site does well and what holds it back. You get a written, fixed quote in NZD before any work starts.