Short answer
- Test your site at PageSpeed Insights and look at the mobile results first.
- Google measures loading, responsiveness and visual stability through Core Web Vitals: LCP, INP and CLS.
- For most small business sites the biggest wins are oversized images, too many plugins or scripts, and slow hosting.
- Speed helps, but it doesn't replace relevance. A fast page that doesn't answer the search still won't rank or convert.
Why speed matters for a local business
Think about how people find you: on a phone, often on mobile data, comparing two or three businesses from the map results. If your page shows a blank screen for a few seconds, the competitor's page that loaded first gets the call. You never see that lost customer in any report; they simply never arrive.
Speed also matters to Google. Its documentation on page experience says its core ranking systems look at signals like Core Web Vitals, while being clear that great, relevant content still comes first. So think of speed as removing a handicap, not as a ranking shortcut.
If you run ads, speed matters twice: you pay for every click, including the people who leave before the page loads.
How to test your site in 5 minutes
- Open PageSpeed Insights and paste your homepage address.
- Look at the Mobile tab first. Most local customers are on phones, and mobile scores are usually the lower ones.
- Check the top section ("Discover what your real users are experiencing"). If your site has enough visitors, this shows real-world data from Chrome users. Small sites often don't have enough traffic yet, which is normal.
- Then look at the lab test below it and its list of "Opportunities" and "Diagnostics". These point at the specific files slowing you down.
- Test your most important page too, not just the homepage: your main service page or the page your ads point to.
If you've set up Google Search Console, its Core Web Vitals report groups pages that share the same problem, which is handy once your site has more pages and visitors.
Core Web Vitals in plain English
Google's web.dev guide defines three Core Web Vitals and the thresholds for a "good" experience:
| Metric | What it means for your visitor | Good |
|---|---|---|
| LCP: Largest Contentful Paint | How long until the main content (usually your hero image or headline) appears | 2.5 seconds or less |
| INP: Interaction to Next Paint | How quickly the page reacts when someone taps a button or opens a menu | 200 milliseconds or less |
| CLS: Cumulative Layout Shift | How much things jump around while loading, like a button moving just as you tap it | 0.1 or less |
For a typical small business site, LCP is the one most often in trouble, usually because of one huge image at the top of the page.
The fixes that usually matter most
In rough order of how often they make the biggest difference on small business sites:
1. Resize and compress images
A photo straight from a phone can be several megabytes and thousands of pixels wide, displayed in a box a few hundred pixels wide. Resize images to the size they're shown at, compress them, and use modern formats like WebP where your platform supports it. This alone often fixes LCP.
2. Cut plugins, widgets and third-party scripts
Chat widgets, popups, sliders, social feeds, several tracking tags: each one adds code the phone has to download and run, which hurts loading and INP. Remove anything you don't actively use. Keep the tracking you genuinely need, like your analytics and ad conversion tags.
3. Fix layout jumps
Give images and embeds a set width and height so the page reserves space for them, and avoid banners that push content down after it loads. That's usually all CLS needs.
4. Load fonts sensibly
Use one or two font families with only the weights you need. Every extra weight is another file.
5. Check your hosting
If the page takes a long time before anything starts downloading, the server may be the bottleneck. Very cheap shared hosting is a common cause. Good hosting with a CDN (content delivery network) helps, especially when your visitors are far from the server.
6. Don't autoplay big videos at the top
A background video looks impressive and is often the heaviest thing on the page. A strong photo with a play button usually serves visitors better.
If you use Wix, Squarespace or WordPress
| Platform | What you control | Where to start |
|---|---|---|
| Wix / Squarespace | Images, number of apps and widgets, page length, fonts | Remove unused apps, replace huge images, simplify the top section |
| WordPress | Almost everything: theme, plugins, hosting, caching | Audit plugins, use a lightweight theme, add caching and image compression, check hosting |
| Hand-built site | Everything | Images first, then scripts and fonts |
On page builders you can't change the underlying code, so focus on what goes on the page. On WordPress, the biggest problems I see are page-builder themes stacked with plugins that each load their own files.
What I do on the sites I build
Every website I build is hand-coded rather than made with a heavy page builder, with images resized and compressed, only the fonts it needs, no unnecessary scripts, and sizes set on images so nothing jumps. If your current site is slow and you're not sure why, a free audit includes a look at speed alongside your Google profile and ads, and I'll tell you whether it's fixable or worth replacing. Ongoing technical fixes are also part of SEO.