Bulk PageSpeed Insights & Core Web Vitals Checker (Sitemap)
Pricing
Pay per event
Bulk PageSpeed Insights & Core Web Vitals Checker (Sitemap)
Audit hundreds of URLs or a whole sitemap with Google's official PageSpeed Insights API: Lighthouse scores, lab LCP/CLS/TBT, real-user CrUX Core Web Vitals (LCP, INP, CLS) and top fixes, mobile + desktop, with pass/fail thresholds for monitoring.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Lindenbyte Studio
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Features
Share
Bulk PageSpeed Insights & Core Web Vitals Checker
Run Google PageSpeed Insights on hundreds of pages at once, or point it at a sitemap.xml and audit the whole site. You get one flat row per URL and device with Lighthouse scores, lab metrics (LCP, CLS, TBT, FCP, Speed Index, TTI), real-user Core Web Vitals from the Chrome UX Report (LCP, INP, CLS, FCP, TTFB at p75), Google's Core Web Vitals pass/fail assessment and the top fixes ranked by estimated time saved.
It uses Google's official PageSpeed Insights API v5, so the numbers match what you see on pagespeed.web.dev.
Why this one
- Sitemap input: give
https://yoursite.com/sitemap.xml(sitemap indexes and.xml.gzwork too) and cap it withmaxUrls. - Mobile and desktop in one run:
strategy: bothgives two rows per URL. - Clean field data: CrUX p75 values and FAST/AVERAGE/SLOW categories as flat columns, CLS already divided by 100, plus a flag when Google only has origin-level data for the page.
- Pass/fail thresholds for monitoring: set e.g.
minPerformanceScore: 80,maxLcpMs: 2500or "require passing Core Web Vitals" and each row getspassedand a readablefailedCheckslist. Schedule it weekly and alert on failures. - Failed pages are free: unreachable pages come back as rows with
errorset and are not charged.
Use cases
- SEO agencies: Core Web Vitals report for a client's whole sitemap in one CSV.
- Developers: catch performance regressions after a deploy with a scheduled run and thresholds.
- Site owners: find which templates (product pages, blog posts) have poor LCP or CLS, and what to fix first.
- Competitor benchmarking: compare your pages with competitors' on mobile and desktop.
Input
| Field | What it does |
|---|---|
urls | Pages to audit (example.com is read as https://example.com/) |
sitemapUrl | Sitemap or sitemap index; its pages are added to the list |
maxUrls | Cap on unique URLs (default 100) |
strategy | mobile (default), desktop or both |
categories | performance (default), plus optional seo, accessibility, best-practices |
apiKey | Optional: your own free Google PSI key. Without it the Actor's built-in key is used |
concurrency | Parallel audits (default 4, max 10) |
minPerformanceScore, minSeoScore, minAccessibilityScore, minBestPracticesScore | Optional score thresholds (0-100) |
maxLcpMs, maxCls, maxTbtMs | Optional lab metric thresholds |
requireFieldCwvPass | Fail rows whose real-user Core Web Vitals do not pass |
Output (one item per URL and device)
Real values from a Lighthouse 13 mobile audit of web.dev (field data shortened):
{"url": "https://web.dev/","finalUrl": "https://web.dev/","strategy": "mobile","performanceScore": 73,"seoScore": 92,"accessibilityScore": 90,"bestPracticesScore": 77,"lcpMs": 2866, "fcpMs": 2866, "tbtMs": 618, "speedIndexMs": 4136, "ttiMs": 13997, "serverResponseMs": 346, "cls": 0,"fieldDataScope": "url","fieldOriginFallback": false,"fieldOverallCategory": "AVERAGE","fieldLcpP75Ms": 2600, "fieldLcpCategory": "AVERAGE","fieldInpP75Ms": 295, "fieldInpCategory": "AVERAGE","fieldClsP75": 0.3, "fieldClsCategory": "SLOW","fieldFcpP75Ms": 2032, "fieldTtfbP75Ms": 842,"fieldCwvAssessment": "FAILED","topOpportunity": "Render-blocking requests (~1600 ms)","opportunities": [{ "id": "render-blocking-insight", "title": "Render-blocking requests", "estimatedSavingsMs": 1600, "estimatedSavingsBytes": null, "displayValue": "Est savings of 1,610 ms" },{ "id": "unused-css-rules", "title": "Reduce unused CSS", "estimatedSavingsMs": 750, "estimatedSavingsBytes": 133084, "displayValue": "Est savings of 130 KiB" }],"passed": false,"failedChecks": ["Performance score 73 < 80", "Lab LCP ms 2866 > 2500"],"lighthouseVersion": "13.6.0","reportUrl": "https://pagespeed.web.dev/analysis?url=https%3A%2F%2Fweb.dev%2F&form_factor=mobile","error": null,"fetchedAt": "2026-11-13T07:13:23.769Z"}
A run summary (counts, threshold pass/fail, problems) is saved as SUMMARY in the key-value store.
Field notes: fieldDataScope is url when Chrome UX Report has data for that exact page, origin when Google only has site-wide data (fieldOriginFallback: true), and null for low-traffic sites with no CrUX data. fieldCwvAssessment follows Google's rule: LCP, INP and CLS must all be "good" at p75.
Pricing
Pay per result: you are charged for each successful audit (one URL on one device). Pages Google cannot load are returned with an error and are not charged. Set a max cost on the run and the Actor stops when it is reached.
Limits
- Each audit takes Google 10-40 seconds; 100 URLs on both devices take a few minutes at the default concurrency.
- Lighthouse lab scores vary a few points between runs; that is normal for Lighthouse, not this Actor.
- Pages behind logins, or that block Google's Lighthouse bot, return an error row.
- Google's keyless PSI quota is currently zero, so a key is always used: ours by default, or yours if you add one (25,000 audits/day free: https://developers.google.com/speed/docs/insights/v5/get-started#APIKey). If a key's daily quota runs out, the run stops with a clear message and keeps the results so far.
Not affiliated with Google. PageSpeed Insights, Lighthouse and Chrome UX Report are Google products.