Bulk Lighthouse Audit: Core Web Vitals & SEO

Run Lighthouse on hundreds of URLs at once, on mobile and desktop. For every page you get the Performance, Accessibility, Best Practices, SEO and new Agentic Browsing scores, the Core Web Vitals lab metrics, the list of checks the page fails and a shareable HTML report. No API key needed, and failed URLs are free.

What it does

• 🚦 Five scores from 0 to 100: Performance, Accessibility, Best Practices, SEO and Agentic Browsing.
• ⏱️ Core Web Vitals lab metrics: Largest Contentful Paint (LCP), Cumulative Layout Shift (CLS), Total Blocking Time (TBT), First Contentful Paint (FCP), Speed Index and server response time. Each one is rated good, needs improvement or poor, with the same colors as the Lighthouse report.
• 🧾 A to-do list per page: the SEO, accessibility, best-practice and AI-agent checks the page fails, and the top performance opportunities with their estimated time savings.
• 📄 The full HTML report of every page, the same report as in Chrome DevTools, ready to send to a client. You also get a screenshot, and the raw JSON report if you want it.
• 🤖 Agentic Browsing: the category added in Lighthouse 13. It checks how well AI agents can read and use the page: the accessibility tree, llms.txt and WebMCP.
• 📱 Mobile and desktop in one run.
• 🎯 Steady scores:
  • Every audit runs in a fresh Chrome with two CPU cores of its own, so the scores come out close to those of Lighthouse on a normal computer.
  • Set Runs per page to 3 or 5 to keep the median run, as Lighthouse CI does.
• 🌍 Reports in 44 languages, from English and Spanish to Japanese and Vietnamese.
• 🧪 Block third parties, such as analytics, ads or chat, to see how fast the page is without them.
• ✅ Plain-English errors, for free: a page can fail because it does not load, answers with an error, shows a bot check or stays blank. You get one-line reasons such as "The server answered with HTTP 404.", and such pages cost nothing.

How to use it

1. Paste your URLs (one per line; example.com works too).
2. Choose Mobile, Desktop or both.
3. Click Start. Each page shows up in the Output tab with its scores. reportUrl opens its Lighthouse report.

Pricing

$20 per 1,000 audits ($0.02 per page and device), with pay-per-event pricing.

• One audit is one Lighthouse run of one URL on one device. For example, 100 pages on mobile and desktop are 200 audits and cost $4.
• With Runs per page set to 3, each page and device counts as 3 audits.
• You pay only for pages that were audited. A failed URL costs nothing.
• A tiny start fee is charged per run, about $0.0004 with the default 8 GB of memory.
• Set a maximum cost per run in the run options, and the Actor stops when it reaches it.

Input example

{
    "urls": ["https://apify.com", "example.com/pricing"],
    "devices": ["mobile", "desktop"],
    "categories": ["performance", "accessibility", "best-practices", "seo", "agentic-browsing"],
    "runsPerUrl": 1,
    "reportLanguage": "en-US"
}

All other settings are optional. See the Input tab for the full list.

Output example

One dataset row per URL and device (shortened):

{
    "url": "https://apify.com/",
    "finalUrl": "https://apify.com/",
    "device": "mobile",
    "status": "success",
    "performance": 59,
    "accessibility": 100,
    "bestPractices": 73,
    "seo": 85,
    "agenticBrowsing": 98,
    "fcpMs": 2320,
    "fcpRating": "needs-improvement",
    "lcpMs": 3033,
    "lcpRating": "needs-improvement",
    "tbtMs": 3459,
    "tbtRating": "poor",
    "cls": 0.001,
    "clsRating": "good",
    "speedIndexMs": 4895,
    "speedIndexRating": "needs-improvement",
    "ttfbMs": 89,
    "reportUrl": "https://api.apify.com/v2/key-value-stores/STORE_ID/records/apify-com-mobile-1a2b3c4d-report.html",
    "screenshotUrl": "https://api.apify.com/v2/key-value-stores/STORE_ID/records/apify-com-mobile-1a2b3c4d-screenshot.jpg",
    "jsonReportUrl": null,
    "opportunities": [
        { "id": "bootup-time", "title": "Reduce JavaScript execution time", "displayValue": "7.6 s", "savingsMs": 3800 }
    ],
    "failedAudits": [
        { "category": "best-practices", "id": "third-party-cookies", "title": "Uses third-party cookies" }
    ],
    "runs": 1,
    "warnings": [],
    "lighthouseVersion": "13.5.0",
    "benchmarkIndex": 2605,
    "durationSecs": 22.2,
    "auditedAt": "2026-10-28T03:13:48.486Z",
    "error": null
}

A failed URL has "status": "failed", empty scores and a reason in error, such as "The page did not show any content." The Output tab has two views: Scores and Core Web Vitals.

Why are my scores different from PageSpeed Insights?

• Lab scores depend on the machine and network that run the test. PageSpeed Insights runs Lighthouse on Google's own servers. This Actor runs Lighthouse with its default settings, on two dedicated CPU cores per audit. Expect a few points of difference, and more on heavy pages full of JavaScript.
• Scores vary from run to run, wherever Lighthouse runs. For steadier numbers, set Runs per page to 3 and the Actor keeps the median run.
• PageSpeed Insights also shows field data, the speed real Chrome users saw over 28 days. This Actor measures lab data only.

benchmarkIndex in the output tells how fast the CPU was during the audit.

Use it from your code or an AI agent

Run the Actor and get the results in one call:

curl -X POST "https://api.apify.com/v2/acts/Hpbt~bulk-lighthouse-audit/run-sync-get-dataset-items?token=YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"urls": ["https://example.com"], "devices": ["mobile"]}'

• JavaScript or Python: use the Apify client (see the API tab for ready-made code).
• AI agents: the Actor works through the Apify MCP server.
• No-code: connect it to Zapier, Make, n8n, Google Sheets or Slack through Apify integrations.

Tips

• Monitor your sites: schedule a weekly run in Apify and send the dataset to Google Sheets or Slack to see when a score drops.
• Client reports: send reportUrl. The report opens in any browser and needs no Apify account.
• What do third parties cost? Run the page twice, the second time with Block these requests set to *google-analytics.com*, *googletagmanager.com* or *doubleclick.net*, and compare.
• More pages at once: the default 8 GB of memory audits one page at a time. 16 GB audits 2 pages at once, and 32 GB audits 4.

Limitations

• No logging in, no CAPTCHA solving and no bot-protection bypass. Pages that answer with a bot check are reported as failed, and they are free.
• Local and private network addresses (localhost, 10.x, 192.168.x…) are blocked.
• Lab data only. There is no field data from real users (Chrome UX Report).
• Proxies are not used, because a proxy would make every page look slower than it is.

FAQ

Which Lighthouse version does it use? Lighthouse 13.5 with the Chrome in Apify's image. lighthouseVersion in every row tells the version.

Is this an official Google tool? No. Lighthouse is Google Chrome's open-source auditing tool (Apache 2.0 license). This Actor runs it for you at scale and is not affiliated with Google.

How long are the reports kept? As long as your Apify plan keeps run storage. Download them or send them on with an integration if you need them longer.

Something looks wrong? Open an issue in the Issues tab with the URL and the input you used.