To use Google PageSpeed Insights, go to pagespeed.web.dev, enter your page URL, select Analyze and read the results for the mobile and desktop tabs. The report shows real-user data when enough exists, then a lab test with a performance score and a list of issues to fix. You can run a second check at any time with our free website speed test.
Key takeaways
- PageSpeed Insights tests one URL at a time and shows mobile and desktop results.
- The top of the report is field data from real Chrome users. The lower part is a lab test.
- A performance score of 90 to 100 is good, 50 to 89 needs improvement and 0 to 49 is poor (Google).
- Fix the biggest issue first, then test again.
How do you run a PageSpeed Insights test?
- Open Google PageSpeed Insights at pagespeed.web.dev.
- Paste the full URL of the page you want to test, including https.
- Select Analyze and wait for the report.
- Start with the Mobile tab, then check Desktop.
- Read the field data, the performance score and the issues.
Test your key pages one at a time: your homepage, a blog post and your most important landing page.
What does the PageSpeed Insights report show?
Field data
The first section shows how real visitors experienced your page, based on Chrome users over the previous 28 days. It shows whether the page passes the Core Web Vitals assessment. Field data only appears when enough visits exist.
Lab data and scores
The lab section shows a performance score from a simulated Lighthouse test, plus scores for accessibility, best practices and SEO. The lab score changes slightly between runs. Read about this in our guide on PageSpeed Insights accuracy.
Issues and audits
The lower part lists opportunities and diagnostics, such as large images or unused JavaScript, and the audits you already pass. Start with the items marked as the largest problems.
How do you read the Core Web Vitals results?
The report checks three Core Web Vitals: LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less are good (Google, web.dev). A page passes when these are met for most real visits. See our guide on how to run a Core Web Vitals test.
What is a good PageSpeed Insights score?
A good performance score is 90 to 100. Scores from 50 to 89 need improvement and scores from 0 to 49 are poor. See what a good PageSpeed score is for details.
How do you fix the issues PageSpeed Insights finds?
- Pick the largest issue in the report.
- Fix it. Common fixes are compressing images, enabling caching and removing unused scripts.
- Run the test again two or three times.
- Repeat with the next issue.
Our guide on how to increase mobile page speed and the full guide on how to improve website speed explain each fix.
What are the limits of PageSpeed Insights?
PageSpeed Insights tests one public URL at a time and cannot test pages behind a login. It does not replace real-user monitoring for a whole site. To test many URLs, see bulk PageSpeed Insights testing.
Frequently asked questions
Is Google PageSpeed Insights free?
Yes. You can test any public URL for free in your browser.
Why is there no field data for my page?
Google needs enough real-user visits to report field data. New or low-traffic pages may only show lab results.
Should I test mobile or desktop first?
Mobile first, because the mobile test is stricter and Google primarily uses the mobile version of a page for indexing.
Why does my score change every time?
Server response, network conditions and background tasks vary between runs. Test two or three times and compare the pattern.
Does the score affect my rankings?
The score itself does not. Google uses real-user Core Web Vitals as part of its page experience signals.
Conclusion
PageSpeed Insights is simple to use: enter a URL, read the field data first, then the lab score and issues, and fix one problem at a time. Cross-check your result with our free website speed test.
