If your website takes too long to load, visitors leave before they see your services. For a small business, that means lost calls, lost bookings, and lost sales, and it can also hold back your Google rankings.
This guide shows how to check page speed for a small business website using free tools, how to read the results, and what to fix first.
Quick answer
To check page speed for a small business website, enter your page address into Google PageSpeed Insights and run the test for mobile. Read the Core Web Vitals results at the top, then look at the list of opportunities below. Test your homepage and your most important service or product pages, and repeat after each fix.
Why page speed matters
- Visitors: Slow pages lose people, especially on mobile connections.
- Conversions: a faster page makes it easier to call, book, or buy.
- SEO: Google uses page experience signals, including Core Web Vitals, as one of many ranking factors. Speed alone will not rank a weak page, but a slow page can lose to a similar fast one.
The numbers to watch: Core Web Vitals
Google measures page experience with three main metrics called Core Web Vitals.
| Metric | What it measures | Good score |
|---|---|---|
| Largest Contentful Paint (LCP) | How long the main content takes to appear | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds when someone taps or clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the page jumps around while loading | 0.1 or less |
If most of your visitors see scores in the “good” range for all three, your page passes the Core Web Vitals check.
How to check page speed for free
Method 1: Google PageSpeed Insights
This is the best place to start. It is free, needs no account, and shows what Google measures.
- Open PageSpeed Insights and paste the full address of your page.
- Select Analyze and wait for the result.
- Start with the Mobile tab, because most visitors and Google’s tests focus on mobile.
- Read the Core Web Vitals section at the top, then scroll to the Opportunities and Diagnostics lists.
You will see two kinds of data:
- Field data: results from real visitors over the past 28 days. It only appears if your page has enough visits. This is the data that matters most.
- Lab data: a test run once on a simulated device. It is useful for finding problems and checking fixes, but it can differ from what real visitors see.
A small or new site often has no field data yet. In that case, rely on the lab results to find fixes.
Method 2: The Core Web Vitals report in Google Search Console
If you have verified your site, this report shows how groups of your pages perform for real visitors.
- Open Google Search Console and select Core Web Vitals in the menu.
- Open the mobile report and then the desktop report.
- Select a group of URLs marked “Poor” or “Needs improvement” to see the issue and example pages.
The report appears only when your site has enough real visitor data.
Method 3: Lighthouse in Chrome
- Open your page in Google Chrome and right-click, then select Inspect.
- Open the Lighthouse tab, choose Mobile, and select Analyze page load.
This gives a lab report like the one in PageSpeed Insights. It is handy for testing pages that are not public yet.
Method 4: GTmetrix or WebPageTest
These free tools show a detailed loading timeline, which helps you see what slows the page down, such as a large image or a slow third-party script. They also let you choose a test location, which can matter if your customers are in a particular region.
How to read the results and what to fix first
The overall score is a guide, not a goal. Focus on the three Core Web Vitals and on the specific items listed under Opportunities. Fix the biggest ones first.
| Common problem | How to spot it | What to do |
|---|---|---|
| Large, uncompressed images | “Properly size images” or “Serve images in next-gen formats” | Resize images to the size they display, compress them, and use WebP or AVIF where your site supports it. |
| Slow main image or banner (poor LCP) | The LCP element is an image or hero section. | Compress it, do not lazyload it, and make it the right size for mobile. |
| No browser caching or compression | “Serve static assets with an efficient cache policy” | Turn on caching and compression through your host or a caching plugin |
| Too many plugins or scripts | “Reduce unused JavaScript” | Remove plugins and scripts you do not need |
| Third-party scripts | Chat widgets, trackers and ad tags in the diagnostics | Remove the ones you do not use and load the rest later |
| Layout jumping (poor CLS) | Content moves as the page loads | Set the width and height on images and reserve space for banners and embeds. |
| Slow server response | “Reduce initial server response time” | Upgrade your hosting plan, or use caching or a content delivery network (CDN) |
| Render-blocking files | “Eliminate render-blocking resources” | Minify CSS and JavaScript and load non-essential files later |
For most small business sites, images, plugins, and hosting cause the bulk of the problem. Fix those three before anything else.
A simple order of work
- Run PageSpeed Insights on your homepage and your top two or three money pages on mobile.
- Write down the Core Web Vitals and score for each page.
- Fix images first, then caching, then unused plugins and scripts.
- Retest each page and compare with your starting numbers.
- If the server response is still slow, talk to your host or consider a better plan.
Testing tips
- Test the pages that matter. Check your homepage, your main service or product pages, and your contact or booking page, not only one page.
- Test on mobile first. Most visitors and Google’s checks focus on mobile.
- Run each test two or three times. Results can vary a little between runs, so look for the trend, not a single number.
- Change one thing at a time. You will then know which fix made the difference.
- Test after changes. Recheck after you install a plugin, change your theme, or add a new script.
- Check on a real phone. Open the page on your own phone on mobile data and notice how it feels.
How often to check
Check your key pages once a month, and after any redesign, plugin change, or new tracking script. Keep a simple record of your scores so you can see whether things improve or slip.
FAQ
What is a good page speed score?
A PageSpeed Insights performance score of 90 or higher is considered good, but the Core Web Vitals matter more than the score. If your LCP, INP, and CLS are in the good range for real visitors, your page passes.
Does page speed affect SEO?
Yes, as one of many signals. Speed alone will not make a weak page rank, but a slow page can lose visitors and may rank below a similar page that loads quickly.
Why is my mobile score lower than my desktop score?
Mobile tests simulate a slower device and connection, so they are stricter. Fix the mobile results first.
Do I need a developer to fix page speed?
Not always. Compressing images, removing unused plugins, and turning on caching are easy for most site owners. Slow hosting or heavy scripts may need your host or a developer.
Conclusion
Checking page speed takes a few minutes and tells you exactly where your site is slow. Run your key pages through PageSpeed Insights on mobile, read the Core Web Vitals, and fix images, caching, and unused plugins first. Then retest and check again every month.
