Page Speed Checker

Measure real load speed with Google PageSpeed Insights

  • 100% Free
  • Files stay private
  • Works in your browser
Try it now·Page Speed Checker

Page to analyze

Enter a URL and pick a device profile to run a Lighthouse performance audit.

RequiredThe full address of the page to analyze.

Lab data from Google PageSpeed Insights; can take ~10s to 30s.

How it works

  1. Choose a device and URL

    Pick Mobile or Desktop, then type the full address of the page into the Page URL field.

  2. Press Analyze speed

    Your URL is sent through our server to Google PageSpeed Insights, which runs a Lighthouse performance test. This can take 10 to 30 seconds.

  3. Read your score

    The Performance results show a Performance score rated Good, Needs improvement or Poor, plus Core Web Vitals such as LCP and CLS.

Enter a URL and see how fast the page really loads. Page Speed Checker runs your page through Google PageSpeed Insights and returns the Lighthouse performance score out of 100, along with the Core Web Vitals that make up that score (Largest Contentful Paint, First Contentful Paint, Cumulative Layout Shift, Total Blocking Time, Speed Index, and Time to Interactive) for a mobile or desktop profile.

What Is Page Speed Checker?

Page Speed Checker is a free tool that measures a single page's loading performance and reports it as a Lighthouse score from 0 to 100. You submit a URL and pick mobile or desktop; our server calls Google PageSpeed Insights, which loads the page in a controlled lab environment and times each stage of the render. The result breaks down into the metrics Google weights in its score: LCP, which marks when the main content appears; FCP, the first pixel painted; CLS, how much the layout jumps around; TBT, how long the main thread is blocked; Speed Index, how quickly content fills the screen; and TTI, when the page becomes reliably interactive. Because the page is fetched and rendered fresh each time, a check typically takes about 10 to 30 seconds depending on the page's size and the chosen profile.

Who Benefits from This Tool

  • Performance engineers: get a repeatable lab score to track before and after an optimization.
  • Technical SEOs: monitor Core Web Vitals that feed into Google's page-experience signals.
  • E-commerce managers: tie a slow LCP on product pages to the load-time drag that costs conversions.
  • Front-end developers: pinpoint whether a jump in TBT came from a heavy script or a third-party tag.
  • Agency account managers: pull a clear, shareable score to show a client the impact of a speed project.
  • Site owners on WordPress or Shopify: check whether a new theme or plugin quietly slowed the page down.

Key Features

  • 0-100 performance score: the headline Lighthouse number that summarizes overall page speed at a glance.
  • Core Web Vitals breakdown: LCP, FCP, and CLS reported individually so you know which metric is dragging.
  • Blocking and interactivity metrics: TBT, Speed Index, and TTI show how responsive the page feels while loading.
  • Mobile or desktop profile: switch between the two, since a page can score very differently on each.
  • Lab-based measurement: runs in PageSpeed Insights' controlled environment for consistent, comparable results.
  • No account needed: free to run with no sign-up, install, or API key of your own.

How to Use

  1. Enter the full URL of the page you want to measure, including https://.
  2. Choose the mobile or desktop profile, depending on which audience you care about.
  3. Run the check and wait roughly 10 to 30 seconds while the page is rendered and timed.
  4. Read the 0-100 score first, then look at LCP, CLS, and TBT to see what's pulling it down.
  5. Apply a fix, then re-run on the same profile to measure whether the metric improved.

Common Use Cases

  • Benchmarking a landing page's speed before and after compressing images.
  • Diagnosing a poor LCP caused by a large hero image or a slow server response.
  • Comparing mobile versus desktop scores to see where the bigger problem lives.
  • Tracking whether a new analytics or chat script pushed TBT into the red.
  • Producing a quick performance snapshot to include in a client audit.

Tips and Best Practices

  • Test on mobile first. It's usually the harder profile and the one Google weights most.
  • Run a check two or three times; lab scores vary run to run, so look at the range, not one number.
  • Chase the worst metric first: a red LCP or TBT moves the overall score more than fine-tuning a green one.
  • Aim for LCP under 2.5 seconds and CLS under 0.1 to clear the "good" Core Web Vitals thresholds.
  • Test the specific page that matters, not just the homepage; templates perform differently under real content.

Limitations and Notes

These numbers are lab data: a single controlled measurement, not the field data Google collects from real Chrome users over time. A page can post a strong lab score and still feel slow for visitors on weak connections or older phones, so treat the score as a diagnostic baseline rather than a promise. Results can vary from run to run because network and server conditions shift, and a very large or heavily rate-limited page may time out. The tool checks one publicly reachable page at a time; pages behind a login or firewall won't return results. Our server performs the PageSpeed Insights lookup on your behalf. The tool does not run in your browser, and the URL you submit is used only to run the test.

FAQs

It's lab data, meaning a single controlled measurement from PageSpeed Insights rather than field data averaged across real visitors. Lab data is great for diagnosing and comparing fixes, but real-user experience can differ depending on devices and networks.

Lab scores fluctuate because server response times, network conditions, and third-party scripts vary between runs. Run the check a few times and judge the page by the typical range rather than any single result.

Google treats 90 to 100 as good, 50 to 89 as needing improvement, and below 50 as poor. Getting mobile pages into the 90s is demanding, so steady gains toward the green band are a realistic goal.

Start with whichever Core Web Vital is worst, often LCP or TBT, because those carry the most weight in the score. Fixing a red metric usually moves the overall number far more than polishing one that's already green.

No. Our server calls Google PageSpeed Insights on your behalf and returns the metrics to you. The page isn't measured locally on your own device.

Each run measures one profile, since a page can score very differently on mobile versus desktop. Run it once for each profile to get a full picture of how the page performs on both.

More Website Management Tools

Other tools in Website Management Tools.

All Website Management Tools