Bulk PageSpeed Insights Checker: Lighthouse & Core Web Vitals avatar

Bulk PageSpeed Insights Checker: Lighthouse & Core Web Vitals

Pricing

from $5.00 / 1,000 page auditeds

Go to Apify Store
Bulk PageSpeed Insights Checker: Lighthouse & Core Web Vitals

Bulk PageSpeed Insights Checker: Lighthouse & Core Web Vitals

Bulk-audit URLs or a whole sitemap with Google PageSpeed Insights: Lighthouse scores, lab metrics, real-user Core Web Vitals (CrUX) with pass/fail, and the top 3 fixes, mobile and desktop in one CSV-ready row. Optional monitoring flags real changes. Failed pages are free.

Pricing

from $5.00 / 1,000 page auditeds

Rating

0.0

(0)

Developer

Michael Schönherr

Michael Schönherr

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Categories

Security

Limited permissions

Share

Audit a list of URLs or a whole sitemap with Google's official PageSpeed Insights and get one CSV-ready row per URL, mobile and desktop side by side:

  • Lighthouse scores: Performance, Accessibility, Best Practices, SEO (0–100)
  • Lab metrics: LCP, FCP, TBT, CLS, Speed Index
  • Real-user Core Web Vitals (CrUX): LCP, INP, CLS, FCP, TTFB at the 75th percentile, with a clear passed / failed result and whether the data is for the page or the whole site
  • Top 3 fixes with the estimated time saved, e.g. "Render-blocking requests (~1.5 s)"
  • A link to the full Google report for every URL

Monitoring built in: give the run a name and schedule it. Every run is compared with the previous one, and significantChange tells you when something really moved (10+ points or a changed Core Web Vitals result), instead of alerting on Lighthouse's normal noise.

No setup: an API key is built in. Pages that cannot be audited are free.

Who uses it

You areYou use it to
SEO / web agencyMonthly speed reports for all clients, sitemap-wide audits, proof of improvements
Shop or site ownerFind the slowest templates and the fixes with the biggest impact
Developer teamCatch performance regressions after releases with scheduled monitoring
AI agentsCall it as an MCP tool: "Which of my 200 pages fail Core Web Vitals on mobile?"

Output (one row per URL)

Columns are prefixed with mobile_ and desktop_:

FieldExampleMeaning
url, finalUrlhttps://www.example.com/input and URL after redirects
statusokok, partial (one device failed), error, invalid
mobile_performance … mobile_seo62, 91, 96, 100Lighthouse category scores
mobile_lcpMs, mobile_fcpMs, mobile_tbtMs, mobile_cls, mobile_speedIndexMs4322, 1840, 350, 0.045, 3901lab metrics
mobile_fieldLcpMs, mobile_fieldInpMs, mobile_fieldCls, mobile_fieldFcpMs, mobile_fieldTtfbMs3100, 180, 0.08real users, p75 (CrUX)
mobile_fieldScopeurl / originpage-level data or whole-site fallback
mobile_cwvAssessmentfailedpassed, failed, no-field-data
mobile_topIssues["Render-blocking requests (~1.5 s)", …]biggest savings first
mobile_performanceChange, significantChange-18, trueonly with monitoring
reportUrlhttps://pagespeed.web.dev/analysis?url=…full Google report
lighthouseVersion, fetchedAt, errorstransparency

The Overview table shows the most important columns; export everything as CSV, Excel, JSON or via API.

Core Web Vitals thresholds used (p75, "good"): LCP ≤ 2.5 s, INP ≤ 200 ms, CLS ≤ 0.1, as defined by Google on web.dev. Sites with too little traffic have no real-user data; you then still get all lab metrics and no-field-data.

Pricing

Pay per audit, no subscription. One audit = one URL on one device.

EventPrice
page-audited$5.00 per 1,000 audits (a URL on mobile + desktop = 2 audits = $0.010)
Page could not be loaded, API error, invalid inputfree

Set a maximum cost per run in Apify; the Actor stops cleanly when it is reached.

Input example

{
"urls": ["https://www.example.com", "apify.com"],
"sitemapUrl": "https://www.example.com/sitemap.xml",
"maxSitemapUrls": 100,
"strategies": ["mobile", "desktop"],
"monitorName": "client-a",
"locale": "en"
}

Tips

  • Weekly monitoring: schedule the Actor with a monitorName and connect a Slack or email integration that triggers when significantChange is true.
  • Scores vary a few points between runs because Lighthouse simulates a real device. Compare trends and use significantChange, not single points.
  • Audit titles in your language: set locale, e.g. de for German.

FAQ

Do I need a Google API key? No. You can add your own key for very large volumes; it is stored encrypted.

Why is a page marked error? Google's Lighthouse could not load it (for example: blocked for bots, 404, timeout). The reason is in errors, and you are not charged.

Something wrong or missing? Open an issue on the Actor page. We usually answer within one business day.


Kurz auf Deutsch

Prüft beliebig viele URLs oder eine ganze Sitemap mit Google PageSpeed Insights: Lighthouse-Werte, Labormesswerte, echte Core Web Vitals (CrUX) mit Bestanden/Nicht bestanden und die 3 wichtigsten Verbesserungen, mobil und Desktop in einer Zeile. Mit Monitoring-Funktion für echte Veränderungen. Nicht prüfbare Seiten sind kostenlos. Tipp: locale: "de" für deutsche Audit-Titel.


Anbieter / Impressum (Angaben gemäß § 5 DDG): Michael Schönherr · Am Spiegelwald 1 · 08344 Grünhain-Beierfeld · Deutschland · E-Mail: m.schoenherr80@gmail.com