Skip to content
Devtoolry

Page Speed Checker

Test page speed on mobile and desktop: real-user Core Web Vitals (LCP, INP, CLS) from Chrome and a Lighthouse score with the biggest fixes, from Google PageSpeed Insights.

Something not working, or missing a feature? Send feedback

About the Page Speed Checker

The Page Speed Checker tests a page with Google PageSpeed Insights and shows both kinds of speed data. Field data comes from real Chrome users over the last 28 days (the Core Web Vitals Google uses in ranking: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift), for the page or, when it has too little traffic, the whole site. Lab data is one simulated Lighthouse visit with a 0–100 performance score and the changes that would save the most time.

Our server sends the URL to Google PageSpeed Insights, and Google loads and measures the page. Results are cached in memory for 30 minutes; nothing is stored on disk.

How to use the Page Speed Checker

  1. Enter the page address and choose mobile (what Google indexes) or desktop.
  2. Wait 10–40 seconds while Google loads and measures the page.
  3. Check the real-user Core Web Vitals first; they are what counts for search.
  4. Work through the biggest opportunities, then test again.

Works well with the Page Speed Checker

Frequently asked questions

What are good Core Web Vitals?

At the 75th percentile of visits: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds and Cumulative Layout Shift under 0.1. A page passes when all three are good.

Why is there no real-user data?

Google only publishes field data when enough Chrome users visited the page (or the site) in the last 28 days. New and small sites see only the lab test until then.

Why does the score change between tests?

The lab test is one simulated visit, so network and server timing vary from run to run. Compare several runs, and trust the field data for the real picture.