Yes, your website needs to work on phones, and “works” means more than “shows up.” Google reads the phone version of your site when it decides what your pages are about and where they rank, and almost every customer you have carries a smartphone. A site that works on phones lets people call you with one tap, read without zooming, hit buttons with a thumb, load quickly on cell data, and fill out your form without a fight.
Why does Google care about the phone version?
Because Google ranks your site based on the phone version. Its own guide for site owners says it plainly: “Google uses the mobile version of a site’s content, crawled with the smartphone agent, for indexing and ranking” (Google Search Central). This is called mobile-first indexing.
What that means for you: if something is on your desktop page but missing or hidden on the phone version, Google may not count it. Google’s guide tells owners to make sure the mobile site “contains the same content as your desktop site.” A services list that collapses into a menu nobody opens is fine. A services list that simply disappears on phones is a problem.
You don’t need a separate phone site or an app. Google says a separate mobile version isn’t required. One site that rearranges itself for the screen is the normal way to do it.
How many of your customers are on phones?
Nearly all of them carry one. The Pew Research Center’s 2026 survey found 91% of U.S. adults own a smartphone, and 16% own a smartphone but have no home broadband (Pew Research Center). For that 16%, the phone is the internet. If your site doesn’t work on it, you don’t exist to them.
Think about when people find a trade business. A homeowner sees water on the floor and searches from the basement. A roofer’s next customer is standing in the driveway after a hailstorm. A landscaper’s customer is scrolling at night on the couch. A diner looking for dessert is on the sidewalk. None of them walk to a desktop computer first.
Tip: your own website’s visitor numbers can tell you exactly how many come from phones. Ask whoever runs your site for the split between phones and computers over the last three months. Most local businesses are surprised.
What does “works on phones” actually mean?
It means a stranger can do what they came to do with one thumb, standing up, on a cell signal. In practice that is five things:
| What | What it looks like when it works | What it looks like when it doesn’t |
|---|---|---|
| Call | A call button on every screen; one tap dials | The number is in the footer, or it’s a picture |
| Read | Text is readable at normal size and zoom still works | You pinch to read, or zoom is blocked |
| Tap | Buttons are big, with space between them | You hit the wrong link with your thumb |
| Load | The page shows up in a couple of seconds on cell data | A blank screen while giant photos load |
| Forms | A few boxes; the phone fills in name and number | Ten boxes, tiny fields, typing everything |
The single most important of the five is the call button. Put it at the top of the page and keep it on screen as people scroll, usually as a bar at the bottom. The number has to be real text set up as a phone link, so the phone offers to dial it. A plumber or HVAC company that answers after hours should say so right next to the button. The other four are below, each with the rule behind it.
Readable without zooming, and zoom still allowed
Text should be big enough to read at normal size, in one column, with no sideways scrolling. Zoom should still work for people who need it. The accessibility standard most of the web follows says text must be able to grow to 200 percent without anything breaking (W3C, WCAG 2.2). Some sites switch zoom off with a single setting, and the web’s main reference for developers warns that this keeps people with low vision from reading the page (MDN). Your older customers are the ones who notice.
Buttons big enough for a thumb
Every button and link should be easy to hit without hitting its neighbor. The accessibility standard sets the minimum at 24 by 24 pixels at Level AA (W3C, target size minimum), and a stricter level at 44 by 44 pixels (W3C, target size enhanced). Treat 24 as the floor and build the important buttons, like call and request a quote, to the bigger size. A row of tiny links squeezed together is the most common miss.
Fast on cell data
A phone page should show its main content in a couple of seconds, even on a weak signal. Google’s speed tool calls a page good when its biggest piece of content loads within 2.5 seconds, and when the page reacts to a tap within 200 milliseconds (Google). The usual problem is photos uploaded straight from a camera, several megabytes each. Shrinking them to the size of the screen, and loading the ones lower on the page only when someone scrolls to them, fixes most slow sites.
Forms you can fill with a thumb
A quote form on a phone should be short and let the phone help. Ask only what you need to call back. Label every box. Set up the name, phone and email boxes so the phone can offer to fill them in: the accessibility standard asks for exactly this, because it saves typing for everyone and especially for people who find typing hard (W3C, identify input purpose). Then send yourself a test and make sure it arrives.
How can you test your own site for free?
You can check most of this in five minutes with your own phone and one free Google tool.
- Use your own phone, not your office computer. Open your site the way a customer would: search your business name on Google and tap the result.
- Tap the phone number. Does the phone offer to call?
- Read a paragraph. Could you read it without pinching? Try pinching anyway: does zoom work?
- Swipe sideways. If the page slides left and right, something is too wide.
- Tap every button with your thumb, including the menu. Count the misses.
- Fill out your own form and check that it reached you.
- Run PageSpeed Insights. Paste your web address and look at the mobile result. Google’s tool reports on both phone and desktop (Google). Green is good. Red on mobile means visitors are waiting.
- Ask someone over 60 to find your number and send you a request. Watch, don’t help.
Write down what went wrong. That list is what to ask your web person to fix, or what to compare when you get quotes. Our guide on what a contractor website should have covers what should be on the page once it works.
How we build phone-first for you
We design every site on a phone first and the desktop second. Every site gets a call bar that stays on phone screens and tap-to-call throughout the page, so one tap reaches you from anywhere. Zoom is always allowed, every image has alt text, and tap targets are large. Before anyone sees it, each site is checked at three phone screen sizes and passes an automated accessibility check with zero critical or serious issues.
Pages are small and light: images load as you scroll, and there are no ad trackers. Our best build so far scored 100 in all four categories on Google’s speed test. Forms are short, with spam protection, and land where you will see them.
You see your new site working on your own phone before you pay. The build is $5,000, one time. After launch it’s $99 a month for Care or $249 for Growth, month to month, and every change you email us gets the same phone check as launch day. On Growth, every month we read Google’s report of the searches that found you and fix the pages that fall short. We build everything Google needs. Nobody can promise a ranking.
See what we build and what it costs, look at sites we’ve built, or apply in about two minutes.
Sites we've built
Test your site on your own phone
0 / 6
Tap to tick. Your ticks stay on this device.