PageSpeed Checker
Lighthouse scores and real-user Core Web Vitals for mobile and desktop, powered by Google.
- Free
- No sign-up
What is a PageSpeed checker?
A PageSpeed checker measures how fast a page loads and how stable and responsive it feels. This tool uses the Google PageSpeed Insights API, the same engine behind Google's own PageSpeed Insights report, and presents the results in separate mobile and desktop tabs. Each tab combines two very different kinds of data: a Lighthouse lab test run on demand, and real-user measurements from the Chrome UX Report.
The lab data comes from Lighthouse loading the page once in a controlled environment. You get the Lighthouse performance score from 0 to 100 and five metrics: Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Total Blocking Time (TBT), First Contentful Paint (FCP) and Speed Index. Below them are the top opportunities with estimated savings and diagnostics that explain what the page is doing.
The field data shows the Core Web Vitals that real Chrome users experienced: LCP, Interaction to Next Paint (INP) and CLS, each at the 75th percentile with a pass or fail verdict. It is shown for the specific URL and for the whole origin when Google has enough traffic data. The tests run on Google's infrastructure, not from our server in Germany, so our location does not affect the numbers. Results are cached briefly, so repeating a check within a short window returns the same report.
How to check page speed
- 1
Enter the page URL
Paste the full URL. Test your most important templates individually, such as the homepage, a product or service page and an article, because each performs differently.
- 2
Run the test
The tool requests a PageSpeed Insights analysis. Lighthouse loads the page, which typically takes several seconds to complete.
- 3
Start with field data
If Core Web Vitals field data is available, check whether LCP, INP and CLS pass at the 75th percentile. This is what real visitors experience and what Google uses.
- 4
Switch between mobile and desktop
Mobile results are almost always worse because the test simulates a mid-range phone on a throttled connection. Prioritize mobile if most of your traffic comes from phones.
- 5
Work through opportunities
Address the opportunities with the largest estimated savings first, then use the diagnostics to find the cause of long tasks, layout shifts or a slow LCP element.
When to use a PageSpeed checker
Diagnosing failing Core Web Vitals
When Search Console flags URLs as poor or needing improvement, test a representative URL to see which metric fails and what lab diagnostics suggest.
Testing before and after a release
Run the lab test before and after deploying a new theme, script or image strategy to catch regressions before they reach field data.
Evaluating third-party scripts
Chat widgets, tag managers, ad scripts and consent banners often dominate Total Blocking Time. Diagnostics show which scripts cost the most.
Comparing templates and competitors
Test similar pages on your site and on competing sites to see whether a speed gap exists and where it comes from.
Lab vs field data, and the thresholds that matter
Field data comes from the Chrome UX Report (CrUX), which aggregates real visits over a rolling 28-day window. A page passes Core Web Vitals when all three metrics are good at the 75th percentile: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less. Values up to 4 seconds, 500 milliseconds and 0.25 respectively count as needing improvement; anything above is poor. INP replaced First Input Delay (FID) as a Core Web Vital in March 2024.
Lab data is a single simulated load, useful for debugging because it is repeatable and explains causes. The Lighthouse score weights five metrics: TBT and LCP carry the most weight, followed by CLS, then FCP and Speed Index. Lab tests do not include user interactions, so they cannot measure INP; TBT is the closest lab proxy, since long main-thread tasks are what delay responses to taps and clicks.
The two often disagree, and that is expected. Real visitors use faster or slower devices than the emulated phone, arrive with warm caches, and interact with the page. When they conflict, field data reflects reality and is what Google's page experience signals use. A low Lighthouse score with passing field data is not an emergency; passing lab scores with failing field data deserves attention.
Frequently asked questions
Is the PageSpeed checker free?
Yes, the PageSpeed checker is free and requires no account. You get mobile and desktop results, Lighthouse lab metrics, Core Web Vitals field data when available, opportunities and diagnostics. Checks are rate-limited per visitor, and recent results are cached briefly so repeated tests of the same URL return quickly.
What is sent where, and is anything stored?
The URL you enter is sent to Google's PageSpeed Insights API, and Google's servers load that page to run Lighthouse and look up CrUX data. Nothing else from your site is fetched by us. Reports are cached briefly to avoid duplicate requests, then discarded; they are not saved to your profile or published.
Why does my score change every time I run it?
Lighthouse scores vary between runs because server response times, network conditions, third-party scripts and ads change from load to load. Swings of several points are normal. Run a few tests and look at the trend, and rely on field data for the overall picture since it averages thousands of real visits.
Why is there no field data for my page?
Field data appears only when the Chrome UX Report has enough real-user visits for that URL or origin. New pages, low-traffic sites and pages behind logins often fall below that threshold. When URL-level data is missing, check whether origin-level data is shown, and use the lab results for debugging in the meantime.
Does the Lighthouse score affect Google rankings?
No, the Lighthouse score itself is not a ranking factor. Google's page experience signals use Core Web Vitals field data from real Chrome users, not lab scores. A faster page still helps users and conversions, but chasing a perfect 100 rarely pays off once your field metrics pass.
Why is mobile so much slower than desktop?
The mobile test emulates a mid-range phone with a throttled CPU on a slow 4G connection, while the desktop test uses a fast machine and connection. Heavy JavaScript hurts most on mobile, because parsing and executing it takes several times longer on a slower processor, which raises TBT and delays LCP.
Related tools
More Domain & Server tools →Bulk Redirect Chain Checker
Trace every hop for up to 100 URLs — chains, loops, 302s and broken destinations.
Domain & Server
HTTP Headers Checker
See every response header, hop by hop — with a security grade and caching explained.
Domain & Server
DNS Lookup
Query A, AAAA, MX, NS, TXT, SOA and CAA records on Cloudflare and Google DNS — plus SPF and DMARC checks.
Domain & Server
What Is My IP Address
Your public IP, country, browser and connection details — instantly, and never logged.
Domain & Server