# Bulk Lighthouse & Core Web Vitals Auditor (no API key) (`ammartheawesome/lighthouse-auditor`) Actor

Audit a list of public URLs with Lighthouse on mobile and/or desktop. Flat, CSV-friendly rows: performance, accessibility, best-practices and SEO scores, LCP, CLS, TBT and a Core Web Vitals lab pass/fail. Runs Lighthouse itself, so no Google API key is needed.

- **URL**: https://apify.com/ammartheawesome/lighthouse-auditor.md
- **Developed by:** [Ammar Arquil](https://apify.com/ammartheawesome) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.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.

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 & Core Web Vitals Auditor

Give it a list of public web pages. It runs Google's open-source [Lighthouse](https://github.com/GoogleChrome/lighthouse) itself, on mobile and/or desktop, and returns one flat row per page and device. **No Google API key, no quota to manage.**

### What you get per row

| Field | Meaning |
|---|---|
| `performanceScore`, `accessibilityScore`, `bestPracticesScore`, `seoScore` | Lighthouse category scores, 0–100 |
| `lcpMs`, `cls`, `tbtMs` | Largest Contentful Paint, Cumulative Layout Shift, Total Blocking Time |
| `fcpMs`, `speedIndexMs`, `ttfbMs` | First Contentful Paint, Speed Index, server response time |
| `lcpGood`, `clsGood`, `tbtGood`, `coreWebVitalsLabPass` | Pass/fail against Google's "good" thresholds (LCP ≤ 2.5 s, CLS ≤ 0.1, TBT ≤ 200 ms) |
| `finalUrl`, `lighthouseVersion`, `fetchedAt`, `error` | Where it ended up, tool version, time, and the reason if the audit failed |

Rows download as CSV, Excel or JSON straight from the dataset.

### Read this before relying on the numbers

- These are **lab results** from a simulated device and network, not real-user (field) data. They are good for comparing pages and tracking changes, and will differ from what real visitors see.
- Lab data has no INP metric, so **Total Blocking Time** stands in for responsiveness in `coreWebVitalsLabPass`. A missing metric gives `null`, never a pass.
- Scores vary a little from run to run (typically a few points). Compare trends, not single runs.

### Price

Pay per event: **$0.01 per successful audit** (one URL on one device). Failed audits (timeouts, unreachable pages, pages that never paint) are returned with an `error` and are **not charged**. Auditing 100 URLs on mobile and desktop = 200 audits = $2.00. Each run also has a $0.00005 start fee (a twentieth of a cent). Set a maximum cost per run in Apify and the Actor stops when it is reached. No other fees.

### Input

- **URLs to audit**: up to 500 public pages, one per line.
- **Devices**: `mobile`, `desktop` or both.

Only public `http(s)` pages are accepted. Localhost, private networks, and URLs with embedded credentials are refused. Audit only sites you own or are allowed to test: Lighthouse loads each page like a normal browser visit.

### Limits

Each audit takes roughly 20–60 seconds and runs one at a time. The Actor always runs with at least 4 GB of memory (one full CPU): with less, Lighthouse's CPU-bound timings come out unrealistically slow, so smaller memory settings aren't offered. Pages behind logins are not supported. Redirects are followed by the browser, as for any visit.

### Acceptable use

Please don't use this Actor for, or on behalf of, gambling or betting, alcohol, adult or immodest content, interest-based lending, or deceptive marketing. It's built for ordinary business, research and personal use.

# Actor input Schema

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

Public web pages, one per line (up to 500). https:// is added if missing. Localhost and private-network addresses are refused.

## `strategies` (type: `array`):

mobile (slow-4G, phone-sized) and/or desktop. Each URL is audited once per device and each successful audit is one charged event.

## Actor input object example

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

# Actor output Schema

## `results` (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

```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",
        "https://www.wikipedia.org"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("ammartheawesome/lighthouse-auditor").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",
        "https://www.wikipedia.org",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("ammartheawesome/lighthouse-auditor").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",
    "https://www.wikipedia.org"
  ]
}' |
apify call ammartheawesome/lighthouse-auditor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,ammartheawesome/lighthouse-auditor"
        }
    }
}
```

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/yhYXDiof0jFVEc3II/builds/yLhSCK5k6gsrryZGW/openapi.json