Who it is for
This is for a small business owner or office manager whose website feels sluggish on a phone, or who simply has never checked. It fits if customers mention the site “takes forever,” if your contact or booking page stalls on cell data, or if a designer added a lot of photos and features and nobody has measured since. You do not need technical skills to run the test and read the results. Some fixes you can do yourself; others you hand to whoever manages the site, with a clear list.
Why this matters
Most people who look up a local business do it on a phone, often on cell data, often in a hurry. If the page is blank for several seconds, or the buttons jump around while it loads, many of them give up and call the next business in the list.
Google measures this too. It publishes three “Core Web Vitals” that describe how a page feels to real visitors, and it shows them for your site in free tools. Good numbers will not make a weak page rank on their own, but slow pages lose visitors no matter where they rank.
What you need
- Your website address and the addresses of your two or three most important pages (usually the home page, a main service page, and the contact or booking page).
- About 30 minutes to test and read results, plus time for fixes.
- Login access to your website builder or content system, or the contact details of whoever manages the site.
- Optional: access to Google Search Console for your site. If you have not set it up yet, see our guide Is Google finding your website? Set up Search Console in 30 minutes.
Steps
1. Feel it the way a customer does
- On your own phone, turn WiFi off so you are on cell data.
- Open a private or incognito browser tab, so nothing is already saved from earlier visits.
- Load your home page and count how long until you can read the main headline. Then tap through to your contact page and try the main button.
- Write down anything that annoyed you: a long blank screen, a pop-up covering everything, text that jumped as you tried to tap, a map or video that took ages.
This takes two minutes and often tells you more than any score.
2. Run a free speed test
- Open PageSpeed Insights, paste your home page address, and click Analyze.
- Make sure the Mobile tab is selected. That is the one that matters most for a local business.
- Repeat for your contact page and your busiest service page. Pages can behave very differently.
3. Read the three numbers that matter
Near the top, PageSpeed Insights may show a section about what real visitors experienced over the past 28 days. If your site does not get enough Chrome traffic, that section says there is no data, which is normal for a small site, and you can rely on the lab test further down instead (how PageSpeed Insights works).
The three Core Web Vitals, in plain English (web.dev):
- Largest Contentful Paint (LCP): how long until the main thing on the page, usually a big photo or headline, shows up. Good is 2.5 seconds or less.
- Interaction to Next Paint (INP): how quickly the page responds when someone taps a button or menu. Good is 200 milliseconds or less. The lab test cannot measure this one directly and shows Total Blocking Time as a stand-in.
- Cumulative Layout Shift (CLS): how much things jump around while loading. Good is 0.1 or less.
Green is good, orange needs improvement, and red is poor (Search Console Core Web Vitals report). Needs improvement is LCP over 2.5 seconds up to 4 seconds, INP over 200 milliseconds up to 500 milliseconds, and CLS over 0.1 up to 0.25. Poor is LCP over 4 seconds, INP over 500 milliseconds, and CLS over 0.25. The overall score out of 100 is a lab estimate and can change a few points between runs even when nothing changed, so do not chase a perfect 100. Focus on getting the three numbers into the green.
4. Find the usual suspects
Scroll down to the suggestions (labeled as diagnostics or opportunities). On small business sites, the same few causes show up again and again:
- Huge photos. A phone does not need a 5,000-pixel photo straight off a camera. Look for suggestions about properly sizing or compressing images, or serving them in modern formats.
- A big slideshow or video at the top. Autoplay sliders and background videos are often the single slowest thing on the page.
- Too many add-ons. Chat widgets, review feeds, social media embeds, extra fonts, several tracking scripts, and old plugins you no longer use all add weight. Look for suggestions about unused JavaScript or third-party code.
- Slow server response. If the report flags a slow initial server response, the hosting itself may be the bottleneck, not the page.
- Things that jump. Ads, banners, or images without a set size push text down as they load, which hurts layout shift.
Take a screenshot of the top few suggestions for each page you tested.
5. Fix what you can yourself
These are usually safe for an owner to do in your website builder:
- Shrink photos before uploading. Resize to roughly the width they actually display at (for most sites, no more than about 2,000 pixels wide for a full-width photo, much less for small ones) and compress them. Many builders do some of this automatically, but not for every image or theme.
- Replace an autoplay slider with one strong photo and a clear headline.
- Remove add-ons you do not use. Old pop-ups, a second chat tool, a social media feed nobody checks. If your site uses plugins, deactivate an unused one first, check the site, then delete it.
- Swap a live map embed on the home page for a simple “Get directions” link to your Google Maps listing, if the map is slow.
After each change, rerun PageSpeed Insights on the same page so you know what helped.
6. Hand the rest to your web person with a clear list
Send whoever manages the site:
- The page addresses you tested.
- Your screenshots of the three numbers and the top suggestions for each page.
- What you noticed on your phone in step 1.
- A plain ask, for example: “Can we get LCP to 2.5 seconds or less on mobile for these three pages, and tell me which add-ons are slowing it down?”
Typical fixes on their side include caching, image lazy-loading, trimming scripts, a lighter theme, or a content delivery network. If slow server response keeps showing up, ask whether the hosting plan is the problem.
7. Keep an eye on it
- Put a monthly reminder on your calendar to rerun PageSpeed Insights on your top pages.
- If you use Search Console, open the Core Web Vitals report once in a while. It groups pages by status, but only once Google has enough real visitor data, so a small site may show nothing there for a long time (Core Web Vitals report help).
- Retest any time you add a new plugin, widget, slideshow, or big batch of photos.
Caution
- Back up your site, or confirm your builder keeps version history, before removing plugins or changing themes. A deactivated plugin can break a form or booking page.
- After every change, test your contact form and booking or checkout on a phone. A faster page that no longer sends leads is a bad trade.
- Do not delete your analytics or tracking code to raise the score without deciding you no longer need that data. Ask your web person about loading it more efficiently instead.
- Be wary of “speed booster” plugins that promise a perfect score. Stacking several of them can conflict and slow the site down or break it.
- Scores vary from run to run. Compare a few runs before deciding a change helped or hurt.
- Be careful with emails or calls offering to “fix your Google speed score” for a guaranteed ranking. Speed helps visitors stay; it is not a ranking guarantee.