Chapter 1 · The resource
Speed with PageSpeed Insights, explained simply
Follow this course in your space: your progress is saved, and the community answers your questions.
Follow for freePageSpeed Insights is a free Google tool that measures the speed and quality of a page. You paste your website's address, click "Analyze," and get a report full of colors, numbers and technical terms. This lesson teaches you to read it in five minutes and pull out what really matters.
Run the analysis
- Go to pagespeed.web.dev.
- Paste the full address of your homepage, with
https://. - Click "Analyze" and wait a few seconds.
- The report has two tabs: Mobile and Desktop. Always start with Mobile: it's the most demanding, and it's the one most of your visitors use.
Take a screenshot of the top of the report and paste it into your audit document, with the date.
The two parts of the report
At the top: data from real visitors
If your website gets enough visits, Google shows measurements collected from real users of the Chrome browser over the last few weeks. It's the most reliable part, because it reflects the real experience.
For a small website, this part is often empty, with a message saying there isn't enough data. That's not a problem: it simply means your website doesn't have enough traffic yet for Google to publish averages.
Below: the lab test
This is a simulation: Google loads your page on a virtual phone with an average connection, and measures. It gives you the famous scores out of 100.
The four scores
| Score | What it measures | What matters for you |
|---|---|---|
| Performance | How fast the page displays | The most important one for your customers on a phone |
| Accessibility | How easy it is for everyone to use, including people with low vision | Contrast, text size, alt text on images |
| Best Practices | Overall technical quality | Mainly HTTPS and visible errors |
| SEO | The technical basics of search ranking | Title, description, a page Google can read |
The colors: green from 90 to 100 (good), orange from 50 to 89 (needs improvement), red from 0 to 49 (poor).
How to read your performance score
- The score varies from one analysis to the next, sometimes by several points, without you changing anything. Run the analysis three times and keep the trend, not a single number.
- A perfect score isn't the goal. A small business website in the high orange that loads fast on your phone over 4G is in good shape. What matters is that your customers don't wait.
- Red calls for action. It almost always points to a concrete problem, often the images.
The three key measurements, translated
In the report, three measurements make up what Google calls the Core Web Vitals. Here's what they mean, with the thresholds Google considers good.
| Measurement | In plain English | Good if |
|---|---|---|
| LCP (Largest Contentful Paint) | The time to display the biggest visible element, often the large photo at the top | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How responsive the page is when you tap a button | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | Stability: does the content jump around while loading? | 0.1 or less |
INP only shows up with data from real visitors: in the lab, nobody taps your page. For a simple business website, LCP is often the measurement to watch first.
The recommendations: which ones to listen to
At the bottom of the report, PageSpeed lists ideas for improvement, often in technical jargon. For a small website, three come up often and are within your reach:
- Images that are too heavy or the wrong size ("Properly size images," "Serve images in next-gen formats," or similar wording). The fix: make your photos lighter before you upload them. A free tool like Squoosh does it in your browser. A phone photo of several megabytes can often get much smaller with no visible loss.
- Insufficient contrast (under Accessibility). Light gray text on a white background is hard to read in the sun. Make the text darker or the background lighter.
- Images without alt text (under Accessibility). Add a description to every important image.
The other recommendations (unused JavaScript, render-blocking resources, cache) are about the code. If your website is built with a ready-made tool, they're the tool's job, not yours. If you work with a web provider, send them the screenshot of the report.
Before / after: Moreau's Bakery
| Before | After | |
|---|---|---|
| Homepage photo | Phone photo uploaded as is | Same photo, made lighter and resized |
| Mobile Performance score | Red | High orange |
| LCP | Well above 2.5 s | Close to the threshold |
| How it feels over 4G | The big photo showed up last | The page displays all at once |
Only the image changed. That's often the case on small websites.
Your turn
- Analyze your homepage three times on the Mobile tab and write down the four scores, with the date.
- Write down the LCP value and see whether it beats the 2.5-second threshold.
- In your audit document, list the recommendations that mention images, contrast or alt text. They'll be your candidates for the lesson on priorities.
Recommended tool
Create your website for free in a few minutes
With Flopix, your business website is online in a few minutes, all included: hosting, edits, a step-by-step guided form. Free trial so you can judge for yourself.
Premium
Unlock every course of the group Flopix
Every lesson, new courses as soon as they come out, and the community. No commitment.