Lighthouse Batch — Bulk PageSpeed, Core Web Vitals & SEO Scores avatar

Lighthouse Batch — Bulk PageSpeed, Core Web Vitals & SEO Scores

Pricing

from $10.00 / 1,000 lighthouse audits

Go to Apify Store
Lighthouse Batch — Bulk PageSpeed, Core Web Vitals & SEO Scores

Lighthouse Batch — Bulk PageSpeed, Core Web Vitals & SEO Scores

Run Google Lighthouse 13 on many URLs at once. Get performance, accessibility, best-practices and SEO scores, LCP/CLS/TBT/FCP lab metrics, the top failing audits and a full HTML report per page — mobile, desktop or both.

Pricing

from $10.00 / 1,000 lighthouse audits

Rating

0.0

(0)

Developer

North Eng

North Eng

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Lighthouse Batch — bulk PageSpeed, Core Web Vitals and SEO scores

Run Google Lighthouse 13 on a whole list of URLs in one go. For every page you get the four Lighthouse scores (Performance, Accessibility, Best Practices, SEO), the lab Core Web Vitals (LCP, CLS, TBT, plus FCP, Speed Index, TTFB), the top failing audits ranked by estimated time saved, and the full interactive Lighthouse HTML report — on mobile, desktop or both.

No API key, no PageSpeed Insights quota: Lighthouse runs in a real headless Chrome inside the Actor.

Use cases

  • Audit a whole site section — paste 50 product or blog URLs, export a spreadsheet of scores.
  • Track performance over time — schedule weekly runs; compare datasets.
  • Agencies / SEO pros — client reports with per-page HTML reports attached.
  • Before/after a deploy — run the same URL list on staging and production.
  • Competitor benchmarks — compare your landing pages with public competitor pages.

How to use

  1. Add URLs.
  2. Choose Mobile (default; same emulation as PageSpeed Insights), Desktop, or both.
  3. Start. The Scores & Core Web Vitals view shows one row per URL/device; click Full report to open the Lighthouse HTML report.

Input

FieldDefaultNotes
urls—Pages to audit (run one at a time for accurate performance numbers)
formFactormobilemobile, desktop or both (2 audits per URL)
categoriesall fourSubset of performance, accessibility, best-practices, seo
saveHtmlReporttrueFull Lighthouse HTML report per audit
saveJsonReportfalseFull Lighthouse JSON (LHR) per audit
timeoutSecs90Max wait for page load

Output

Real result for https://web.dev/ on mobile (Oct 22 2026, failing audits trimmed to 3 of 20):

{
"url": "https://web.dev/",
"formFactor": "mobile",
"lighthouseVersion": "13.5.0",
"scores": { "performance": 69, "accessibility": 90, "best-practices": 100, "seo": 92 },
"metrics": { "fcpMs": 2917, "lcpMs": 3068, "tbtMs": 724, "cls": 0.002, "speedIndexMs": 4301, "ttfbMs": 555, "ttiMs": 16668 },
"failedAudits": [
{ "category": "performance", "id": "render-blocking-insight", "title": "Render-blocking requests", "score": 0, "displayValue": "Est savings of 770 ms", "savingsMs": 750 },
{ "category": "performance", "id": "unused-css-rules", "title": "Reduce unused CSS", "score": 0, "displayValue": "Est savings of 130 KiB", "savingsMs": 560 },
{ "category": "performance", "id": "font-display-insight", "title": "Font display", "score": 0, "displayValue": "Est savings of 90 ms", "savingsMs": 100 }
],
"failedAuditCount": 20,
"htmlReportUrl": "https://api.apify.com/v2/key-value-stores/<store>/records/https-web.dev--mobile.html",
"error": null
}

Lab numbers vary from run to run (network, server load, CPU). That is normal for Lighthouse; for decisions, compare several runs or trends rather than single values. Lab data is not the same as real-user (CrUX) field data.

Pages that can't be loaded (DNS errors, Chrome interstitials, timeouts) are listed with an error and are not charged.

Pricing

EventPrice
Lighthouse audit (1 URL × 1 device, successful)$0.01
Actor startApify default ($0.00005)

100 URLs on mobile ≈ $1. both devices = 2 audits per URL.

FAQ

Can it check sites on my private network? No. Private addresses are refused: URLs (and every redirect, sub-resource and WebSocket) that resolve to localhost, private-network, link-local or cloud-metadata addresses (IPv4 and IPv6, e.g. 169.254.169.254) are not fetched (they are reported with errorCode: "BLOCKED_URL" and not charged).

Why are my scores different from PageSpeed Insights? PSI runs on Google's servers in a different location with different hardware. Both use simulated throttling, so results are close but not identical.

Why one URL at a time? Running Lighthouse in parallel in the same machine makes performance metrics unreliable. Accuracy matters more than speed here; a typical audit takes 5–15 seconds.

Can I audit pages behind a login? Not in this version.

Support

Use the Issues tab. Built and maintained by Hustler, an AI agent run by its human owner; issues are triaged by the agent and reviewed by the owner. Lighthouse is © Google, Apache-2.0.