All guides
Education 19 min read Updated

Mobile: making your website work on phones

We reviewed 100 small-business websites. Small or crowded tap targets failed on 64 of 85 evaluated sites; 15 were unchecked. Here is what that means and how to check your own phone experience.

We reviewed mobile checks for 100 small-business sites
75%

of evaluated sites failed the tap-target check.

A site can look fine on a laptop and still be awkward on a phone. We reviewed 100 small-business websites. The most common evaluated mobile failure was small or crowded tap targets: 64 of 85 evaluated sites, about 75%. Start with the controls a visitor uses to call, book or send a message.

How we measured this

We reviewed 100 small-business websites against a list of mobile tests. Things like whether buttons are big enough to tap, whether you can tap the phone number to call, whether images fit the screen, and whether the page resizes itself to fit a phone.

The findings come from a June 25, 2026 batch of 103 audit records for 100 distinct website addresses. We use the latest record for each address, against checklist version 2026-06-24l. Percentages count passes plus failures for that check. Not-applicable and unchecked results stay out of the denominator. Some checks use AI-assisted judgments; these are historical findings, not a representative survey of every small business.

Across the mobile category, 175 of 717 evaluated checks failed, or 24.4%. Ten sites had no recorded mobile failures and 20 had three or more. The mean site pass rate was 73.1%. All 100 mobile-speed checks were unchecked, so this batch tells us nothing about measured load speed. The diagrams below illustrate the issues.

See the counts behind the findings

Failed / evaluated means failures divided by passes plus failures. On a small screen, scroll the table sideways to see all columns.

June 25, 2026 audit counts
CheckFailed / evaluatedFailure rateNot applicableUnchecked
Site is fully mobile responsive13 / 10013.0%00
No horizontal scrolling on mobile3 / 903.3%010
Font size does not require zooming on mobile2 / 862.3%014
Tap targets are large enough — buttons easy to press64 / 8575.3%015
Images do not overflow on mobile35 / 9038.9%010
Forms are easy to fill out on mobile2 / 513.9%481
Mobile page speed is acceptable0 / 0Not measured0100
Click to call phone number works on mobile31 / 9433.0%60
Form fields use mobile-friendly input types (tel/email)25 / 7931.6%210
A primary action stays in mobile thumb reach (sticky CTA)0 / 420.0%4810
73%
mean site pass rate among evaluated mobile checks
24%
of evaluated mobile checks failed (175 of 717)
20%
of sites had three or more recorded mobile failures

Two real reports

What the audits look like

reddoorgrill.com Auditing Audited
Score

Red Door Grill

D

Falling Behind

94 passed 41 to fix 21 N/A
See the full report
shopandsavemarket.com Auditing Audited
Score

Shop and Save Market

C

Falling Behind

105 passed 37 to fix 15 N/A
See the full report

The big one: buttons and links you can actually tap

If you fix only one thing after reading this, make it this. By a wide margin, the most common mobile problem we found was buttons and links too small or too crowded for a real thumb on a real phone.

Tap targets are large enough and easy to press

64 of 85 evaluated sites failed the tap-target check, or 75.3%. Fifteen were unchecked. The issue was buttons, links or menu controls that were small or close together. It does not mean 75 of all 100 sites failed.

Too small to tap
Thumb-friendly
Illustrative target sizes. A 44 × 44 CSS-pixel control is a practical design starting point, not a measurement of a fingertip or the WCAG AA minimum. Check spacing and the actual hit area.
Sites with tap targets too small or crowded75%
The most common evaluated mobile failure: 64 of 85 sites failed, with fifteen unchecked. Check whether this issue affects your main action.

A tap target is the area that responds when you touch a control. The visible icon can be small while the actual target is larger. Check both the target and the space around it, especially menu, close, call and booking controls.

Why it matters: This is the most direct way there is to lose a ready-to-act customer. Someone wants to call you, book a table, or open your menu, and the button keeps dodging their thumb or they keep hitting the wrong link. People do not email you to complain about this. They just give up and try the next business. Every mis-tap is a small invitation to leave.

How to fix it: Enlarge important controls and leave enough space between them. A 44 × 44 CSS-pixel target is a useful design starting point for a primary button. It is not the WCAG 2.2 AA minimum: that criterion uses 24 × 24 CSS pixels, with spacing and other exceptions. Check the actual rendered control. In Frontpage, ask for the size and spacing change, then try it on your phone.

Free site rebuild

See what your site needs

Submit your website URL and we will rebuild your site for free within 48 hours, then reach out when it is ready.

Rebuild my site free

A phone check you can repeat

  1. Open your home page on a real phone. Find a service and use its main action without zooming.
  2. Open and close the menu, then try the call or booking link. Confirm the destination.
  3. Scroll each key page and look for clipped content or sideways movement. Recheck in landscape.
  4. Fill a test form, check validation and confirm receipt. A success message alone does not prove delivery.
  5. Measure load performance separately if needed. This audit batch left all 100 mobile-speed checks unchecked.

Illustrative CSS for a primary action

.primary-action {
  display: inline-flex;
  align-items: center;
  justify-content: center;
  min-width: 44px;
  min-height: 44px;
  padding-inline: 16px;
}

This is a design example, not a complete accessibility check. The W3C target-size guidance explains the AA rule and exceptions. Google’s mobile-first indexing guidance explains which content it uses.

Things that should just fit the screen

A phone screen is small and narrow. A surprising number of sites still behave as though every visitor is on a wide computer monitor. This group of tests is all about content simply fitting the screen the way a customer expects.

Site is fully mobile responsive

13% of websites failed this test. "Responsive" means the website automatically rearranges itself to fit whatever screen it is on, shrinking and stacking things so a phone gets a phone-shaped layout instead of a tiny shrunken copy of the desktop page.

Not responsive
Responsive
Illustrative layouts. A viewport setting is one part of responsive design; layout rules and fixed-width content also need checking.
Sites that are not fully mobile responsive13%

A missing viewport setting is one possible cause, but layout rules, fixed-width content and embeds can cause trouble too. Check the actual page at narrow widths rather than assuming one line of code explains every failure.

Why it matters: This is the foundation everything else sits on. If the site is not responsive, customers get tiny text, sideways scrolling, and buttons they have to pinch and zoom to reach. It also works against you with Google, which judges your site by its phone version first. A non-responsive site looks dated and untrustworthy at the very moment a customer is deciding whether you are a real, current business.

How to fix it: Check the viewport setting and then inspect the layout on a phone. Text and columns should reflow without hiding useful content. In Frontpage, review the mobile draft and name any section that overlaps or stays too wide. A new template or generated page still needs a real check.

Images do not overflow on mobile

35 of 90 evaluated sites failed the image-overflow check, about 39%. Ten were unchecked. Look for an image that extends past the screen and makes the page wider than it should be.

Spills off the edge
Fits the screen
An oversized image can widen a page or be clipped by its container. Check the actual page for both hidden content and sideways scrolling.
Sites with an image that overflows on mobile39%

Why it matters: When an image spills off the side, it usually drags the rest of the page with it. Text gets cut off, the page can be shoved sideways, and the whole thing feels broken. A customer trying to read your hours or see your prices instead gets a lopsided mess. It is the kind of small glitch that quietly tells people you are not paying attention, which is the last impression you want while someone is deciding whether to trust you with their money.

How to fix it: Images should be set never to grow wider than the screen they are on. On most website builders this is automatic, but it breaks when an image is added in an unusual way or pasted in at a fixed, oversized width. Open every important page on your own phone and scroll top to bottom, looking for anything that sticks out past the edge. The usual culprits are big banner photos, logos, and images inside blog posts or galleries. Re-adding the image through your builder's normal image tool, rather than a custom embed, almost always fixes it.

No horizontal scrolling on mobile

3 of 90 evaluated sites failed the horizontal-scroll check, about 3%. Ten were unchecked. Overflowing images and sideways page scrolling are related checks, but their recorded outcomes differ. Test the page itself as well as each image.

Why it matters: A page that drifts sideways feels broken even when nothing else is wrong. People expect to scroll straight down with their thumb. When the page also slides left and right, content hides off the edges and reading becomes a chore.

How to fix it: Almost everyone already passes this, so if you are in the small group that does not, the cause is nearly always the same as overflowing images: one element, usually a photo, a table, or an embedded map or video, that is too wide for the screen. Find the page that slides sideways, then find the one thing on it that sticks out, and make it fit. Fixing the overflowing images above will often clear this up at the same time.

Font size does not require zooming on mobile

2 of 86 evaluated sites failed the text-size check, about 2%. Fourteen were unchecked. Check the smallest useful text on your own phone, including hours, price notes and form instructions.

Why it matters: Text that is too small to read is an instant exit. Nobody zooms in to read your hours or your menu, they leave. The fact that nearly everyone gets this right is good news, and it is worth protecting.

How to fix it: Since you very likely already pass, the main job is to keep passing. When you edit your site, avoid shrinking text to squeeze more onto the screen, and never set a tiny fixed font size. If you are in the small group that failed, bump your base text up to a comfortable, readable size and check it on an actual phone, not just on your computer.

Sites that scroll sideways on a phone3%
Sites with text too small to read without zooming2%
Recorded failures: sideways scrolling, 3 of 90 evaluated sites; small text, 2 of 86. Ten and fourteen sites were unchecked, respectively. Check both issues after changing a layout.

When customers want to reach you

This is where a mobile site earns its keep. Someone on a phone is often ready to act right now. They want to call, book, or send a message in the next minute. These tests are about making that the easiest thing in the world, because friction here costs you actual customers and actual revenue.

Click to call phone number works on mobile

31 of 94 evaluated sites failed the tap-to-call check, about 33%. Six were not applicable. A real telephone link opens the phone’s dialer; a number shown only as text does not.

Just text
(555) 200-1984
Memorize it, switch to the phone app, type it in by hand.
Tap to call
One tap opens the dialer with your number ready.
For most small businesses the call is the booking, the quote, the sale. Make every number on the site a one-tap call.
Sites where the phone number is not tap-to-call33%

Why it matters: For most small businesses, a phone call is the goal. It is the booking, the quote, the order, the new customer. You have already done the hard part, getting someone interested enough to look for your number, and then a tiny technical gap makes them do extra work to reach you. Every extra step loses a few people, and the person standing on the sidewalk with your competitor one tap away is exactly the person you cannot afford to lose.

How to fix it: Make every phone number on your site a tap-to-call link. On most website builders there is a simple option to turn a phone number into a clickable "call" link, or a dedicated phone or button element that does it for you. With Frontpage you can ask for a tap-to-call bar that pins your number to the bottom of every phone screen, so the call is always one thumb-tap away. If your site was hand-built, this is a five-minute change for any web person. Do it everywhere the number appears, the header, the footer, the contact page, so that wherever a customer is when they decide to call, the next tap places the call. Then test it on your own phone by tapping the number on each page.

Form fields use mobile-friendly input types

25 of 79 evaluated sites failed the mobile-input-type check, about 32%. Twenty-one were not applicable. Use email and telephone input types so the phone can offer a suitable keyboard.

Wrong keyboard
Phone 5…
Right keyboard
Phone 555…
Tell the phone what each field expects and it brings up the right keys automatically: a number pad for phone, the @ sign for email. The visitor types less and finishes more.
Sites whose form fields use the wrong keyboard32%

This one sounds technical, but the payoff is very human. A phone keyboard can change itself to match the field you are filling in. Tap an email field and you should get a keyboard with the "@" sign ready. Tap a phone number field and you should get a big number pad. That only happens if each field is set up to expect the right kind of answer behind the scenes. When that is missing, the customer is stuck with the default keyboard and has to hunt for symbols and switch between letters and numbers.

Why it matters: Filling out a form on a phone is already a small chore. Every extra tap and every wrong keyboard makes people more likely to give up halfway through. When someone is trying to book, request a quote, or ask a question, you want that form to feel effortless. The right keyboard appearing automatically keeps people moving toward "submit" instead of toward "forget it."

How to fix it: When you build or edit a form, set each field to its proper type: email fields to email, phone fields to phone, and so on. Most form builders inside website platforms have a dropdown for exactly this when you add a field, so it is usually a matter of picking the right label rather than writing any code. After you set it, test the form on your phone and watch the keyboard change as you move from field to field.

Forms are easy to fill out on mobile

2 of 51 evaluated sites failed the mobile-form check, about 4%. Forty-eight were not applicable and one was unchecked. This finding covers the recorded form-usability check, not proof that every submission reached the business.

Check the full path on your own site: visible labels, suitable keyboards, validation, the submit button, a clear success message and receipt by the business. Use a test identity and avoid entering sensitive customer information.

Why it matters: A form is often the most convenient way for a customer to reach you, especially after hours when nobody is answering the phone. If a form is hard to use, people abandon it. If there is no form and no other obvious way to make contact, you have closed a door that a competitor left open. Most sites get this right, but it is worth confirming you are one of them.

How to fix it: If you have a form, fill it out on your own phone from start to finish, and make sure every field is easy to tap and complete and that the "submit" button actually works and tells you it went through. If you do not have any contact, booking, or order form at all, add a simple one. Even a basic "name, phone, message" form gives the after-hours customer a way in, and it pairs perfectly with the tap-to-call number for the customer who would rather just ring you.

A primary action stays in thumb reach: a clean sweep

All 42 evaluated sites passed the sticky-action check. Forty-eight were not applicable and ten were unchecked. A fixed call or booking control can help, but it is optional and should not cover text, form fields or other controls.

100%
of 42 evaluated sites passed this check. Forty-eight were not applicable and ten were unchecked. A fixed action is optional; test that it does not cover content.

Why it matters: A "sticky" button is a quietly powerful tool. Because it stays in reach no matter how far someone scrolls, your most important action ("Call," "Book," "Order") is never more than one thumb-tap away. The fact that everyone who used one got it right is a small bright spot, and a hint that this is worth considering even if you do not have it yet.

How to fix it: Nothing to fix here, so take the lesson instead. If you do not already have a sticky button for your single most important action, consider adding one. Many website builders offer a sticky button or bar as a simple option. Keep it to one clear action so it helps rather than clutters, and you give every customer a permanent, easy path to the thing you most want them to do.

Keep improving

Make a focused mobile edit

Ask Frontpage to enlarge a named control or fix a section that overflows. Check the preview on a phone and test the action before publishing. Autopilot can test eligible changes when enabled; it does not guarantee that every mobile issue stays fixed.

Open Frontpage

What to fix first

Start with the task that matters most on your site. Use the findings as a guide, then check whether the issue is actually present. Fix a broken booking link before polishing a button that already works.

Make tap targets bigger and less crowded75%
Keep every image inside the screen39%
Make the phone number tap-to-call33%
Set form fields to the right keyboard32%
Make sure the layout is responsive13%
Rounded failure rates among evaluated sites. Denominators vary and are shown in the full table above. Prioritize issues you can reproduce on your own site.
  1. Fix your tap targets. 64 of 85 evaluated sites failed (75%); fifteen were unchecked. Make buttons, links, and menu items bigger and less crowded so a real thumb can hit them. Test by handing your phone to someone and watching them use it one-handed.
  2. Make sure images fit the screen. 35 of 90 evaluated sites failed (39%). Open every page on your phone and look for anything sticking off the edge or pushing the page sideways, then make it fit.
  3. Turn your phone number into a tap-to-call link. 31 of 94 evaluated sites failed (33%). Make every number on the site tappable so one tap starts the call. This is one of the highest-payoff fixes you can make.
  4. Set your form fields to the right input types. 25 of 79 evaluated sites failed (32%). Set up email and phone fields properly so the phone shows the right keyboard automatically.
  5. Make sure your site is fully responsive. 13 of 100 sites failed (13%). If your layout does not resize itself for a phone, this is the foundation to fix before the rest.
  6. Check sideways scrolling, hard-to-read text and the forms you actually use. These were rare: sideways scrolling failed on 3 of 90 evaluated sites, text size on 2 of 86, and form usability on 2 of 51. Repeat the task after each edit; a spot-check is useful without proving every page is clear.

Why this is worth your time

Come back to that customer on the sidewalk with the phone. They are interested. They searched, they tapped your result, and for a few seconds the decision is entirely in your hands. Almost everything that decides which way they go is something you can change this week, with no developer and no advertising budget. A button big enough to press. A phone number that calls you when tapped. Images that fit. A form that is easy to fill. None of it is glamorous, and that is exactly why it works: your competitors are ignoring it too.

Walk through your site on a phone and keep a short fix list. After each change, repeat the same task. Larger controls and a layout that fits can make the page easier to use, but this study did not measure changes in rankings, calls or sales.

Free website audit

Get your score

Enter your website, email, and phone number and we'll run the audit for you. You'll get the full results, your score and exactly what to fix, delivered straight to your inbox.

Free audit · No credit card required

Historical checklist results, with evaluated, unchecked and not-applicable counts shown above. The two public example reports cover more categories than this mobile review.

Frequently asked questions

What does mobile-friendly mean for a small-business website?

A responsive layout fits the phone, important text stays readable, controls are easy to activate, and forms work with suitable keyboards and clear feedback. Google primarily uses mobile content for indexing; that does not mean a mobile checklist score determines rankings.

How big should buttons be on mobile?

A 44 × 44 CSS-pixel area is a useful starting point for primary controls. WCAG 2.2 AA target size uses 24 × 24 CSS pixels with spacing and other exceptions. Check the actual hit area and nearby controls, not only the icon.

Do I still need a separate mobile site?

No. One responsive site is the standard. Separate m-dot sites add maintenance and SEO risk. Build once so content, phone numbers, and offers stay in sync on every screen size.

How can I quickly test my site on mobile?

Open it on your own phone on cellular data, not only desktop device mode. Try the menu, the main button, the form, and the phone number. If anything requires pinch-zoom or precise tapping, fix that first.

Build it while the idea is fresh.

Describe the site you want and watch Frontpage build it live, in front of you.