Pull live Google PageSpeed results for performance, SEO, accessibility, and key loading metrics on mobile or desktop.
If this tool isn’t working as expected, please take a screenshot of the error and report the problem here so we can investigate and improve it.
Core Web Vitals are Google's user experience metrics that factor into search rankings. A page that loads slowly (high LCP), feels unresponsive to interaction, or shifts its layout unexpectedly (high CLS) can rank behind faster, more stable competitors.
This tool fetches live Google PageSpeed data for any public URL on mobile or desktop, so you can see exactly where a page stands without running Lighthouse yourself or opening PageSpeed Insights directly.
This tool sends the URL you provide to our server, which calls Google's PageSpeed Insights API (Lighthouse) on your behalf and returns live performance, SEO, accessibility, and best-practices scores, plus loading metrics for mobile or desktop. Largest Contentful Paint, Speed Index, Total Blocking Time, and Cumulative Layout Shift come from Lighthouse's simulated lab run; a separate "Interaction Metric" (in milliseconds) comes from Google's real-user field data when available, prioritizing INP (Interaction to Next Paint, the current Core Web Vital) with a fallback to the older First Input Delay field only if INP data isn't present.
Provide the page to analyze along with your preferred device.
Google PageSpeed returns live Lighthouse scores and loading diagnostics.
Review category scores for performance, SEO, accessibility, and best practices.
Use the advice cards to prioritize image and script work.
Provide the page URL and choose Mobile or Desktop, then click Run Live Analysis.
Check the Performance, SEO, Accessibility, and Best Practices percentages for a quick overall read.
Review Largest Contentful Paint, Speed Index, Total Blocking Time, Cumulative Layout Shift, and the Interaction Metric for specifics.
Re-run the same URL with the other device selected to see how the experience differs.
Copy or download the results as a plain-text summary for a report or before/after comparison.
Best For
Input
A URL, Device: MobileResult Shape
4 category scores (e.g., Performance 87%), 4 lab metrics (LCP, Speed Index, TBT, CLS) from that run's Lighthouse simulation, and one Interaction Metric value in ms from Google's real-user field dataThe category scores and 4 lab metrics are freshly simulated on every run; the Interaction Metric alone reflects real visitors' actual experience over a recent period, when Google has collected enough data for that URL.
Re-run the same URL after a change like image compression or lazy loading to confirm the lab metrics improved.
Run a competitor's public URL to see their Lighthouse scores and loading metrics for comparison.
Run the same URL on both device settings to see where the gap is largest.
Problem
Solution
Only the Interaction Metric comes from real-user field data when available - Largest Contentful Paint, Speed Index, Total Blocking Time, and Cumulative Layout Shift are always Lighthouse's simulated lab results.
Problem
Solution
Google only provides field data for URLs with enough real-world traffic - lower-traffic pages will show "Not available" for the Interaction Metric.
Problem
Solution
The tool shows a generic "Interaction Metric" value in milliseconds rather than naming a specific metric - it prioritizes INP data when Google provides it.
Problem
Solution
Each run is a single live snapshot - there's no saved history, monitoring, or trend chart across multiple checks.
Problem
Solution
Google's PageSpeed API can rate-limit rapid requests - if you see a "temporarily unavailable due to high demand" message, wait a moment before retrying.
Performance often differs significantly by device - run the URL twice with each device setting rather than assuming one result represents both.
This means Google doesn't have enough real-user traffic data for that URL yet - the lab metrics (LCP, Speed Index, TBT, CLS) are still valid on their own.
Lab scores can vary slightly between runs due to normal measurement variance - use it to validate a specific fix rather than to chase small run-to-run fluctuations.
Google's commonly cited pass thresholds are roughly LCP under 2.5 seconds, an interaction metric under 200ms, and CLS under 0.1 - the tool doesn't apply these itself, so compare the returned numbers against them yourself.
The tool returns raw metric values and category percentages - it doesn't apply Google's Core Web Vitals thresholds itself or label a result as passing or failing.
Google only supplies real-user field data for pages with sufficient traffic - lower-traffic URLs will show "Not available" for this metric even though the lab metrics still return.
Only the Interaction Metric is sourced from real-user field data - Largest Contentful Paint and Cumulative Layout Shift shown here are lab (simulated) values, not field data, even though Google's field data can include those too.
Each check is a single live snapshot - there's no saved history, scheduled monitoring, or trend tracking across multiple runs.
Rapid repeated requests can trigger a temporary "high demand" error from Google's PageSpeed API - space out repeated checks on the same URL.
Localhost addresses and private network IP ranges are blocked and can't be checked.
If Google's API doesn't respond within 15 seconds, the request fails with a timeout error.
Both come from the same PageSpeed Insights call, but they measure fundamentally different things.
| Lab Metrics (LCP, Speed Index, TBT, CLS) | Interaction Metric (Field Data) | |
|---|---|---|
| Source | Lighthouse's simulated test run, fresh every time | Google's aggregated real-user data (CrUX), when available |
| Always available? | Yes - returned on every successful run | No - only for URLs with enough real-world traffic |
| What it reflects | A simulated run under controlled conditions | How real visitors actually experienced interaction responsiveness |
Which should you use?
Lab metrics are consistent and always available but simulated; the Interaction Metric reflects real visitors but only exists for well-trafficked pages - use both together rather than relying on either alone.
The most common question is whether these are lab results or real-user data. Both, depending on the metric: Largest Contentful Paint, Speed Index, Total Blocking Time, and Cumulative Layout Shift come from Lighthouse's simulated lab test every time, while the Interaction Metric is real-user field data from Google - and it's only available for URLs with enough traffic for Google to have collected it. The FAQ below covers thresholds, the lab-vs-field distinction, and what to do when field data isn't available.
Both, depending on the metric: Largest Contentful Paint, Speed Index, Total Blocking Time, and Cumulative Layout Shift are Lighthouse's simulated lab results on every run. The Interaction Metric is real-user field data from Google, shown only when Google has collected enough traffic data for that URL.
It returns four Lighthouse category scores (Performance, SEO, Accessibility, Best Practices), four lab metrics (Largest Contentful Paint, Speed Index, Total Blocking Time, Cumulative Layout Shift), and one field-data Interaction Metric in milliseconds, prioritizing INP with a fallback to the legacy FID field if INP isn't available.
Yes. Choose either device mode before running the check to compare experiences.
Google's commonly cited thresholds are roughly LCP under 2.5 seconds, an interaction metric under 200 milliseconds, and CLS under 0.1. This tool returns the raw numbers but doesn't label them pass or fail itself, so compare them against these figures yourself.
Google only provides real-user field data for URLs with enough traffic - lower-traffic pages won't have this data yet, even though the other lab metrics will still return normally.
Leave your email so we can prioritize similar tools and updates.
Trending tools will appear as visitors explore the catalog.
Your recently visited tools will show up here.