Google PageSpeed Insights is a free tool that tests how quickly your web pages load and what is slowing them down. Many business owners run it once, see a red number and don't know what to do next.
This guide explains how to run a test, how to read the results, and which fixes tend to matter most for typical small business websites.
How to run a test
- Go to PageSpeed Insights and paste in the address of a page, such as your homepage.
- Click to analyse. It takes a few seconds.
- Look at the Mobile results first. Most visitors use phones, and Google primarily uses the mobile version of your site for search.
- Switch to Desktop to compare.
Test more than just your homepage. Try your most visited page, a service page and, if you sell online, a product page. Slow pages are often not the one you expect.
Lab data and field data
PageSpeed Insights shows two kinds of data, and it helps to know the difference.
Field data (sometimes labelled as real-user data) comes from real visitors using Chrome over the previous period. It tells you how your page actually performs for people. It only appears if your site gets enough visits to have data.
Lab data comes from a test run on the spot, on a simulated device and connection. It's useful for diagnosing problems, but it varies between runs and won't match what every visitor experiences.
If both are available, field data shows your real-world situation, while lab data helps you work out why.
What the numbers mean
The performance score runs from 0 to 100. Broadly, 90 and above is good, 50 to 89 needs improvement, and under 50 is poor. Don't obsess over it. It comes from the lab test, and it moves around a few points between runs.
The three Core Web Vitals matter more, because Google uses them as part of how it assesses page experience:
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How long the main content takes to appear | 2.5 seconds or less | More than 4 seconds |
| INP (Interaction to Next Paint) | How quickly the page responds when someone taps or clicks | 200 milliseconds or less | More than 500 milliseconds |
| CLS (Cumulative Layout Shift) | How much the page jumps around while loading | 0.1 or less | More than 0.25 |
Our guide to Core Web Vitals for Irish business owners explains each of these in more detail.
Reading the suggestions
Below the scores, PageSpeed Insights lists "Opportunities" and "Diagnostics". These are specific suggestions, usually sorted by how much time they might save. Don't try to fix every item. Look at the top few, and ask what's causing them.
The fixes that matter most
For most small business sites, a handful of causes account for most of the slowness.
1. Oversized images. This is the single most common problem. Photos straight from a camera or phone can be several megabytes. Resize images to the size they're actually displayed at, compress them, and use modern formats such as WebP or AVIF where your platform supports them. Add "lazy loading" to images lower down the page, but not to the main image at the top, which should load immediately.
2. Too many third-party scripts. Chat widgets, tracking pixels, social feeds, review badges and fonts from outside sources all add load time. Ask whether each one earns its place. Remove the ones that don't.
3. Slow or cheap hosting. If the server takes a long time to respond, nothing else will fix it. Look at the "server response time" suggestion. A better hosting plan, or a content delivery network, can make a big difference.
4. No caching. Caching stores a ready-made copy of your pages so the server doesn't have to rebuild each one for every visitor. Most platforms have a caching option or plugin.
5. Render-blocking code. Large stylesheets and scripts that load before anything appears can delay the first view. Minifying files and loading non-essential code later helps. This usually needs a developer.
6. Layout shifts. If the page jumps while loading, set width and height on images and reserve space for adverts, embeds and banners, so nothing pushes the content down after it appears.
7. Heavy themes and plugins. On platforms like WordPress, a bloated theme or a pile of plugins can slow a site badly. Remove what you don't use. Choose lightweight, well-maintained tools.
8. Web fonts. Loading several font families and weights adds up. Use fewer, and make sure text shows while fonts load.
What not to worry about
- A perfect 100. It's rarely worth the effort, and chasing it can make a site worse for real users.
- Small differences between runs. Run it a few times and look at the trend.
- Desktop results alone. Mobile is what counts most.
- Fixing everything at once. Change one thing, test, and see what happened.
After you make changes
Test again, using the same pages, and compare. Remember that field data takes time to update, because it reflects the previous weeks of real visits. Google Search Console has a Core Web Vitals report that shows how your pages are doing across the whole site, and flags groups of pages that need attention.
Speed is part of maintenance
Sites rarely get faster on their own. New images, plugins and scripts get added over time, and the score slips. That's why speed checks belong on a regular maintenance schedule, as in our website maintenance checklist. If you're unsure whether your slow site is losing you customers, our post on 5 signs your website is losing customers is a good place to look.
Want it looked at properly?
If you'd like someone to run the tests, work out what matters and fix it, speed work is part of our SEO services and can be done within a website care plan. You can also book a free call, and we'll tell you honestly what's worth doing.