A local business website is mobile-optimized when the mobile version holds the same content as the desktop one, loads its main content within 2.5 seconds, responds to taps within 200 milliseconds, and keeps its layout still. Those are Google's published "good" targets for Core Web Vitals, measured at the 75th percentile of page loads. Add a tap-to-call button and you have the core of a mobile checklist.
This guide turns those rules into a checklist for a shop, salon or studio site. All figures come from the sources at the end, and worked examples are labelled as assumptions.
→
LCP target (loading)
web.dev
→
INP target (responsiveness)
web.dev
→
CLS target (visual stability)
web.dev
→
Percentile of page loads measured
web.dev
See Sources at the end of the article. Cards marked Assumption are examples, not results.
What Do Google's Mobile Rules Require?
Google indexes the mobile version. Its mobile-first indexing guide says only the content shown on the mobile site is used for indexing, so anything missing from mobile may not be seen by Google at all.
Google recommends responsive web design, because it is the easiest pattern to implement and maintain, and because content and metadata are then the same on mobile and desktop.
If your site uses separate mobile pages or dynamic serving, check that the following match across versions:
- Main content and headings
- Structured data
- Title elements and meta descriptions
- Image alt text
- Robots meta tags
Google also says not to lazy-load primary content upon user interaction. Hiding your services list behind a tap-to-expand panel that loads on demand is the kind of thing to test.
What Are the Core Web Vitals Targets?
web.dev defines three metrics. Largest Contentful Paint (LCP) measures loading, and should occur within 2.5 seconds. Interaction to Next Paint (INP) measures responsiveness, and should be 200 milliseconds or less. Cumulative Layout Shift (CLS) measures visual stability, and should be 0.1 or less.
A page passes when all three meet their targets at the 75th percentile, split by mobile and desktop. In practice that means three out of four visits should meet the target, not just the fast ones.
You can read your own results in Google's PageSpeed Insights or in the Core Web Vitals report in Search Console. Neither Google nor web.dev publishes an average score for local business sites, so compare against the targets, not against a competitor.
How Do You Speed Up a Local Site on Mobile?
For most small sites the slow part is the largest image or text block at the top of the page. web.dev splits LCP into four parts: time to first byte, resource load delay, resource load duration and element render delay. Its advice for each is concrete:
- Do not lazy-load the main image. Make it discoverable in the initial HTML and give it high fetch priority, but on only one or two images.
- Shrink the file. Use modern formats, compression and correctly sized images, and serve them from a CDN near visitors.
- Cut redirects and slow server work. Both add to time to first byte.
- Keep render-blocking code small. Avoid synchronous scripts in the head.
web.dev says its target shares per subpart are guidelines to compare against each other, not millisecond budgets.
Does Speed Change Conversions?
One large study suggests it can, with limits. Deloitte and the agency 55, commissioned by Google, tracked 37 European and American brand sites across more than 30 million user sessions for 30 days at the end of 2019. A 0.1 second mobile speed improvement was linked to an 8.4% rise in retail conversion rate and 9.2% more spend per retail visitor.
Those are retail and travel brands, and the data is from 2019. The study did not cover local service sites, so do not expect the same percentage for a booking page. It does show that small speed gains were measurable at scale. For related reading, see our
mobile-first website design guide.
What Should Be on a Mobile Page for a Local Business?
Visitors on a phone usually want one of three things: to call, to get directions, or to check hours. Put those within the first screen.
- A tap-to-call link. Use the tel: scheme in a link, as MDN documents, for example a link whose address starts with tel: followed by the number. Cellular devices autodial it.
- Address and hours as text. Plain text is readable by Google and by the visitor. Our Google Business Profile checklist covers keeping them identical to your profile.
- A single main action. One booking or contact button, not five competing choices.
Google Business Profile reports calls as clicks on the call button on your profile, and website clicks as clicks on the website link. Compare those numbers with your site's own call-button clicks to see where phone traffic starts. Our analytics and tracking guide shows how to set that up.
How Do You Test Your Site on a Phone?
Run through this list on a real phone, on mobile data, not only on office wifi:
- Open the home page and time how long until the main image and headline show.
- Tap the call button and confirm your dialer opens with the right number.
- Scroll the page and watch for content that jumps as images load.
- Open the booking or contact form and complete it.
- Compare the services, prices and hours with the desktop page.
Then run the page URL through PageSpeed Insights and note the three vital metrics. Retest after every design change or new plugin.
All inputs below are assumptions, not benchmarks.
| Input | Before | After |
|---|
| Monthly mobile visits | 800 | 800 |
| Share of visits tapping call | 2% | 4% |
| Calls from the site | 16 | 32 |
| Calls that become a booking | 25% | 25% |
| Bookings from the site | 4 | 8 |
| Average booking value | $60 | $60 |
| Added revenue per month | | $240 |
The extra 16 calls at a 25% booking rate give 4 more bookings, and 4 x $60 is $240. If your numbers are half as good, the gain halves too. Measure your own call-tap rate for a month before and after a change.
Open your home page on your phone, tap the phone number, and check that it dials. If it does not, fix that before anything else.
FAQ
What are the Core Web Vitals thresholds?
LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less, at the 75th percentile of page loads (web.dev).
Does Google use my mobile site for ranking?
Google says only the content shown on the mobile site is used for indexing. Make sure your mobile pages hold the same content as desktop.
Do I need a separate mobile site?
No. Google recommends responsive web design as the easiest pattern to implement and maintain.
Does a faster site mean more bookings?
A Google-commissioned study linked a 0.1 second mobile speed gain to an 8.4% higher retail conversion rate. That was for retail and travel brands in 2019, so treat it as direction, not a forecast.
Use a link with the tel: scheme and your number. Phones autodial it, per MDN.
Sources
Need a site that works on phones? See our
Website service or
book a free audit.
Free for local businesses
Want this applied to your business?
I'll review your Google presence, local SEO, and ad accounts — and send you a specific action plan within 48 hours. No pitch, no pressure.