Phone-first websites: built for the customer holding one
Most people who find a local business do it on a phone, often standing in the problem: a leak under the sink, a dog that needs a groom before the weekend, a fence blown down overnight. A website designed on a big screen and squeezed onto a phone lets those people down. This guide explains what phone-first means in practice and how to check your own site.
6 min readUpdated The team at Vantage Point Digital

Contents
- Why the phone version is the real version
- Speed: the measurements Google uses
- What slows small business websites down
- The first screen on a phone
- Tap targets, text and forms
- Layout habits that work on phones
- Accessibility helps everyone
- How to test your own site in fifteen minutes
- What this means if you are choosing a website
- Questions people ask
Why the phone version is the real version
Ofcom's research into how people in the UK go online has shown for years that the smartphone is the device most people use most. For local services the share is higher still, because people search when the need arises, wherever they are. A customer on a laptop at a desk is the exception.
Google has made the same shift. It uses mobile-first indexing, which means it primarily looks at the mobile version of a page when deciding how to rank it. If your phone layout hides content, loads slowly or is hard to use, that is the version Google judges you on.
Speed: the measurements Google uses
Google's Core Web Vitals are three measurements of how a page feels to use. Google publishes thresholds for each:
| Measurement | What it means | Google's "good" threshold |
|---|---|---|
| Largest Contentful Paint (LCP) | How long until the main content, usually the big heading or photo, appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds when you tap something | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much things jump around while loading | 0.1 or less |
You can check any page with Google's free PageSpeed Insights tool. It shows real-world data from Chrome users where Google has enough of it, plus a lab test. Run it for your home page and your most important service page, and look at the mobile results, not desktop.
Speed matters beyond Google. A page that takes several seconds to show anything on 4G in a car park loses people to the next result before they have seen your work.
What slows small business websites down
Photos
The number one cause, and photographers feel it most; our guide for photographers covers galleries that stay fast. A photo straight off a modern phone can be several megabytes. A gallery of twenty of them, uncompressed, can make a page weigh more than a feature film trailer. The fixes:
- Resize photos to the largest size they will actually be shown at.
- Use modern formats such as WebP or AVIF, which are much smaller than JPEG at the same quality.
- Let photos further down the page load only when the visitor scrolls to them (lazy loading).
- Serve smaller versions to phones and larger ones to big screens.
Too much code
Website builders and themes often load scripts for features you do not use: sliders, animations, chat widgets, several tracking tools, fonts in six weights. Each one adds weight and delay. Remove what you do not need.
Slow hosting
Cheap shared hosting can take a second or more just to start sending the page. A fast host, or a content delivery network that serves your site from near the visitor, makes a noticeable difference.
Pop-ups
A full-screen pop-up the moment someone arrives is irritating on a phone and can count against you. Google's guidance has long discouraged intrusive interstitials that cover the main content on mobile, apart from necessary ones like cookie notices.
The first screen on a phone
On a typical phone, the first screen, before any scrolling, is a small space. It needs to carry:
- Your business name or logo, small.
- A heading saying what you do and where: "Mobile dog groomer in Chelmsford".
- A tap-to-call button, and ideally a second option such as a message link.
- One line of proof: an accreditation, years trading, or a real review rating.
A huge photo with a slogan over it, pushing everything else below the fold, wastes this space. Photos are vital, but they can come a scroll later.

Tap targets, text and forms
- Buttons should be big enough to hit with a thumb, with space between them. A common guide is at least 44 to 48 pixels square.
- Text should be readable without zooming. Body text around 16 pixels is a sensible minimum on mobile.
- Phone numbers should be links that start a call when tapped.
- Addresses should link to a map for directions if customers visit you.
- Forms should ask only for what you need: name, phone or email, postcode and a short description. Use the right keyboard for each field so a phone number field brings up the number pad. Never make people create an account to enquire.
- Menus should be short. If a phone menu has fifteen items, most will never be tapped.
Layout habits that work on phones
- One column. Content stacked in a single column, in order of importance.
- Short paragraphs. Two or three sentences. Long blocks of text look like walls on a small screen.
- Headings that summarise. Many people scan the headings and read only the part they need.
- Sticky call button. A call button that stays visible at the top or bottom of the screen as people scroll.
- No horizontal scrolling. Tables and images should fit the width or be designed for small screens.
- Contrast. Light grey text on white is hard to read outdoors in daylight. Strong contrast helps everyone.
Accessibility helps everyone
A site that works well on a phone is usually a site that works well for people with poor eyesight, shaky hands or a slow connection too. Proper headings, descriptive link text, alt text on images, good contrast and buttons that can be reached by keyboard all help. Many of your customers will be older homeowners, and readable text and big buttons matter to them.
How to test your own site in fifteen minutes
- Open your site on your own phone, on mobile data with Wi-Fi off
- Count the seconds until you can see what you do and where
- Check you can call with one tap from the first screen
- Try the menu: can you find each service in two taps?
- Fill in your own contact form. How long did it take? Did it work?
- Look at your galleries: do photos appear quickly?
- Run PageSpeed Insights on the home page and check the mobile score
- Ask someone over 60 to find your phone number and book you, and watch without helping
What this means if you are choosing a website
When anyone shows you examples of their work, look at them on your phone, not on their laptop. Ask what they do about photo sizes, which hosting they use, and whether pages pass Core Web Vitals. Our guide to what a trade website needs covers the content side, and our guide to website costs covers the money.
Every site we build is designed for phones first; our how it works page explains the process. If you want to see how your current site performs, our free Business MOT loads it on a phone and tells you what is slowing it down.
Questions people ask
- How fast should my website load on a phone?
- Google's guidance is that the main content should appear within about 2.5 seconds, which it measures as Largest Contentful Paint. You can check your pages with Google's free PageSpeed Insights tool.
- What is mobile-first indexing?
- It means Google primarily uses the mobile version of a page to decide how to index and rank it. If your phone version is missing content or works poorly, that affects your search visibility.
- Why is my website slow on mobile?
- The most common causes are large uncompressed photos, too many scripts and plugins, and slow hosting. Resizing and compressing images is usually the quickest improvement.
- Do I need a separate mobile website?
- No. A single responsive website that adapts its layout to the screen is the standard approach and what Google recommends. Separate mobile sites are an older approach that creates extra work.



