Is Your Website Good on a Phone? A Ten-Minute Check You Can Run Yourself
It’s evening, someone is on a bus, and they type “electrician Wrocław Krzyki” into their phone. They land on your site. The text is so small they have to pinch it open, the menu is hiding somewhere past the edge of the screen, and the phone number turns out to be an image nobody can tap. Six seconds later they are back in the search results, calling someone else.
You will never see that happen. On your computer the site looks fine, because that is where you approved it and that is where you glance at it once a quarter. The trouble is that almost none of your customers look at it that way. This article shows you how to check your own site the way a customer does, and what to do with what you find.
Your customers are on a phone, you are looking at a monitor
For local services, phones usually account for 60-80 percent of visits. In emergency trades where “right now” is the whole point (plumbers, roadside assistance, locksmiths) it can pass 85 percent, because nobody looks for that kind of help while sitting at a desk. Even in services people plan well in advance, like a wedding photographer or an accounting firm, the first contact with your business almost always happens on a small screen, with the decision coming later.
You don’t have to take my word for it. If your site has any analytics, it will break traffic down by device and give you your own number instead of an average from an article. For how to read numbers like that without drowning in charts, see the piece on how to know if your website actually works.
What “responsive” means in plain language
A responsive site is one set of content that rearranges itself depending on screen width. On a desktop your services sit in three columns side by side; on a phone the same services stack one under another. The menu collapses into a button. Images shrink to the width of the screen instead of sticking out past it. Nothing disappears, the layout simply changes shape.
There is also the old approach of a separate mobile version at an address like m.yourbusiness.com. Ten years ago that was normal practice. Today it leads nowhere: two sites to update, twice as many chances for one of them to go stale, and endless confusion about which version Google should show. If your developer proposes this, it is fair to ask when they last built a site.
The symptoms that give it away
You need no tools for this part, just an honest look at your own phone.
- You have to pinch the text open before you can read it.
- The page scrolls sideways and content runs off the right edge.
- Buttons and links sit so close together that your thumb keeps hitting the wrong one.
- The phone number is text or an image rather than a link that dials.
- The menu opens over half the screen and refuses to close.
- The cookie banner covers most of the view and pushes the accept button off screen.
- The contact form asks for seven fields, to be typed one-handed on the move.
- The map grabs the scroll, so you get stuck on it halfway down the page.
One symptom off that list is survivable. Three of them mean you are losing calls that nobody will ever count for you.
The ten-minute check
Put the laptop away. Pick up your phone and open your own site over mobile data rather than home wi-fi, because the customer standing in a car park does not have fibre either. Then walk the customer’s path without zooming in once.
- Find what you do and where you work. It should be visible before any scrolling.
- Look for a price or a range. If there isn’t one, note that as a separate problem.
- Tap the phone number. The dialler should open with the number already filled in.
- Send yourself an enquiry through the form, holding the phone in one hand.
- Turn the phone sideways and see whether the layout falls apart completely.
If that walk took you more than about ninety seconds and you hesitated even once, your customer will hesitate too. The difference is that they have two competitor tabs already open.
One tool is worth adding at the end: Google PageSpeed Insights, the mobile result. It reports loading time and lists concrete problems, including text that is too small and tap targets that sit too close together. A warning about older guides: Google retired both the standalone Mobile-Friendly Test and the Mobile Usability report in Search Console at the end of 2023. Anyone still pointing you to those tools is working from stale notes.
| Symptom | What the customer loses | Effort to fix |
|---|---|---|
| Sideways scrolling | Patience in the first few seconds | Usually one styling fix |
| Phone number not tappable | The simplest possible contact | Fifteen minutes |
| Tap targets too small | Hits the wrong element, returns to Google | An hour or two |
| Heavy photos straight from a camera | Several seconds of loading on mobile data | Depends on how many |
| Layout designed for a monitor | Effectively the whole site | A rebuild, not a fix |
Google looks at your site through a phone
That is not a metaphor. Google indexes sites with a mobile crawler and judges what that crawler sees, not the desktop version. So if something was tucked away on mobile “to save space”, your service descriptions, the list of towns you cover, then as far as search is concerned that content does not exist. Sites fail to rank for local phrases for exactly this reason while their owners go hunting for a link building problem.
When a site is missing from the results altogether, there are more possible causes and they are worth working through in order. I listed them in the article on why your website is not on Google. The mobile version is one of them, rarely the only one. For phrases like “hairdresser Ursynów”, most of the work sits in your content and in the consistency of your local data, which I covered in the guide to local SEO for a small business.
Speed is the other half of the same problem
A site can be properly responsive and still drive people away because it takes four seconds to appear. A phone has a weaker processor than a laptop and a worse connection, so everything that goes unnoticed on a desktop becomes visible on mobile: photos straight out of a camera, carousels, plugins that each bolt on a few more scripts. Layout and speed get judged together, because the customer does not separate the two sensations. For what Google measures and how to reach a PageSpeed score of 90+, see the article on business website speed.
Your site failed. Now what
Work out the scale first. If the problems are small tap targets, a phone number that doesn’t dial and two four-megabyte photos, you are looking at a few hours of work. A developer will typically charge somewhere around PLN 100-200 an hour and the whole thing closes for a few hundred. Throwing the site away at that point would be a waste.
It gets worse when the layout was designed for a monitor and only afterwards did someone try to squeeze it onto a phone. Sites like that cannot be patched sensibly, because every fix exposes the next one. The same goes for a site with nothing to show: if the desktop version is a slogan and a stock photo, there is nothing for the mobile version to rescue.
In that second case a new site works out cheaper than patching the old one. With Sitario you describe your business in a form and look at the finished site about an hour later. The layout is built phone first, and every site we ship gets measured in PageSpeed Insights with a target of 90+ on mobile. The Start plan costs PLN 249 as a one-off, including the first year of hosting; you pay only after seeing the finished site, and the domain and source files are yours. After launch you get a panel with statistics and an enquiry inbox, so you can see how many calls and form submissions the site brought in rather than guessing.
When this is not your problem
Honestly: a mobile-ready site will not change anything for every business. If your work comes from tenders and long B2B relationships, and the site serves as a reference point for a contractor who already knows you, a rebuild will not pay for itself in phone calls. If what you need is a shop with stock levels, calendar booking with payments, or a system wired into your inventory software, that is a job for an agency rather than a done-for-you product.
One more thing. A site that works beautifully on a phone will not bring you customers on its own. It only stops losing them. Traffic comes from your Google Business Profile, from content matched to what people actually search for, and from reviews. The mobile version decides what happens to that traffic after the tap.
Summary
Pick up your phone, open your own site over mobile data, and try to find a price and place a call within a minute without zooming. The entire diagnosis fits into that one move. If it goes through without friction, check the mobile score in PageSpeed Insights and get back to work. If it snagged, write down exactly where it snagged and decide: a few fixes from your developer, or a site built from the start for the screen where eight customers in ten will see it.