# Bulk Lighthouse Audit - Core Web Vitals, SEO, Accessibility (`tinyrex/lighthouse-audit`) Actor

Run real Google Lighthouse audits on many URLs, no API key or PageSpeed quota: performance, accessibility, best practices and SEO scores, Core Web Vitals and top issues. $0.01/audit, no compute fees; failed pages free.

- **URL**: https://apify.com/tinyrex/lighthouse-audit.md
- **Developed by:** [TinyRex](https://apify.com/tinyrex) (community)
- **Categories:** SEO tools, Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 lighthouse audits

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Bulk Lighthouse Audit: Core Web Vitals, SEO and Accessibility Scores for Many URLs

Run **real Google Lighthouse audits** on a list of URLs in one run, with **no API key and no PageSpeed Insights quota**. Each page gets its **performance, accessibility, best practices and SEO scores**, the lab **Core Web Vitals** (LCP, CLS, TBT, FCP, Speed Index) and a short list of the **top issues to fix**. **$0.01 per audit ($10 per 1,000)**, no compute fees on top, and **pages that fail to load are free**.

Lighthouse (the open-source auditing tool from Google Chrome, Apache-2.0) runs inside the Actor in headless Chrome, so you are not limited by the shared keyless PageSpeed API quota that often returns HTTP 429.

### What you get per URL

| Field | Example |
|---|---|
| `performance`, `accessibility`, `bestPractices`, `seo` | 92, 88, 100, 90 (0-100, same scale as PageSpeed Insights) |
| `largestContentfulPaintMs`, `cumulativeLayoutShift`, `totalBlockingTimeMs` | 2100, 0.02, 150 |
| `firstContentfulPaintMs`, `speedIndexMs`, `serverResponseTimeMs`, `totalByteWeight` | 1200, 1800, 180, 845000 |
| `topIssues` | `[{"title": "Render blocking requests", "category": "performance", "savingsMs": 300}, ...]` |
| `reportHtmlUrl` (optional) | Public link to the full Lighthouse HTML report |
| `error` | Why an audit failed (failed audits are free) |

Export to CSV, Excel, JSON or Google Sheets from the dataset, or call it from the API, Make, Zapier or n8n.

### Use cases

- **SEO agencies:** score a client's top 50 landing pages before and after a fix, in one CSV.
- **Developers:** check Core Web Vitals across a whole sitemap (pair with [Sitemap URL Extractor](https://apify.com/tinyrex/sitemap-scraper)).
- **Lead generation:** find prospects with slow or inaccessible websites and show them the numbers.
- **Monitoring:** schedule a weekly run and track scores over time.

### How to use

1. Paste URLs or bare domains into **URLs**.
2. Pick **Mobile** (the PageSpeed Insights default), **Desktop**, or **Both** (2 audits per URL).
3. Optionally limit **Categories**, turn on **Save HTML report**, and start the run.

Example input:

```json
{
  "urls": ["https://example.com", "https://apify.com"],
  "formFactor": "mobile",
  "categories": [],
  "maxIssues": 10,
  "saveHtmlReport": true
}
```

### Pricing

Pay per event: **$0.01 per successful Lighthouse audit** (Silver and Gold plans get automatic discounts). Platform compute is included. **Free:** invalid URLs, DNS errors, refused connections, timeouts, HTTP 4xx/5xx pages and pages Lighthouse cannot score. With "Both" devices, each device counts as one audit. Set a max charge per run and the Actor stops cleanly when it is reached.

### Notes and limits

- Audits run one at a time so CPU contention doesn't distort performance scores; expect about 15-30 seconds per page (heavy pages up to ~2 minutes).
- Scores are **lab data** from simulated throttling, like the Lighthouse part of PageSpeed Insights. Real-user field data (CrUX) is not included.
- Scores vary a few points between runs on any Lighthouse setup; compare trends, not single points.
- Audit only sites you own or have permission to test. Pages behind a login or CAPTCHA are not audited.
- Not affiliated with or endorsed by Google. Lighthouse is a trademark of Google LLC.

### FAQ

**Is this the same as Google PageSpeed Insights?** It runs the same open-source Lighthouse engine that PageSpeed Insights uses for its lab section, but on Apify instead of Google's API, so no API key or quota is needed.

**Why is my score different from PageSpeed Insights?** Hardware, network location and Lighthouse version differ, so scores can differ by a few points. Use the same Actor setup for before/after comparisons.

**Can I audit a whole website?** Yes: get all page URLs with [Sitemap URL Extractor](https://apify.com/tinyrex/sitemap-scraper) and paste them in.

### Related actors

- [SEO On-Page Audit](https://apify.com/tinyrex/seo-on-page-audit): titles, meta tags, headings, canonical, hreflang and JSON-LD at HTTP speed.
- [Broken Link Checker](https://apify.com/tinyrex/broken-link-checker): find broken links and redirects across a site.
- [Bulk Website Screenshot](https://apify.com/tinyrex/bulk-website-screenshot): full-page screenshots of many URLs.
- [Tech Stack Detector](https://apify.com/tinyrex/tech-stack-detector): which CMS, analytics and frameworks a site uses.

# Actor input Schema

## `urls` (type: `array`):

Pages to audit. Full URLs or bare domains (example.com becomes https://example.com). Duplicates are removed. One charge per successful audit; unreachable pages, HTTP errors and Lighthouse errors are free.

## `formFactor` (type: `string`):

Lighthouse preset. Mobile matches Google PageSpeed Insights' default (throttled Moto G-class phone). 'Both' runs mobile and desktop and counts as 2 audits per URL.

## `categories` (type: `array`):

Lighthouse categories to run. Empty = all four. Fewer categories make audits a bit faster; the price is the same.

## `maxIssues` (type: `integer`):

How many failing audits (sorted by estimated time savings) to list in topIssues. 0 = none.

## `saveHtmlReport` (type: `boolean`):

Store the full Lighthouse HTML report for each audit and add a public link (reportHtmlUrl). Same report you'd get in Chrome DevTools.

## `saveJsonReport` (type: `boolean`):

Store the full raw Lighthouse JSON result (lhr) for each audit (reportJsonUrl). Large: ~0.5-2 MB per page.

## `pageTimeoutSecs` (type: `integer`):

Max time Lighthouse waits for a page to load.

## `maxAudits` (type: `integer`):

Stop after this many successful audits. 0 = no limit (the run's max charge still applies).

## Actor input object example

```json
{
  "urls": [
    "https://example.com"
  ],
  "formFactor": "mobile",
  "categories": [],
  "maxIssues": 10,
  "saveHtmlReport": false,
  "saveJsonReport": false,
  "pageTimeoutSecs": 60,
  "maxAudits": 0
}
```

# Actor output Schema

## `audits` (type: `string`):

One row per URL and device.

## `reports` (type: `string`):

Key-value store with optional HTML/JSON reports.

## `summary` (type: `string`):

Totals for the run.

# 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

```javascript
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"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tinyrex/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

```python
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"] }

# Run the Actor and wait for it to finish
run = client.actor("tinyrex/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

```bash
echo '{
  "urls": [
    "https://example.com"
  ]
}' |
apify call tinyrex/lighthouse-audit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tinyrex/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/pMTPtVeIFMSeqn4xE/builds/JULwbHL4DEZruGSPc/openapi.json