Lab data and real-user data
The test asks Google’s PageSpeed Insights to load your page and measure it with Lighthouse, on a simulated mid-range phone or on a desktop. You get a performance score out of 100 and the key Core Web Vitals: Largest Contentful Paint (when the main content appears), Cumulative Layout Shift (how much the layout moves) and Total Blocking Time (how long the page stays unresponsive). When your site has enough traffic, Google also shows data measured on real Chrome visitors over the last 28 days, which is what counts for search.
Reading the results
- 90 to 100: fast. Keep an eye on it after each change.
- 50 to 89: room for improvement; the opportunities listed below the score show where to start.
- Below 50: slow. Visitors on mobile are likely to leave before the page appears.
Scores vary from one run to the next: run the test two or three times before drawing conclusions, and always test on mobile first.
The usual culprits
Oversized images (convert them with the WebP converter), too many third-party scripts, a slow server or cheap shared hosting, and themes that load everything on every page. For a check of the rest of the page — titles, indexing, structured data — run the SEO analyzer. If you need a faster site, our website development team builds pages with performance in mind from the start.
Read our guide: Core Web Vitals in plain English.
Are you an agency? We work white-label →
Frequently asked questions
Why does my score change from one test to the next?
Lab tests depend on network and server conditions at that moment. Run the test two or three times and look at the trend.
What is a good score?
90 or more is fast, 50 to 89 needs improvement, under 50 is slow. Real-user data, when available, matters most for search.
Is my API key or data exposed?
No. The test runs on our server, which calls Google’s API; only the page address is sent.