Mobile-friendly website checklist for small businesses (2026)

It's 7:40 on a February morning and a homeowner in Warrington is standing in a cold basement holding a phone in one hand and a flashlight in the other. They search "furnace repair near me," tap your site and wait. If the phone number isn't one thumb-tap away within a few seconds, they hit back and call the next company.

That's what "mobile-friendly" means for a local business: the person in the basement can find you, trust you and call you, one-handed, on a weak signal. Mobile site optimization is the work that gets them there: a fast page, a layout that fits the screen, buttons big enough for a thumb and forms that don't fight back. Here's the checklist we use, with Google's current numbers and how to test each item yourself.

Why mobile matters more than desktop for local businesses

Google now crawls and indexes sites with its smartphone crawler. Its Search Central blog said that after July 5, 2024, the remaining sites still crawled with the desktop crawler would be crawled with only the smartphone one. In plain English: the mobile version of your site is the version Google judges.

Your customers are mostly on phones too, especially for urgent searches. Check your own analytics to see the split; for many service businesses, phones are the majority.

Your platform makes a difference, but less than people think. Hosted builders such as Wix and Squarespace manage much of the speed work for you, while a WordPress site is only as fast as its theme, plugins and host. Our Wix vs Squarespace vs WordPress comparison has the field data. Whatever you're on, the checklist below applies.

Contact and calls

• ✓ Phone number at the top of every page, visible without scrolling.
• ✓ Tap-to-call works. The number is a real link (tel:), not an image or plain text. Tap it on your phone and confirm the dialer opens with the right number.
• ✓ One main action per screen. "Call now" or "Book online," not five competing buttons.
• ✓ Text option if you take texts. Many people would rather text than call from a job site or an office.
• ✓ Hours and service area are easy to find, since "are they open?" and "do they come to me?" are the first two questions.

Buttons and tap targets

People tap with thumbs, not a mouse pointer. Small links packed together cause mis-taps and frustration.

• ✓ Buttons are large. WCAG 2.2 sets a minimum target size of 24 by 24 CSS pixels at level AA and recommends 44 by 44 at level AAA. For your main buttons, aim for 44 pixels tall or more.
• ✓ Space between links, especially in menus and footers, so a thumb doesn't hit two at once.
• ✓ Main buttons sit in easy thumb reach, in the content, not crammed into a corner.
• ✓ Menu button is labeled. A "Menu" label next to the three-line icon helps people who don't recognize the icon.

Text and readability

• ✓ Body text is at least 16px. Smaller text forces people to pinch and zoom. On iPhones, form fields with text smaller than 16px also make the page zoom in when tapped, which is disorienting.
• ✓ Short paragraphs. Two to four lines on a phone screen is plenty.
• ✓ Strong contrast. Light gray text on white looks elegant on a big monitor and disappears in sunlight on a phone. WCAG asks for a contrast ratio of at least 4.5 to 1 for normal text.
• ✓ No sideways scrolling. Every page should fit the screen width, including tables and images.
• ✓ The viewport tag is set so the page scales to the device. Most modern themes and builders handle this; old custom sites sometimes don't.

Images and page weight

Images are usually the heaviest thing on a small business site, and the easiest thing to fix.

• ✓ Photos are resized to the size they're displayed at. A 4,000-pixel photo straight off a phone has no business on a 400-pixel-wide screen.
• ✓ Modern formats such as WebP or AVIF, which are much smaller than JPEG at similar quality.
• ✓ Responsive images, so phones download a smaller file than desktops.
• ✓ Lazy-loading below the fold, but never on the main image at the top of the page. Lazy-loading the first image delays the part of the page Google measures for loading speed.
• ✓ No autoplay background video on mobile. It eats data and battery and rarely helps someone call you.
• ✓ Fewer third-party scripts. Chat widgets, heatmaps, old tracking codes and social feeds all add weight. Remove anything nobody uses.

Core Web Vitals: Google's current thresholds

Core Web Vitals are Google's three measurements of real-world page experience. Here are the thresholds Google publishes on web.dev (checked October 2026):

Metric	What it measures	Good	Needs improvement	Poor
Largest Contentful Paint (LCP)	How quickly the main content appears	2.5 seconds or less	2.5 to 4 seconds	Over 4 seconds
Interaction to Next Paint (INP)	How quickly the page responds to taps	200 milliseconds or less	200 to 500 milliseconds	Over 500 milliseconds
Cumulative Layout Shift (CLS)	How much the layout jumps around while loading	0.1 or less	0.1 to 0.25	Over 0.25

Source: web.dev, "How the Core Web Vitals metrics thresholds were defined." Google assesses each metric at the 75th percentile of real page visits.

INP replaced the older First Input Delay metric in March 2024, so if an old report mentions FID, it's out of date.

What usually fixes each one

• Slow LCP: an oversized hero image, slow hosting, or a page builder loading too much code before the content. Compress the top image, improve hosting, cut unused plugins.
• Slow INP: heavy JavaScript, often from page builders, sliders, chat widgets and tracking tags. Remove what you don't need.
• High CLS: images without set dimensions, ads or banners that push content down, fonts that swap late, and headers that appear after the page loads.

Forms on mobile

A quote request form is where mobile visitors most often give up.

• ✓ Ask for less. Name, phone, what you need, and maybe town or zip. You can get the rest on the call.
• ✓ Right keyboard for each field. Phone fields bring up the number pad and email fields bring up the @ key when they're set up with the right input types.
• ✓ Autofill turned on, so the phone can fill in name, email and address.
• ✓ Labels stay visible. Placeholder text that disappears when someone starts typing leaves them guessing what the field was.
• ✓ Big, clear submit button with a specific label ("Request my quote," not "Submit").
• ✓ Clear confirmation after sending, and a test submission each month to make sure the emails still arrive.
• ✓ Spam protection that doesn't punish humans. Puzzles that are hard to solve on a small screen cost you real leads.

Sticky headers and pop-ups: the common pitfalls

A sticky header with a phone button can be great on mobile. Done badly, it eats the screen.

• ✓ Keep it short. If the sticky header takes up a quarter of a phone screen, it's too tall. Logo, phone button, menu button; that's it.
• ✓ Don't let it cover headings. When someone taps a link to a section on the same page, a sticky header can hide the heading they jumped to. Your developer can fix this with a scroll offset.
• ✓ No late-loading banners that shove the page down after it appears; that's a layout shift visitors feel and Google measures.
• ✓ Pop-ups wait or stay small. A full-screen pop-up the moment the page loads is the fastest way to lose someone. Google's guidance on page experience specifically calls out intrusive interstitials.
• ✓ Cookie and chat banners don't cover the call button.

How to test your site on mobile

You don't need special tools to find most problems.

1. Use real phones. Your own, plus an older Android phone if you can borrow one. Turn off Wi-Fi and test on cellular data. Try it one-handed.
2. Do the three-task test. Can you find the phone number, find your hours and send the contact form, each within about ten seconds?
3. Run PageSpeed Insights. Enter your home page and a main service page. The top section shows field data from real Chrome users over the previous 28 days (if your site has enough traffic); the lower section is a lab test from one simulated phone. Field data is what counts.
4. Use Lighthouse in Chrome's developer tools for a detailed lab report. Google retired its old Mobile-Friendly Test in December 2023 and points people here instead.
5. Check Search Console under Experience > Core Web Vitals to see which groups of pages pass or fail on mobile.
6. Watch someone else use it. Hand your phone to a friend, ask them to request a quote, and don't help. Where they hesitate is where customers hesitate.

When to fix and when to rebuild

If the site fails on a few items, such as heavy images, a tiny phone number or a long form, those are usually quick fixes. If the theme itself is slow, the layout breaks on phones or the site is built on a page builder that loads a mountain of code, patching it can cost more than starting over.

A useful rule of thumb: if the fixes would touch most pages and the site is more than five years old, get a quote for both. Our website redesign service rebuilds sites mobile-first while keeping the pages and addresses that already bring in calls, and our website design service covers new builds. If you're hiring someone, our questions to ask a web designer include how they test speed on phones, and our guide to website redesign costs explains what to budget.

What to do next

Do the three-task test on your own phone today; it takes two minutes. If anything fails, or you want the numbers behind it, our free visibility audit checks your mobile speed, Core Web Vitals and how your site shows up in local searches, and lists the fixes in order.