A Ten Point Phone Test for Your Cafe Website

Thomas Garner

Oct 7

11 min read

A cell phone sitting on top of a wooden table

You built or inherited a website while sitting at a desk, on a big screen, with a mouse and a fast connection. Your actual customer is standing on a sidewalk, one thumb free, phone signal weak, wanting to know if you are open right now and which way to walk. Short answer: run this ten point test on your own phone, on cellular data, and score yourself honestly against what a hurried stranger actually needs.

Most visits to a small cafe website are quick, practical checks, not leisurely browsing: hours, address, menu, and directions. A test built around those needs finds the problems that lose visits, rather than the problems a desktop review would notice first. The ten points below are concrete, each with a pass and fail description, so you can score your own site out of ten and walk away with a specific fix list, not a vague sense that mobile matters.

Why Test on Your Own Phone

A laptop review of your website tells you almost nothing about what a phone visitor experiences, because the two are genuinely different devices with different screen sizes, different input methods, and often a much slower connection. Google's own mobile first indexing guidance treats the mobile version of a page as the primary version it evaluates, which is a strong signal that mobile is not a secondary concern layered on top of a desktop site, it is the main event.

Testing on your own phone, specifically on cellular data rather than your shop's fast wifi, matters because your actual customer is rarely standing in your shop already connected to your network when they look you up. They are often outside, walking past, or a few blocks away deciding whether to detour toward you, running on whatever signal their carrier gives them at that moment. A site that loads fine on wifi can feel painfully slow on a weak cellular connection, and that gap is exactly what this test is built to catch.

Set aside fifteen minutes, put your phone on cellular data, and go through the ten points below on your own site, one at a time, scoring pass or fail as you go. Do not test from inside your shop on your own wifi. Walk outside if you have to.

If you can, hand your phone to someone else and watch them try to find your hours or tap toward directions without any guidance from you. Owners tend to know their own site well enough to work around its problems without noticing them, tapping in the right spot out of habit rather than because the button is easy to hit. A second person who has never seen the site before will stumble on exactly the friction points this test is designed to catch.

The Ten Points

One, hours visible without scrolling. Load your homepage and, without scrolling down at all, check whether today's hours are visible somewhere on the screen. Pass means a visitor sees your hours in the first view. Fail means they have to hunt for it.

Two, tap to call. Find your phone number on the site and tap it. Pass means it opens your phone's dialer automatically. Fail means it is plain text that has to be copied and pasted or manually dialed.

Three, tap for directions. Find your address and tap it. Pass means it opens a maps app or a map view ready to navigate. Fail means it is plain text with no linked action.

Four, menu readable without zooming. Open your menu page and read it at the normal zoom level your phone opens pages at. Pass means the text is legible without pinching to zoom in. Fail means you have to zoom to read prices or items.

Five, no popups over the content. Load your homepage fresh and watch what appears in the first few seconds. Pass means nothing blocks the hours, address, or main content. Fail means a popup, banner, or overlay covers the information a visitor came for.

Six, buttons large enough to tap. Try tapping your main buttons, call, directions, order, or menu, with your actual thumb, not a stylus or a careful fingertip. Pass means you hit the right button on the first try consistently. Fail means you keep missing or hitting the wrong neighboring link.

Seven, fast first screen. Time how long it takes from tapping your link to seeing a usable page, roughly, using a phone's stopwatch or just counting. A slow first screen on cellular data is a real, common failure point worth noting even without a formal speed tool.

Eight, no horizontal scroll. Load the homepage and try swiping left and right. Pass means the page stays within the screen width. Fail means part of the page runs off the edge and requires sideways scrolling to see.

Nine, address readable as text. Beyond the tap to open a map, check whether your full street address also appears as plain, readable text somewhere on the page, not only as an embedded map image. Pass means a visitor can read and copy the actual address. Fail means the address only exists inside a map graphic.

Ten, ordering or reservation link working. If you have an order online or reservation link, tap it all the way through to confirm it loads and functions, rather than assuming it does because it once worked. Pass means it opens and works as expected. Fail means it errors, loads a blank page, or leads somewhere unrelated.

Scoring Yourself Honestly

Give yourself one point for each pass, for a score out of ten. This is a self test, not a formal audit, so the value comes from your own honesty about a fail rather than from a polished number. It is tempting to call something a pass because you know where to look, but a real visitor does not have that advantage, so test as if you have never seen the site before.

A perfect ten is a fine outcome and worth confirming, not assuming. A score in the seven to nine range usually points to one or two specific, fixable gaps rather than a site wide problem. A lower score is worth treating as a priority list rather than a discouragement, since most of these ten points are quick to fix once identified, they just need someone to notice them from a phone in hand rather than a desk chair.

Retest after you fix something. A fix that looks right on a desktop preview does not always behave the same way on an actual phone, so the same phone, cellular data, thumb only test that found the problem is also the right way to confirm it is solved.

Resist the urge to average your score against some imagined typical cafe site. There is no documented benchmark this post can point you to for what a typical score looks like, and inventing one would not be honest. Your score matters relative to your own site, before and after you fix what fails, not relative to a number nobody has measured across cafes broadly.

What a Small Phone Test Actually Found

Running these ten points against a handful of cafe sites drawn from a broader dataset makes clear how easy some of these are to miss without ever putting a real thumb to a real screen. A ten site sample is a tiny, illustrative check, not a study, and any fail count from it describes that small sample on the date it was tested, not cafes generally.

The value of a test like this is less in any specific number and more in the pattern it reveals: problems that look fine on a desktop screen, a popup that is easy to dismiss with a precise mouse click, a button that is easy to hit with a cursor, a map embed that looks complete, often behave differently once you are working with a thumb, a smaller screen, and a real cellular connection. That gap between how a site looks to its owner and how it behaves for a visitor is the whole reason this test exists as a phone specific exercise rather than a general checklist.

This is also why the test asks you to use your own phone rather than a testing tool that simulates mobile. A simulation can check screen size and loading speed reasonably well, but it cannot replicate the actual experience of standing outside, signal wavering, trying to tap a button with your thumb while holding a bag in your other hand. That lived experience is what the ten points are built to surface.

It is worth returning to this test after any redesign, not just after a full rebuild. A single change, a new promotional banner added to the homepage, a new plugin, a widget for reviews or social feeds, can quietly introduce a popup or slow down the first screen without anyone intending it. The ten points are quick enough to run again after any change like that, which makes them useful as an ongoing habit rather than a one time exercise you do once and never revisit.

Turning Fails Into a Fix List

Write down every fail with enough detail that a fix is obvious later, not just a checkmark in a box. If your hours are not visible without scrolling, note where they currently sit on the page so whoever fixes it knows exactly what to move. If your call button does not trigger the dialer, note that specifically, since that particular fix is usually a small, mechanical change on most site builders once someone knows to look for it.

Prioritize by what a visitor needs most urgently. Hours, tap to call, and tap for directions tend to matter more in the moment than a slow first screen or a horizontal scroll issue, though all ten are worth fixing eventually. If you can only fix a few things this week, start with whichever fails would most directly stop someone from finding or reaching you.

Most of these fixes do not require a developer. On the major site builders, moving your hours higher on the homepage, converting a phone number into a clickable link, or removing an unnecessary popup are usually settings changes or small block rearrangements available in the same editor you already use to update your menu. Save the harder fixes, a genuinely slow first screen caused by large images or heavy scripts, for when you have more time or help, but do not let those harder items stop you from knocking out the easy ones first.

This test is deliberately separate from a full technical audit or a general list of weekend fixes for a cafe site. It exists to answer one specific question well: does this site work for a phone in hand, right now, for someone who has never seen it before. Score yourself, fix what fails, and retest on your own phone again in a month or so, since small changes elsewhere on the site can quietly break something that used to pass.

Keep the fix list somewhere you will look at it again, not just a mental note. A simple table with three columns, point, fail description, and fix status, is enough. Update it each time you retest, and you will end up with a running record of what your site's phone experience has looked like over time, which is worth more than a single one time score.

Frequently Asked Questions

What are the ten points in this phone test?

Hours visible without scrolling, tap to call, tap for directions, menu readable without zooming, no popups over the content, buttons large enough to tap with a thumb, a fast first screen, no horizontal scroll, address readable as plain text, and a working order or reservation link. Score one point for each pass, out of ten.

Why test on cellular data instead of my shop's wifi?

Because most visitors looking you up on a phone are not already sitting inside your shop connected to fast wifi. They are outside or nearby, running on whatever signal their carrier gives them at that moment. A site that loads fine on wifi can behave very differently on a weaker cellular connection, and that gap is exactly what this test is meant to catch.

What does Google's mobile guidance say about this?

Google's mobile first indexing guidance treats the mobile version of a page as the primary version it evaluates, which signals mobile is not a secondary concern added on top of a desktop site. Search Central's mobile site best practices cover related technical guidance, and this test translates that priority into ten practical, hands on checks an owner can run without technical tools.

How do I know if my call button is set up correctly?

Find your phone number on the site on your own phone and tap it directly. If it opens your phone's dialer automatically with the number already filled in, that is a pass. If it is plain text that has to be manually copied or dialed, that is a fail worth fixing, and it is usually a small, mechanical change on most site builders.

Should I trust a testing tool instead of my own phone?

A simulation based testing tool can check things like screen size and loading speed reasonably well, but it cannot replicate the lived experience of standing outside with a wavering signal, tapping a button with your actual thumb while holding something in your other hand. This test is built around that real experience specifically, which is why it asks for your own phone.

What counts as a fail for the popup point?

A fail is any popup, banner, or overlay that covers your hours, address, or main content in the first few seconds of a fresh load. Test it as point five of the ten, on your own phone, on cellular data rather than your shop wifi, without having visited the site recently. A popup that is easy to dismiss with a precise mouse click on a desktop often behaves differently under a thumb on a small screen. Nothing should block the information someone came to find, and that includes a new promotional banner added later.

How often should I rerun this test?

Rerun it any time you fix something on the list, using the same phone and cellular data conditions that found the problem, since a fix that looks right in a builder's preview does not always behave the same on an actual device. Beyond that, running it again every month or so catches anything that quietly broke from unrelated changes elsewhere on the site.

Does a low score mean my site is ranking poorly?

This test does not measure or predict rankings, and no ranking claim is made based on a score. It measures whether your site works for a phone visitor in practical, specific ways. A low score is a fix list, not a verdict on search performance, and most of the ten points are quick to address once identified.

What if my order or reservation link used to work but I have not checked it recently?

Tap it all the way through now rather than assuming it still works. Links to third party ordering or reservation platforms can break silently when the other platform changes something on its end, and the only way to know is to actually test the full path from your own site through to a working page.

Is this the same as a full technical SEO audit?

No. This test answers one narrower question: does the site work for a phone in hand, right now, for someone who has never seen it before. It takes about fifteen minutes on cellular data and scores ten pass or fail points, from hours visible without scrolling to a working order or reservation link. Google's mobile first indexing guidance treats the mobile page as the primary version it evaluates, which is why this test matters, but it is no substitute for a broader technical review. Hillcane can help at hillcane.co/contact or (256) 384-2449.

Work with Hillcane

You built your cafe site on a laptop. Your customer is on a sidewalk with one thumb and bad signal. Run this ten point test on your own phone to see what they actually experience.

Want a second set of eyes on your cafe site's mobile experience? Reach Hillcane at hillcane.co/contact or call (256) 384-2449.