Getting more calls · 5 min read · October 20, 2026
How fast should your website load on a phone?
On a phone, the main content of your page should appear within 2.5 seconds, the page should respond to a tap within 200 milliseconds, and nothing should jump around while it loads. Those are Google's Core Web Vitals targets, and a PageSpeed Insights mobile score of 90 or higher means your page did well in Google's own lab test.
That's the short answer. Below is what those numbers mean for a plumber, a contractor, a shop or a restaurant, why the score moves around, and what usually slows a small business site down.
Google's three numbers
Google measures how a page feels to a real visitor with three metrics, called Core Web Vitals. Here they are with Google's lines for good and poor, from the PageSpeed Insights documentation:
- Largest Contentful Paint (LCP): when the main content shows up. Good is 2.5 seconds or less. Over 4 seconds is poor. On your site, that's the moment the headline and the big photo of your work appear.
- Interaction to Next Paint (INP): how fast the page reacts. Good is 200 milliseconds or less. Over 500 milliseconds is poor. That's the gap between a visitor tapping "Call now" and something happening.
- Cumulative Layout Shift (CLS): how much things jump. Good is 0.1 or less. Over 0.25 is poor. That's the "Call" button sliding down as a banner loads, so the visitor taps "Directions" instead.
Google's guide to Web Vitals adds one detail that matters: to pass, a page should hit these targets for at least 75% of visits, measured separately on phones and on computers. A site that's fast on your office Wi-Fi and slow on a customer's phone in a parking lot doesn't pass.
Why this matters for a local business
Your customers are often in a hurry. Someone with a burst pipe, someone whose car won't start, someone picking a place for dinner while their friends wait. A page that shows nothing for five seconds gives them time to tap back and try the next result.
Google also cares. Its Search documentation says it highly recommends that site owners achieve good Core Web Vitals for success with Search, and that this, along with other page experience aspects, aligns with what its core ranking systems seek to reward (Google Search Central). That doesn't make speed the only thing that counts, but it does count.
What the PageSpeed mobile score means
When you test a page in PageSpeed Insights, the big number at the top is a lab score from 0 to 100. Google's documentation says:
- 90 or above is good.
- 50 to 89 needs improvement.
- Below 50 is poor.
It's a lab test, not real visitors. Google loads your page once on a simulated mid-range phone over a mobile network and times what happens. The score comes from several of those timings: when the first thing appears, when the main content appears, how fast the page fills in, how long it's frozen while scripts run, and how much the layout shifts. There's no real finger tapping in a lab, so the test can't measure INP directly. It measures how long the page is frozen instead, which Google's Web Vitals guide calls a lab proxy for INP.
Two things confuse people about the score.
It moves between runs. Google's own FAQ says variability comes from things like network availability and the hardware the test runs on. Run it two or three times before you worry about a few points.
The real-visitor section may be empty. Below the score, PageSpeed can show data from real Chrome users over the previous 28 days. A site with few visits often doesn't have enough data for that section, so the lab score is all you get. That's normal for a small local site.
What slows small business sites down
These are the usual suspects:
- Photos straight from the phone or camera, uploaded at full size. A photo meant for a phone screen doesn't need to be as big as the original file.
- Image sliders at the top of the page that load five large photos when a visitor sees one.
- Heavy page builders and themes that load a lot of code for features the site doesn't use.
- Add-ons stacked up over the years: chat widgets, review widgets, embedded social feeds, tracking pixels, a background video.
- Slow hosting, where the server takes a long time just to start sending the page.
- Lots of web fonts, each one a separate download.
None of these are unusual. The fix is usually removing things, not adding them.
Our own number
We hold our work to the same test. On October 18, 2026, we ran Google's mobile speed test on 11 of our live client sites. The median score was 89, with a range of 75 to 96. Those sites belong to businesses in Lithuania and Sweden, and they include a law firm, a flower stand and online stores, so they're real working sites, not empty test pages.
A median of 89 sits just under Google's line for good: some of those sites clear 90, some don't. You can open any of them on your phone and run the same test.
How to check your own site
The quickest way is our free website checker. It runs Google's mobile test and translates it into plain English: your speed score on a phone, the first thing on screen (Google's target is 1.8 seconds or less), how long the page is frozen while loading, when the main content shows on a phone, and how much the layout jumps. It also checks the things that decide whether a fast page actually gets calls, like a tap-to-call link and a quote form.
You can also try it by hand. Turn off Wi-Fi on your phone, open your site in a private tab, and count the seconds until you can read the headline and tap the number.
What to fix first
- Shrink and compress the photos, starting with the one at the top of the page.
- Replace a slider with one strong photo.
- Remove widgets and scripts nobody uses.
- Make sure nothing loads in above your content and pushes it down.
- If the theme or builder is the problem, consider a rebuild instead of more patches.
Speed is one of several reasons a site stays quiet. The others are in why your website doesn't get calls.
If you'd rather start with a site that's built for phones first, ask for a free preview. After a 15 minute call, we build the first version of your site free in 2 days, and you can test it on your own phone before you decide. Get your free preview.