PSI Median Runner
Runs PageSpeed Insights several times for mobile and desktop, reports the median of each metric and how much the runs varied, then ranks the fixes that failed in most runs.
Runs
Each device's runs go one at a time so they don't load the server together. Mobile and desktop run side by side. Each run usually takes 15–40 seconds.
Sharing a result
PageSpeed Insights only creates a pagespeed.web.dev link when a test is run on its own website. Tests run through the API, like the ones here, don't get one. To share the exact run behind your median:
- Click Open full report on mobile or desktop. The run opens in Google's Lighthouse Viewer, which shows the same report you'd see on PageSpeed Insights.
- In the viewer, open the ⋮ menu and choose Save as Gist. Sign in with GitHub once. You get a permanent link (googlechrome.github.io/lighthouse/viewer/?gist=…) that anyone can open.
- Or choose Save as HTML in the same menu and send the file. If you need a link, you can upload it anywhere, e.g. your own site.
For context in your report, include the median and the run scores shown above. A single run can't show how much the score moves between tests.
Where the weight comes from
Taken from the median mobile run (desktop if mobile wasn't tested). Files are grouped by the plugin, theme or third-party service that loaded them.
Fixes, ranked by impact
Only issues that failed in at least half the runs are listed.
How to use it
- Paste the page URL and your API key, then click Run tests.
- Read the median score. That's the number to report, because a single PSI run can be off by 10 points or more.
- Work through the fixes from the top. Each one names the files responsible and which plugin or theme loaded them.
- Click Copy report for Claude and paste it into a chat if you want a deeper look at a specific site.