Open on Apify Examples on GitHub
What it does
This is a bulk PageSpeed checker for people who are tired of pasting URLs into Google's one-at-a-time report. For each URL and device, Google runs Lighthouse on its own servers. You get one clean row back.
Each successful row includes Performance, Accessibility, Best Practices and SEO scores (0 to 100), lab metrics such as LCP, CLS, Total Blocking Time, FCP, Speed Index and TTFB, and the top 5 opportunities sorted by estimated time savings. When Chrome has enough real visitor data, you also get Core Web Vitals from the Chrome UX Report.
If a URL cannot be tested, the run writes an error row instead of pretending it succeeded. Those rows are free.
- Official Google API. No unofficial scraping of the PageSpeed report.
- Mobile, desktop, or both. Both means two rows, and two charges, per URL.
- Whole-site lists welcome. Pull URLs with the Sitemap URL Extractor, then paste the url column here.
Who it is for
It is for people who need the same numbers Google shows, for many pages at once.
- SEO agencies and consultants checking Core Web Vitals across client pages, then exporting to CSV or Sheets.
- Developers comparing Lighthouse performance before and after a release, or scheduling a regular run.
- Anyone automating this through the Apify API, MCP, Make, Zapier or our n8n node.
Price
$3 per 1,000 successful audits ($0.003 per URL on one device). That is the live Apify Store price as of November 11, 2026. Failed, invalid and timed-out audits are free.
500 URLs on mobile and desktop is 1,000 audits, or $3.00. The price is the same whether you request one Lighthouse category or all four.
Example input and output
Input
A short mobile run. Set strategy to both if you want two rows per URL.
{
"urls": [
"https://www.wikipedia.org/",
"https://web.dev/"
],
"strategy": "mobile",
"categories": [
"performance",
"accessibility",
"best-practices",
"seo"
]
}
Output
A shortened row from a real run on November 10, 2026, using the prefilled Wikipedia and web.dev URLs on mobile.
{
"url": "https://www.wikipedia.org/",
"strategy": "mobile",
"scores": {
"performance": 100,
"accessibility": 94,
"bestPractices": 100,
"seo": 100
},
"lab": {
"lcpMs": 1221,
"cls": 0.0005,
"tbtMs": 0
},
"fieldData": {
"overallCategory": "FAST"
},
"status": "ok"
}
Questions
Do I need a Google API key?
No. The tool calls Google's official PageSpeed Insights API for you. You can add your own key if you want, but it is not required.
What counts as one audit?
One URL on one device. A mobile check and a desktop check of the same page are two audits, and two charges if both succeed.
Can I check Core Web Vitals for many URLs at once?
Yes. Paste a list, pick mobile, desktop, or both, and download the rows as CSV, Excel or JSON. When Google has enough real-user data, you also get CrUX ratings for LCP, INP and CLS.
How do I test a whole site?
First pull the URL list with the Sitemap URL Extractor, then paste the url column here.
Are failed audits free?
Yes. Invalid URLs, timeouts and failed lookups are written as error rows and are not charged.