TL;DR
You can test page speed for many URLs without a command line by using a hosted bulk tool. Paste a domain or sitemap, let the tool find the pages, and it runs Lighthouse on each one on mobile and desktop. Pick a tool that tests every page, repeats runs, groups shared issues and keeps history.
Key takeaways
- PageSpeed Insights tests one URL at a time; bulk tools run the same kind of test across a whole list.
- The useful features are page discovery, both devices, repeated runs, grouped issues and history.
- Check how a tool counts usage (per URL, per check or per audit) before comparing prices.
- Free tools are fine for a one-off look; monitoring needs schedules and alerts.
Steps
- 01 Pick the URLs Use your domain or sitemap URL so every indexable page is included, rather than a hand-picked list.
- 02 Start a hosted bulk test Paste the domain or sitemap into a hosted bulk Lighthouse tool and choose mobile, desktop or both.
- 03 Review grouped results Sort issues by the number of pages they affect and start with the template-level fixes.
- 04 Re-test and schedule Re-run the affected pages after each fix and set a weekly or monthly schedule to catch regressions.
PageSpeed Insights is the quickest way to test one page. Paste a URL, wait a few seconds, and you get Lighthouse lab results plus real-user data from the Chrome UX Report. The catch is that it tests one URL at a time. To test a whole site, you either script it or use a tool built for bulk testing.
Why not just script it?
Developers often loop over a sitemap with the Lighthouse CLI or call the PageSpeed Insights API. It works, but you take on the plumbing:
- Installing and updating Node.js, Chrome and Lighthouse
- Managing API keys and quotas, or a machine to run Chrome on
- Retrying timeouts and crashes, and skipping pages behind bot challenges
- Parsing hundreds of JSON reports into something you can act on
- Storing history so you can see whether things got better
If you are a site owner, marketer or SEO consultant, none of that is the job you set out to do.
What a bulk testing tool should do
When you compare hosted tools, look for these features:
| Feature | Why it matters |
|---|---|
| Page discovery | Reads your sitemap or crawls the site, so you test every page, not just the ones you remember |
| Mobile and desktop | The two often have different problems; mobile is usually worse |
| Consistent test conditions | Lighthouse varies with the machine it runs on; the same throttling and machine profile for every page keeps results comparable |
| Grouped issues | Pages from the same template share problems; you want one fix, not 140 reports |
| Field data | CrUX shows what real visitors experience where Google has enough data |
| History and schedules | Lets you prove a fix worked and catch regressions |
| Fair metering | Check whether failed pages and bot-blocked pages count against your usage |
How to run a bulk test with AiroPages
- Go to the AiroPages homepage and enter your domain or sitemap URL.
- AiroPages reads your sitemaps and robots.txt, skips noindex pages and duplicates, and groups pages by template.
- Choose a one-time report, and AiroPages counts your pages and shows the exact price, or pick a monthly plan. See pricing.
- Pay and create your login. The scan starts right away and results appear as each page finishes.
- Review grouped issues, ranked by how many pages each one affects, and copy the fixes for your developer or coding agent.
AiroPages bills per URL scan: one page tested on mobile and desktop, so 200 pages is 200 URL scans. Failed and blocked scans are credited back to your balance as URL scans.
Free tools vs paid tools
Free web tools are good for a quick look at a few hundred URLs. They usually test one device at a time, cap the number of URLs, and do not keep history. Open-source tools such as Unlighthouse are free and powerful, but need Node.js. Paid hosted tools earn their price when you need every page, both devices, history, schedules and alerts. Our comparison pages list the differences.
After the test
Fix the issues that affect the most pages first, then re-test those pages. If you work with a coding agent, read using Claude Code to fix Lighthouse issues.
Published · Last updated