Free PageSpeed bulk tests runner

Scores you can trust,
no server required.

One PageSpeed run swings every time you hit it. Test each URL 3–10 times to cut the noise and get scores you can trust — median, average, and CrUX field data, all in your browser.

01No backend
Every test runs straight from your browser.
02Key stays local
Your PageSpeed API key is stored only in your browser — never on our servers.
03Lab + CrUX
Lab runs and CrUX field data together in one place.
Why should I run multiple tests?

A single Lighthouse run is a snapshot, not a score — it can swing ±20 points depending on server load, network jitter, and CPU throttling variance. Running 3–10 tests and reading the median or average gives you a stable baseline you can actually act on and track over time.

✕
One test
Score: 74 → unreliable, could be 60 or 90 next run
~
3 tests · median
Score: 78 → directionally correct
✓
5 tests · median
Score: 77 → confident, actionable
How it works
1Paste your URL
Enter any public URL. The tool sends requests directly from your browser.
2Configure runs
Select the required metrics, strategy, and number of tests for each strategy.
3Get reliable results
View CrUX field data from real users alongside your lab runs — median and average side by side.
Configuration
Pagespeed API key
Saved automatically — stays in localStorage, never leaves your browser.
Runs Runs sets how many times each strategy is launched. A single strategy runs 3 tests. Picking both Mobile and Desktop doubles that to 6 tests. 3
110
Strategy Strategy picks the device profile PageSpeed emulates when loading the page. Mobile throttles the CPU and network to mimic a mid-range phone (Google's default and what ranking is based on). Desktop tests on a faster wired connection. Pick Both to run each URL on both profiles and compare them side by side.
Cache warmup The first request to a page often hits a cold cache, so the CDN builds and stores the response on the fly — making that run look slower than the site really is. Cache warmup fires one throwaway preflight request first to prime the CDN, then the counted runs measure warm, cache-hit performance for more stable, true-to-life numbers.
Fires one extra preflight — warms CDN before counting.
Report metricsChoose which metrics appear in the report
Perf score metrics
Other metrics
FAQ Still curious? Ask a question →