Lab data and field data
PageSpeed Insights shows two kinds of results. Field data comes from real Chrome users over the previous 28 days and reflects actual experiences. Lab data comes from a single simulated test run now, on a defined device and network. Field data tells you how you are doing, and lab data helps you find out why.
If your site has too little traffic, field data may be missing. Then rely on repeated lab tests.
What the score means
The performance score from 0 to 100 blends several lab metrics. It is a summary, not a verdict. A site can score in the 80s and still pass every Core Web Vital for real users, while another scores 95 and still feels sluggish under real conditions. Look at the individual metrics and the opportunities list rather than the headline number.
Other tools and what they add
GTmetrix shows a waterfall of every file with timings, helpful for spotting slow requests. WebPageTest allows testing from different locations and devices and shows filmstrip views of the load. Chrome DevTools Lighthouse runs similar audits locally. Search Console reports Core Web Vitals by group of pages using field data.
Results differ among tools because test settings differ. Pick one method and compare like with like.
Test properly
Test your most important pages, not just the home page. Use mobile settings, since that is where most problems appear. Run each test three times and look at the median, as single runs vary. Test while logged out and without browser extensions interfering.
Record the date, the page and the main numbers before you make changes, so you can prove an improvement.
Prioritize the findings
Sort suggestions by impact. Large images, slow server response, heavy scripts and render-blocking files tend to matter most. Small items, such as a few hundred bytes of unused code, rarely deserve your time. Some warnings come from third-party tools you cannot change, like an ad or chat script; decide whether the tool is worth its cost.
Fix one cause at a time and retest.
Set realistic goals
Aim for good Core Web Vitals and a site that feels fast on a mid-range phone, not a perfect score. Check again after redesigns or when you add features. Speed is a habit, not a one-time project.
For a worked example, imagine a score of 54 on mobile with a flagged hero image of 2 MB, a chat script and unused CSS. Compress and resize the hero, delay the chat script, and retest. The score may jump into the 70s or 80s with only two changes, while the unused CSS item, worth a few milliseconds, can wait. Track the Core Web Vitals report in Search Console to see whether real visitors notice the difference.
Finally, keep a simple log of each test with the date, the tool, the page and the scores. Over a year it shows whether your habits are holding speed steady or letting it creep downward after each new plugin or banner.
Common questions
Why is my score different every time?
Network conditions, server load and the test machine vary. Compare medians across several runs.
Is a score of 100 necessary?
No. Passing the Core Web Vitals and giving visitors a quick experience matters more.
Which tool should I use?
PageSpeed Insights for a quick view with field data, plus a waterfall tool when you need detail.
This guide is general information. Search engines change how they work and their guidelines; check Google's current documentation for your situation. Nobody can guarantee a ranking.