Bulk PageSpeed & Core Web Vitals Checker
Pricing
from $20.00 / 1,000 page audits
Bulk PageSpeed & Core Web Vitals Checker
Run Google PageSpeed Insights (Lighthouse) on hundreds of URLs or a whole sitemap. Get performance, SEO, accessibility scores, Core Web Vitals (lab + real-user CrUX) and top fixes per page.
Pricing
from $20.00 / 1,000 page audits
Rating
0.0
(0)
Developer
Avi Som
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Security
Limited permissionsShare
Test hundreds of pages, or an entire sitemap, with Google PageSpeed Insights (Lighthouse) in one run. For every URL you get Performance, SEO, Accessibility and Best-practices scores, lab metrics (LCP, CLS, TBT, FCP, Speed Index, TTFB), real-user Core Web Vitals from Chrome UX Report data with a pass/fail verdict, and the top 5 fixes with estimated savings.
No API key or setup needed. Paste URLs or a sitemap and click Start.
Why use it
- Bulk: audit a whole site from its
sitemap.xml(sitemap indexes supported) instead of testing pages one by one on pagespeed.web.dev. - Mobile and desktop in the same run.
- Real-user data: Core Web Vitals (LCP, INP, CLS) at p75 from CrUX, falling back to origin-level data for low-traffic pages, with a Google-threshold passed/failed verdict.
- Actionable: top fixes per page, such as "Reduce unused JavaScript: 900 ms / 200 KB".
- Monitor over time: schedule it weekly, send results to Google Sheets, Slack or Looker Studio, and catch regressions after deploys.
- Summary: average scores per device, how many pages pass Core Web Vitals, and the 10 slowest pages (
OUTPUTrecord).
Who it's for
SEO agencies running client audits, developers checking a release, e-commerce teams tracking speed, and anyone comparing their site to competitors.
Input
| Field | What it does |
|---|---|
urls | Pages to test (https:// added if missing). |
sitemapUrls | Sitemap or sitemap-index URLs; pages are added to the list. |
maxUrlsFromSitemaps | Cap on pages taken from sitemaps (default 50). |
strategies | mobile, desktop or both. Each URL × device = one result. |
categories | Any of performance, accessibility, best-practices, seo. |
includeOpportunities | Include top 5 fixes per page (default on). |
locale | Language of audit titles (e.g. en, de). |
apiKey | Optional: your own free Google PageSpeed API key for very large jobs. |
{"sitemapUrls": ["https://example.com/sitemap.xml"],"maxUrlsFromSitemaps": 200,"strategies": ["mobile", "desktop"]}
Output (one row per URL × device)
{"url": "https://web.dev/","finalUrl": "https://web.dev/","strategy": "mobile","performanceScore": 48,"accessibilityScore": 90,"bestPracticesScore": 96,"seoScore": 92,"lcpMs": 7804,"fcpMs": 7804,"tbtMs": 287,"cls": 0.121,"speedIndexMs": 7804,"ttiMs": 19934,"ttfbMs": 3,"totalPageKb": 3631,"fieldDataSource": "url","fieldLcpMs": 3069,"fieldInpMs": 233,"fieldCls": 0.01,"fieldFcpMs": 3079,"fieldTtfbMs": 1784,"fieldOverall": "SLOW","coreWebVitals": "failed","opportunities": [{"id": "unused-javascript","title": "Reduce unused JavaScript","savingsMs": 3450,"savingsKb": 878},{"id": "unused-css-rules","title": "Reduce unused CSS","savingsMs": 1190,"savingsKb": 140}],"lighthouseVersion": "13.6.0","analyzedAt": "2026-11-05T15:30:02.018Z","reportUrl": "https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fweb.dev%2F&form_factor=mobile"}
Export to CSV/Excel/JSON or connect with Google Sheets, Zapier, Make or n8n.
Pricing
Pay per result: you pay only for successfully analyzed pages (one URL on one device = one result). Failed pages (e.g. the site is down) are listed in the summary and are not charged. Set a maximum cost per run and it stops cleanly.
FAQ
Are scores identical to pagespeed.web.dev? Yes. It uses the same Google PageSpeed Insights API. Lab scores naturally vary a few points between runs.
Why is real-user data sometimes empty? Google only has Chrome UX Report data for pages and sites with enough traffic. Lab metrics are always included.
How long does it take? Each audit takes about 10–30 seconds on Google's side, and several run in parallel, so roughly 100 pages take about 10 minutes.
Something wrong? Open an issue with the URL and it will be fixed quickly.