Website speed on phones: A plain-English fix list for small businesses

Most customers meet your website on a phone, on mobile data. Here's how to measure its speed for free and the six fixes that usually matter most.

An ink drawing of a phone beside a stopwatch, with speed lines and a small lightning bolt.

A parent on the train taps your tuition centre's link from a Facebook group. The screen stays white, then a huge banner photo loads, then the page jumps as a pop-up appears, and by Bishan they've gone back to the group.

Google's Core Web Vitals put numbers on that experience. A good page shows its main content within 2.5 seconds, responds to a tap within 200 milliseconds and doesn't shift around, with a layout shift score of 0.1 or less. Google suggests measuring at the 75th percentile of visits, so most of your visitors get that experience, not just the lucky ones on Wi-Fi.

The quick version:

  • Test your homepage and one service page on PageSpeed Insights.
  • Shrink the big images first, because they're usually the problem.
  • Remove what you don't need: pop-ups, sliders and old plug-ins.
  • Check again on your own phone, on mobile data.

A slow page loses people who were ready to book

Customers who tap through from Google Maps, an Instagram bio or a WhatsApp link usually want one thing: a price, a time or a way to book. They're often on mobile data, between other things. A page that takes a few seconds too long, or jumps as they try to tap, gives them a reason to go back and try the next result.

Fix speed because customers notice it, not to chase a perfect score.

Measure first, for free, in two minutes

Open PageSpeed Insights, paste your website address and look at the mobile result. If your site has enough visitors, the top section shows real-world data from Chrome users. Below it is a lab test with a list of what slowed the page down. Run it on your homepage and on the page customers book from.

Don't chase a perfect score. Look at the three Core Web Vitals and whether each is green, amber or red, and fix the reds first. Write the numbers down before you change anything, so you can see what each fix did.

1. Big photos are the usual culprit

A photo straight off a phone can be 4,000 pixels wide and several megabytes. On a phone screen it needs a fraction of that. Resize images to the width they're shown at, around 1,200 to 1,600 pixels for a full-width banner, and save them in a modern format such as WebP. Most website builders do this if you upload a sensibly sized file.

2. The first screen should load first

Whatever appears at the top of the page, often a banner photo or headline, is what the 2.5-second measure watches. Keep it simple: one image, not a slider of five, and a headline in text rather than words baked into the picture.

3. Pop-ups and late banners make the page jump

A cookie bar, a newsletter pop-up or a chat bubble that appears after the page loads pushes everything down, which is exactly what the layout shift measure counts. Keep only the ones you need, and give images fixed sizes so the space is reserved before they arrive.

4. Every plug-in and widget has a cost

Old booking widgets, three analytics tags, an Instagram feed and a review carousel each add code a phone has to download and run. List what's on your site, ask what each one does for customers, and remove what nobody would miss. A slow tap response is usually too much of this code.

5. Fonts and videos can wait

Two font families are plenty. Background videos on the homepage look good on a laptop and cost a lot on mobile data; a still photo does the job. If you need a video, put it lower down the page and let people tap to play.

6. Your website builder may already have the settings

If your site runs on a builder such as Wix, Squarespace or Shopify, many of these fixes are settings rather than code. Look for image compression, lazy loading for images further down the page, and the option to switch off apps you no longer use. The builder's help pages show where each one lives.

On WordPress, the usual culprits are a heavy theme and too many plug-ins. Before adding a speed plug-in, try removing three you don't need.

7. Test the way your customers browse

After the fixes, open the site on your own phone, with Wi-Fi off, somewhere busy. Time how long it takes to see your prices and the booking button. That's the test that matters, and it takes a minute. Our Google Maps and website checklist covers what should be on that first screen.

Frequently asked questions

How fast should a small business website load on a phone?

Google's Core Web Vitals say the main content should appear within 2.5 seconds, the page should respond to a tap within 200 milliseconds, and the layout shift score should be 0.1 or less, for at least 75% of visits.

How do I test my website speed for free?

Use Google's PageSpeed Insights. Paste your address and check the mobile result, which shows real-world data when your site has enough visitors and a lab test listing what slowed the page.

What usually slows down a small business website?

Oversized photos, sliders, pop-ups that appear late, and too many plug-ins or widgets. Resizing images is usually the quickest win.

How Furoki can help

Furoki Marco includes speed on phones in its check of how Google, Google Maps and AI assistants see your business, alongside page titles, local presence and AI search readiness. You get a score out of 100 and the fixes ranked by impact, free, with no sign-up, in about two minutes.

Run a free Marco audit to see whether speed is the first thing to fix on your site.

Keep reading