Bulk Lighthouse & Core Web Vitals Audit (Apify Actor)

npx add-mcp 'https://mcp.apify.com/?actors=pennydata/bulk-lighthouse-audit'

Bulk Lighthouse & Core Web Vitals Audit (pennydata/bulk-lighthouse-audit) Actor

Run real Lighthouse on a list of URLs, mobile or desktop. One flat row per URL: performance, SEO, accessibility and best-practices scores, LCP, CLS, TBT, FCP and top failed audits. $0.008 per audited URL, failed audits free.

• URL: https://apify.com/pennydata/bulk-lighthouse-audit.md
• Developed by: Penny Data (community)
• Stats: 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
• User rating: No ratings yet

Pricing

$8.00 / 1,000 url auditeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the API section below.

Each client library has reference documentation the quickstart does not restate: JavaScript/TypeScript (npm install apify-client) and Python (pip install apify-client).

README

Bulk Lighthouse, WCAG & EAA Accessibility Audit

The first 3 URLs of each run are free. After that you are charged only for URLs that were audited successfully; failed, blocked or timed-out audits are returned with an error and are free. Flat $0.008 per audited URL (per strategy).

This is a bulk Lighthouse and accessibility audit: automated WCAG-related checks, Core Web Vitals and SEO scores for many pages in one run, useful as a first pass for European Accessibility Act (EAA) work. Paste a list of public URLs and get one flat row per URL from a real Lighthouse run (Google's open-source Lighthouse, run inside the Actor, not the rate-limited PageSpeed Insights API): performance, SEO, accessibility and best-practices scores, the Core Web Vitals lab metrics (LCP, CLS, TBT, FCP, Speed Index) and the five worst failed audits. Export as CSV, Excel or JSON, or schedule it to track a site over time.

Pricing

Event	Price	When it is charged
url-audited	$0.008	One completed Lighthouse audit of one URL with one strategy, from the 4th URL of a run onward. strategy: both means two audits (two rows) per URL.

The first 3 URLs of each run (both strategies of those URLs, if strategy is both) are not charged, so a 3-URL test run has no url-audited charge. 100 URLs on mobile cost 97 x $0.008 = $0.776. Set Max cost per run (USD) (maxCostUsd) and the run stops at exactly that many billed audits. Apify's own platform fee/credits are not part of this table.

Input

Field	Meaning
urls	Public http(s) pages to audit
sitemapUrl	Optional sitemap.xml or sitemap index; its pages (up to maxUrls) are audited
strategy	mobile (default), desktop or both
categories	performance, accessibility, best-practices, seo (performance is always run)
maxUrls, maxCostUsd	Safety caps
concurrency	Parallel Chrome processes (default 2)
timeoutSecs	Per-audit timeout (default 120)

Example input:

{ "urls": ["https://example.com", "https://www.wikipedia.org"], "strategy": "mobile" }

Output (one row per URL)

{
  "url": "https://www.wikipedia.org/",
  "strategy": "mobile",
  "performance": 99, "seo": 100, "accessibility": 95, "bestPractices": 100,
  "lcpMs": 1410, "cls": 0.001, "tbtMs": 0, "fcpMs": 1410, "speedIndexMs": 1410,
  "failedAudits": [{ "id": "link-text", "title": "Links do not have descriptive text", "score": 0, "displayValue": "1 link found" }],
  "lighthouseVersion": "12.8.2"
}

A SUMMARY record in the key-value store lists audits billed, failures and cost.

Sample output

Five rows from a 10-URL test run of this Actor (mobile strategy, default settings, run locally before publishing). Lighthouse scores vary from run to run, so expect your numbers to differ somewhat.

url	performance	seo	accessibility	bestPractices	lcpMs	cls	tbtMs	fcpMs
https://www.wikipedia.org/	99	100	95	100	1410	0.001	0	1410
https://www.python.org/	72	83	75	100	5394	0	37	3577
https://developer.mozilla.org/	84	100	96	96	3658	0	0	2374
https://github.com/	28	100	100	96	22774	0.072	1599	13391
https://www.bbc.com/	38	92	88	57	7441	0.049	3123	1536

The full test run audited 10 URLs with 0 failures. Each row also carries the five worst failed audits, speedIndexMs and lighthouseVersion.

Bulk accessibility check for the European Accessibility Act

The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025 to many consumer-facing digital services in the EU, and web accessibility is commonly assessed against WCAG. This Actor helps you see, for many pages at once, which automated accessibility checks fail:

• Every row has an accessibilityFailures list: [{ "id": "color-contrast", "title": "...", "count": 4 }], one entry per Lighthouse accessibility audit that scored below 100% on that page, with the number of affected elements where Lighthouse reports them.
• Set sitemapUrl (a sitemap.xml or sitemap index) instead of listing pages by hand. The Actor reads up to maxUrls page URLs (default 50) from it and audits each one.
• Export the result as CSV or Excel to sort pages by the number of failing checks.

Example input: { "sitemapUrl": "https://example.com/sitemap.xml", "maxUrls": 50, "categories": ["accessibility"] }

Automated checks (Lighthouse uses the axe-core rules) cover only part of WCAG; many requirements need manual review, and this output is not a compliance certificate or legal advice.

Honest limits

• These are lab (simulated throttling) results from a datacenter machine, like Lighthouse in Chrome DevTools. They are not Chrome UX Report field data, and scores vary a few points between runs, more for slow or heavy pages.
• Sites that block datacenter traffic (HTTP 403 or bot walls) cannot be audited; they come back as a free error row.
• Expect roughly 10 to 30 seconds per URL.
• Only pages you provide are loaded, like a normal browser visit. Lighthouse is Apache-2.0 licensed software by Google; this Actor is not affiliated with or endorsed by Google.

Built with AI assistance (Claude, by Anthropic) and tested on real sites before release.

Related Actors

• Website Tech Stack Detector
• Bulk Domain WHOIS & DNS Lookup

Actor input Schema

urls (type: array):

Public http(s) pages to audit. One Lighthouse run per URL (and per strategy).

sitemapUrl (type: string):

Public sitemap.xml (or sitemap index) URL. Its page URLs are audited, up to Max URLs. When set, the example URLs above are ignored; any other URLs you list are added.

strategy (type: string):

mobile (emulated phone, throttled), desktop, or both (two rows per URL, two charges).

categories (type: array):

Lighthouse categories to score. Performance is always measured for Core Web Vitals.

maxUrls (type: integer):

Safety cap on unique URLs processed (also caps pages taken from the sitemap).

maxCostUsd (type: number):

Hard spending guard. The run stops once this many dollars of audits have been billed ($0.008 each). Leave empty for no cap beyond Max URLs.

concurrency (type: integer):

Parallel Chrome instances. Use 1-2 for stable scores; more is faster but adds timing noise.

timeoutSecs (type: integer):

An audit that exceeds this is reported as failed and not charged.

Actor input object example

{
  "urls": [
    "https://example.com",
    "https://www.wikipedia.org"
  ],
  "strategy": "mobile",
  "categories": [
    "performance",
    "accessibility",
    "best-practices",
    "seo"
  ],
  "maxUrls": 50,
  "concurrency": 2,
  "timeoutSecs": 120
}

Actor output Schema

results (type: string):

No description

summary (type: string):

No description

API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

JavaScript example

import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "https://example.com",
        "https://www.wikipedia.org"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("pennydata/bulk-lighthouse-audit").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

Python example

from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": [
        "https://example.com",
        "https://www.wikipedia.org",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("pennydata/bulk-lighthouse-audit").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

CLI example

echo '{
  "urls": [
    "https://example.com",
    "https://www.wikipedia.org"
  ]
}' |
apify call pennydata/bulk-lighthouse-audit --silent --output-dataset

MCP server setup

{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pennydata/bulk-lighthouse-audit"
        }
    }
}

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an Authorization: Bearer <APIFY_API_TOKEN> header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/qtc2P7tCe6yAu3Uxj/builds/owpYaWy0k4hIBgqhr/openapi.json