Most visits to a local business website now arrive from a phone, frequently outdoors, often on an imperfect connection, and usually while the person is doing something else. Responsive design means the layout adapts to the screen size. Mobile optimization means the site is actually usable once it arrives there, which is a much higher bar.

The distinction matters commercially. A site that adapts but frustrates still loses the enquiry. Someone standing in a parking lot trying to find your phone number does not care that the layout technically reflows. They care whether they can call you within a few seconds.

Responsive and usable are not the same thing

A site can pass every responsive check and remain miserable to use. Tap targets too small or crowded too closely together. Phone numbers rendered as text rather than tappable links. Forms requiring pinching and zooming to complete. Menus that need two hands. Layout that shifts while images load, so the button moves at the exact moment someone reaches for it.

That last one has a name and a measurement. Cumulative Layout Shift is a Core Web Vital, and it is measured on mobile first. So are Largest Contentful Paint and Interaction to Next Paint. All three are ranking inputs, which means a site that frustrates people also underperforms in search. The two problems are really the same problem.

What actually breaks on phones

Certain failures recur across almost every site we assess. Images uploaded at full camera resolution and scaled down in the browser, so a phone downloads several megabytes to display something small. Fixed width elements causing horizontal scroll. Sticky headers consuming a third of a small screen. Modal popups that cannot be dismissed with a thumb.

Each is straightforward to fix in isolation. They persist because nobody tests on an actual device, and a desktop browser at a narrow width does not reproduce any of them convincingly.

How we test

• Check on physical devices across both iOS and Android rather than only in a resized desktop browser
• Test on a throttled connection, since your customers are not all sitting on office wifi
• Verify tap target size and spacing against accessibility guidance rather than judging by eye
• Confirm forms can be completed one handed without zooming or horizontal scrolling
• Measure Core Web Vitals from field data where it exists, not only from lab tools
• Check the site with a screen reader, since mobile accessibility and mobile usability overlap heavily

Field data deserves emphasis. Lab tools test a single simulated load on a fast connection. Field data reflects what your actual visitors experienced on their actual devices, and the two frequently disagree. When they do, the field data is the one that matters.

What you receive

• A device tested assessment showing where the mobile experience breaks and why
• Core Web Vitals measured from real user data where available
• Prioritised fixes ordered by impact rather than by ease
• Image and script handling corrected at the source rather than patched
• Verification after the work, on the same devices

Questions we get asked

My site is already responsive. Is that enough?

Often not. Responsive was the requirement a decade ago and is now the floor rather than the goal. The bar today is whether the mobile experience is genuinely good, and most sites designed on desktop and shrunk down are merely tolerable. Tolerable loses to good when both appear in the same set of results.

Does mobile speed really affect rankings?

Yes, though it is one factor among many rather than a switch that flips. The larger effect is behavioural. People abandon slow pages, and a page nobody stays on struggles to hold whatever position it earned. The ranking effect and the conversion effect point the same direction, which makes it an easy investment to justify.

Should I have a separate mobile site?

No. Separate mobile sites split content across two URLs and create duplication, maintenance, and tracking problems. The approach was largely abandoned years ago in favour of a single responsive site, and there is no good reason to revive it now.

What is a good Core Web Vitals score?

Passing all three thresholds on mobile field data is the practical target. Chasing a perfect lab score past that point produces diminishing returns quickly. It is more useful to pass consistently across your real visitors than to score highly in a single simulated test.

How much does this usually cost to fix?

Less than most people expect when the problems are image handling and script bloat, which is the common case. More when the underlying layout needs rebuilding. The assessment tells you which situation you are in before you commit to anything.

Will fixing this break my desktop site?

It should not, and if it does something was wrong with the original build. Mobile improvements are usually additive: smaller images, deferred scripts, and better spacing improve desktop performance as well. Genuine conflicts between the two are rare and manageable.

We will run your site through real device testing and show you precisely where the mobile experience falls apart, including the parts that look fine in a screenshot.