Page Speed Analysis
Short answer
Test any URL with Lighthouse on mobile or desktop: performance score, Core Web Vitals (LCP, INP, CLS), real-visitor data if available, top savings.
What it does not do: It tests one URL with one lab run, whose score varies between runs, and real-visitor data appears only when Chrome has collected enough visits for the page or the site.
What It Does
Runs a real Lighthouse audit on your URL via Google's PageSpeed Insights API, returning Core Web Vitals (LCP, INP, CLS), performance score, and a prioritized list of opportunities. Includes both lab data (controlled run) and field data (real-user CrUX 28-day window) when available.
Why It Matters
Google says Core Web Vitals are used by its ranking systems, although great page experience does not outweigh relevant content. Speed also shapes what visitors do: slow pages lose people before they read a word. Fixing your slowest templates helps every page built on them.
How It Works
-
Enter your page URL and choose mobile or desktop strategy
-
We trigger a real Lighthouse run via Google's PageSpeed Insights API
-
Capture lab metrics (LCP, FCP, CLS, TBT, Speed Index) plus field data from CrUX (INP, LCP, CLS, FCP, TTFB) when available
-
Return a numeric score, the full Core Web Vitals picture, and ranked opportunities such as unused JavaScript or missing text compression
Sample input + output
url: https://rankproof.eu/tools strategy: mobile
Lab test (mobile) Performance score: 83/100 Largest Contentful Paint: 3.7 s First Contentful Paint: 2.1 s Total Blocking Time: 220 ms Cumulative Layout Shift: 0 Speed Index: 2.4 s Real visitors (last 28 days): not enough data yet Opportunities Reduce unused JavaScript −1.1 s · 200 KB
How to read the result
- Performance score (83/100)
- The lab score of one simulated load on a mid-range phone over a slow mobile connection. 90 or more is good, 50 to 89 needs improvement and below 50 is poor. It varies by a few points between runs, so compare several runs before and after a change.
- Largest Contentful Paint (3.7 s) · First Contentful Paint (2.1 s)
- When the largest text block or image in the first screen appeared, and when anything first appeared. Google's good threshold for LCP is 2.5 seconds; in the sample the main content arrives over a second after the first paint, which points to what loads before it.
- Total Blocking Time (220 ms) · Cumulative Layout Shift (0) · Speed Index (2.4 s)
- Total Blocking Time is how long scripts kept the page from responding while it loaded; it is the lab stand-in for INP, which needs real visitors. Layout shift measures how much content jumped (0.1 or less is good). Speed Index is how quickly the visible area filled in.
- Real visitors (not enough data yet)
- Chrome's field data for the last 28 days: the experience of 75% of real visits for LCP, INP and CLS. It appears only when enough Chrome users visited the page, or else the whole site; this is what Google uses for page experience, so it outweighs the lab score when both exist.
- Opportunities (Reduce unused JavaScript −1.1 s)
- Lighthouse's estimate of the time each fix could save in the lab run, with the bytes involved. The figures are estimates for this one run; fix the largest ones first and test again.
Who Uses This
-
Performance Engineer
Re-run the check after every release and track the Core Web Vitals trend by hand to catch regressions early.
-
E-commerce Manager
Audit product pages monthly — every 100ms cut from LCP is measurable revenue on high-traffic categories.
-
SEO Specialist
Identify the worst-performing top 20 pages and prioritize them for the dev team's next sprint.
Common problems and how to fix them
-
Slow Largest Contentful Paint
Find the LCP element in the full report, make sure it is in the HTML rather than added by a script, preload it if it is an image or font, and remove render-blocking resources in <head>. A slow server response delays everything after it.
<script src="/js/app.js" defer></script> <script src="https://analytics.example/tag.js" async></script> <script type="module" src="/js/menu.js"></script> -
High Total Blocking Time
Ship less JavaScript: drop unused libraries, split code by page and load widgets only when needed. Long tasks over 50 ms are what block the page.
-
Layout shift
Give images, videos, ads and embeds a fixed size or aspect ratio, and avoid inserting content above what the visitor is reading.
<img src="/img/team-800.jpg" srcset="/img/team-400.jpg 400w, /img/team-800.jpg 800w, /img/team-1600.jpg 1600w" sizes="(max-width: 600px) 100vw, 800px" width="800" height="420" alt="Our support team" loading="lazy"> -
Unused JavaScript or CSS
Check the coverage of each file in the browser's developer tools, remove what no page uses and load the rest only on the pages that need it.
-
No real-visitor data
It appears once the page, or the site, has enough Chrome visits. Until then, rely on several lab runs and on the same measurements taken in your own analytics.
Frequently Asked Questions
- Lab data vs field data — what's the difference?
- Lab data is one synthetic run in a controlled environment. Field data (CrUX) is real-user metrics aggregated over 28 days. Google ranks based on field data; lab data is the iteration tool.
- Why does my score change between runs?
- Lighthouse has natural variance (CPU contention, network jitter). Google's ranking signal is field data, which averages thousands of real users — far more stable.
- What CWV thresholds should I target?
- Good = LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1. Anything above is "Needs Improvement" or "Poor" and counts against you.
- Mobile or desktop strategy?
- Mobile-first index = mobile is what Google uses for ranking. Always optimize mobile first; desktop is the secondary check.
- Does poor Core Web Vitals hurt rankings?
- It can. Google uses Core Web Vitals in its ranking systems, but relevance comes first — a fast page will not outrank a much more relevant one.
- Does it check text compression?
- Yes. If the page's HTML, CSS or JavaScript is served without compression such as gzip or Brotli, "Enable text compression" appears among the opportunities with the time it would save.
Sources
The documentation this tool and the explanations on this page are based on.
- About PageSpeed Insights — Google for Developers
- Lighthouse performance scoring — Chrome for Developers
- Largest Contentful Paint (LCP) — web.dev
- Interaction to Next Paint (INP) — web.dev
- Understanding Core Web Vitals and Google search results — Google Search Central