Skip to content
Rankora
Free account · 3 live checks/day

PageSpeed and Lighthouse Audit

Enter a URL and choose mobile or desktop: the tool queries Google's PageSpeed Insights API and clearly separates the lab test from real-user data.

Temporarily unavailable

This tool depends on an external data provider that is not connected right now. Nothing is charged. Please try again later.

Privacy and cost

This tool runs a live check on our servers. Free accounts get 3 live checks per day in total across all such tools. We keep your report in your account so you can delete it any time.

How it works

  1. You choose the strategy (mobile or desktop) and the Lighthouse categories to compute.
  2. Our server calls the PageSpeed Insights v5 API; the result is cached for 6 hours and 429/5xx errors are retried.
  3. You get two distinct blocks: lab data (Lighthouse: scores, metrics, opportunities) and field data (CrUX: 75th percentile over 28 days).

Example

A page can score 62 on performance in the lab test while showing a field LCP of 4.2 s: these are two different measurements, shown in two blocks.

What the result means

The Lighthouse score comes from a single simulation on Google's servers and varies between runs: it is not your visitors' experience. CrUX field data reflects real Chrome users but only exists when the URL or origin has enough traffic.

Common problems this tool helps with

  • Mistaking the lab score for real Core Web Vitals.
  • Render-blocking resources or heavy images delaying LCP.
  • High blocking time caused by too much JavaScript.
  • Mobile and desktop gaps missed for lack of a separate test.

Frequently asked questions

Why is the tool unavailable?

It depends on a PageSpeed Insights API key configured on the server. Without one the tool is disabled rather than returning fake values.

Why two different results?

The lab simulates a given device and network; the field aggregates real visitors. Google uses field data for Core Web Vitals.

Are results real-time?

They can be up to 6 hours old: we cache an analysis to save API quota.