Approve your website design on a phone first
Google reads the phone version of your site, and so do most of your visitors. A simple routine for reviewing a design on your own phone, and the questions to ask your agency before you sign off.
November 12, 2026Last updated November 12, 2026
Google starts from the phone. It uses the mobile version of a site’s content for indexing and ranking.
Which makes the usual website approval a little odd. The design gets presented on a big screen in a conference room. Everyone admires the wide photos and the three neat columns. Someone says “looks great, ship it” from a laptop. Meanwhile your customers are standing in line somewhere with one thumb free.
Approve the design on a phone first
Ask your agency to show you every page on a phone before you see it on a laptop. Better yet, open the preview link on your own phone, on the bus, with bad signal. That’s the real test. Things that looked elegant on a big screen, like a slow hero video or a menu hidden behind three taps, show their true cost right away.
It helps to think about where your visitors actually are when they find you. A dad in a pharmacy parking lot, looking up whether the pediatric clinic takes walk-ins on Saturday. A volunteer on her lunch break, trying to find the sign-up form for next week’s food drive. Someone at a bus stop comparing two plumbers before the bus arrives. None of them is sitting at a desk with a second monitor.
The conference room presentation still has its place. Just make it the second look, after everyone on the approval list has spent ten minutes with the site on their own phone.
How to review a site on your phone
A phone review goes better with a plan. Otherwise it turns into scrolling up and down and saying “seems fine.” Here is a simple routine that takes about twenty minutes:
- Pick the three things most visitors come to do, such as finding your hours, booking a visit or making a donation, and do each one start to finish.
- Do it once on Wi-Fi and once on mobile data, ideally somewhere the signal is weak.
- Try it with one hand, holding the phone the way you would on a bus.
- Turn the phone sideways once, and make your phone’s text size bigger once, and see what breaks.
- Write down every moment you had to pinch, zoom, hunt or wait.
That list of moments is your real feedback for the agency. It’s far more useful than “can the logo be bigger,” and it gives the agency specific things to fix.
Ask at least one person outside the project to do the same routine. Try a board member who reads with glasses, or a relative who has never seen the site. They will find things the team stopped noticing weeks ago. Hand them the phone, give them one task and stay quiet while they try. The urge to say “it’s right there, at the bottom” is strong. Write it down instead, because every real visitor will be on their own.
Put the important button where a thumb can reach it
On a phone, the most important action should be easy to find and easy to tap: call, book, give, order. Small text links squeezed between paragraphs don’t count. Neither do forms with eleven fields that each open a different keyboard.
Size matters here in a measurable way. The W3C’s accessibility guidelines set a minimum size for anything you tap, because some people with limited hand movement can’t hit small buttons that sit close together. In practice, everyone benefits. Anyone who has tried to tap “Call” on a crowded bus and hit “Directions” instead knows the feeling.
Check where the main button sits, too. Sometimes the phone number is buried at the bottom of a long page. A sticky bar at the bottom of the screen, or a clear button near the top, saves a lot of scrolling.
Every field is a small chore on a phone
Forms are where phone visitors give up most quietly. On a laptop, eleven fields is a minute of typing. On a phone, it’s a minute of tapping, switching keyboards, losing your place when autocorrect changes a last name and starting over.
Ask for the least you need to reply. A name, a way to reach them and a short message is enough for most first contacts. Make sure the phone field opens the number keypad and the email field opens the keyboard with the @ sign. Those are small settings that a developer can turn on in minutes, and they make the form feel like it was built for the person filling it in.
Then test the form yourself, on your phone, and check that the message arrives. We wrote more about the second half of that in who reads your website forms.
Everything on the page has to travel
On office Wi-Fi a heavy page loads fine. On a phone with two bars, every large photo and every extra script is something the visitor waits for. Compress the images, cut what nobody uses and test on a real phone connection as well as the office one.
Google has a set of measurements for this called Core Web Vitals. One of them tracks how long the main content takes to appear, and Google’s guidance is that it should show up within 2.5 seconds of the page starting to load. On a weak signal, a heavy page can take much longer than that.
The usual culprits are easy to spot once you look. A full-screen background video that plays on every visit. Photos uploaded straight from a camera, many times larger than the screen showing them. A chat widget, two analytics tools and a social feed that each load their own code. You don’t need to remove everything. Ask what each one is doing for the visitor, and keep the ones with a good answer.
Photos deserve a specific question for your agency: are the images resized for phones, or does every phone download the same huge file as a desktop? A good build sends a smaller version to smaller screens. It’s invisible when it works, and it’s often one of the simplest speed improvements on the whole site.
Don’t hide things to make it fit
The old habit was to strip the mobile site down: fewer sections, a shorter menu, the details “available on desktop.” Since Google reads the phone version, anything you hide there is something Google may never see.
Google’s own advice is direct: make sure your mobile site contains the same content as your desktop site. The same page asks for matching image descriptions, structured data and page titles on both versions.
So rearrange it, shorten the sentences and stack the columns, while keeping the substance. A phone visitor who wants the full list of services, the parking details or the price table should be able to find it, even if it sits one tap further down.
What to ask before you approve
You don’t need to know how any of this is built to ask good questions. Before you sign off on a new site or a redesign, ask your agency these:
- Can we review every page on a phone first, using a preview link we can open ourselves?
- Which pages have you tested on a slow mobile connection, and how did they do?
- Is anything on the desktop version missing or hidden on the phone?
- How big are the main buttons on a phone, and is the most important one visible without scrolling?
- What loads on every page that a visitor never sees, like tracking codes or widgets?
A good agency will have answers ready, probably with screenshots. If the answer to the first question is “we usually present on a big screen,” ask them to add a phone review before the big-screen one.
If you’d like us to look at your site the way your customers see it, on a phone in a hurry, book a 30-minute call and we’ll do the walk-through together.
