
Mobile website checks to make before you spend on ads
Paying for ads is paying to send people to your website. If the visit goes badly on a phone, the money is spent and the enquiry never arrives. A short check beforehand costs nothing and shows you problems that no ad can fix.
This is a checklist you can work through yourself, with no technical background. It covers what Google actually says about mobile sites, then five practical checks, then how to test them properly.
Why mobile comes first
Google indexes and ranks sites using the mobile version of your pages. Its own guidance is blunt: "Make sure that your mobile site contains the same content as your desktop site." If your phone version hides or drops content that your desktop version has, Google may not see it.
Google also recommends responsive web design, because it is "the easiest design pattern to implement and maintain". In a responsive site, one set of pages adjusts to the screen. You do not run a separate mobile site that can drift out of date. If your site was built on a modern template or builder, it is probably responsive already, but the checks below will confirm it.
Check 1: can a thumb hit the buttons?
Open your site on your phone and try to tap your menu, your main button and each link in your footer. Do you ever hit the wrong thing? Do you have to zoom in first?
web.dev recommends touch targets of "around 48 device independent pixels", which is roughly 9mm, with about 8px of space between neighbouring targets so that a tap does not land on the wrong one. You do not need to measure pixels. What you are looking for is buttons and links that are comfortably finger-sized, with a little room around each.
Common culprits are:
- Links in a tight list, such as a footer or a row of small icons.
- Menu items squeezed close together.
- Small text links placed right next to each other.
Check 2: can you read it without pinching?
Hold the phone at a normal reading distance, ideally outdoors or near a window, not in your dimly lit office. Can you read the body text easily? Is there enough contrast between the text and the background? Does grey text on a pale background fade out in daylight?
The W3C Web Accessibility Initiative lists colour contrast and zoom among its quick checks. Try zooming in with your fingers: the page should still work and stay readable. The W3C is clear that these checks are "designed to be quick and easy, rather than exhaustive", so treat them as a first pass, not a full accessibility audit.
Check 3: does the form work with a thumb?
If your ad sends people to an enquiry or booking form, fill it in yourself on your phone, start to finish. Notice:
- Does every field have a clear label that stays visible while you type?
- Is it obvious which fields are required?
- Does the keyboard cover the field you are typing in?
- Do you need more fields than you really need to ask for a first enquiry?
- Does the submit button work, and do you see a clear confirmation afterwards?
The W3C quick checks also list form labels and required fields, so this is not only a matter of taste. A form that is awkward on a phone is one of the easiest places to lose someone who was ready to get in touch.
Check 4: is calling you easy?
For many local businesses, a phone call is the enquiry. From a phone, your number should be something a visitor can tap to start a call, not text they have to remember and retype. Check that your number appears near the top of the page and on your contact page, and that tapping it opens the phone's dialler with the right number.
The same goes for other contact routes you offer, such as email, a map link or a messaging link. Tap each one and check it does what a visitor would expect.
Check 5: does the page load acceptably?
Speed is covered in more depth in our separate article on page speed, but it belongs on this list. Google's "good" thresholds for Core Web Vitals, measured at the 75th percentile of page loads, are:
- Largest Contentful Paint (how quickly the main content appears): within 2.5 seconds.
- Interaction to Next Paint (how quickly the page responds to a tap): 200 milliseconds or less.
- Cumulative Layout Shift (how much the page jumps around as it loads): 0.1 or less.
Google says Core Web Vitals are used by its ranking systems. It also says good scores do not guarantee top rankings, and that relevance still comes first. So treat these figures as a way to make the visit better for people, not as a trick for climbing results.
While loading, watch for the page jumping as images arrive. Nothing is more frustrating than reaching for a button just as it moves.
How to test properly
Browser tools can show a phone-shaped window on your computer. In Chrome, this is called device mode in DevTools. It is useful for a quick look, but Chrome's own documentation says it is only an approximation of a real phone, and advises: "When in doubt, your best bet is to actually run your page on a mobile device."
So do the final test on a real phone, and ideally more than one:
- 1Use your own phone, then borrow one with a different screen size or from a different maker.
- 2Test on mobile data as well as Wi-Fi, since many of your visitors will not be on your office connection.
- 3Follow the whole route a customer would take: click the ad, land on the page, find what they need and make contact.
- 4Ask someone who does not know your site to do the same while you watch. Note where they hesitate.
Before you switch the ads on
Write down what you found, fix the issues in order of how likely they are to lose an enquiry, and test again on a real phone. Forms, contact buttons and tap targets usually deserve attention first, because they sit right at the moment someone decides to get in touch.
Fixing these things does not guarantee more enquiries, and results vary from business to business. What it does is make sure that when you pay for someone's visit, the site is ready for them. If you would like help with a mobile-friendly rebuild or fixes, get in touch and we will talk through what your site needs.
Continue Reading
Discover more insights and stories


