# Page Speed Audit (Lighthouse) - Performance & SEO Scores (`cuantic_data/page-speed-lighthouse-audit`) Actor

Runs a real Google Lighthouse audit (performance, SEO, accessibility, best practices) on a public page and returns scores plus Core Web Vitals (LCP, CLS, TBT, FCP) and the top opportunities to fix. Same open-source engine Chrome DevTools uses - no login, no third-party API keys.

- **URL**: https://apify.com/cuantic\_data/page-speed-lighthouse-audit.md
- **Developed by:** [Cuantic Data](https://apify.com/cuantic_data) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 page 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](#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

## Page Speed Audit (Google Lighthouse) — Performance, SEO & Accessibility Scores

Runs a real Google Lighthouse audit (the same engine behind Chrome
DevTools/PageSpeed Insights) on a public page and returns the 4 category
scores (0-100), 6 Core Web Vitals metrics, and a prioritized list of what to
fix first. No third-party API keys, no login.

### What it does

- Launches a real headless Chrome and runs Lighthouse against the given
  URL.
- Returns **0-100 scores** for `performance`, `seo`, `accessibility` and
  `best-practices`.
- Returns the **key metrics**: Largest Contentful Paint, First Contentful
  Paint, Total Blocking Time, Cumulative Layout Shift, Speed Index and Time
  to Interactive.
- Returns the **10 lowest-scoring opportunities** (score < 0.9), sorted from
  worst to best, with the real Lighthouse audit `id` so you can look up the
  official fix in Lighthouse's documentation.

### Who it's for

- Freelancers/agencies that need a speed and technical SEO report before a
  pitch or after a change.
- Teams that want to run the audit in their own pipeline (CI, pre-deploy)
  without installing Lighthouse or maintaining Chrome.

### Input

| Field | Type | Required | Description |
|---|---|---|---|
| `url` | string | Yes | One page per run (pay-per-event = 1 event per page). |
| `device` | string | No (default `mobile`) | `mobile` or `desktop`. |
| `categories` | array | No | Subset of `performance`, `seo`, `accessibility`, `best-practices`. If omitted, runs all 4. |

```json
{ "url": "https://example.com", "device": "mobile" }
```

### Output

```json
{
  "url": "https://example.com",
  "device": "mobile",
  "categoriesAudited": ["performance", "seo", "accessibility", "best-practices"],
  "scores": { "performance": 93, "seo": 80, "accessibility": 96, "best-practices": 96 },
  "metrics": {
    "largest-contentful-paint": { "score": 1, "displayValue": "0.8 s", "numericValue": 773.5 },
    "speed-index": { "score": 0.32, "displayValue": "7.0 s", "numericValue": 7031.6 }
  },
  "opportunities": [
    { "id": "meta-description", "title": "Document does not have a meta description", "category": "seo", "score": 0 }
  ],
  "opportunityCount": 6,
  "lighthouseVersion": "13.5.0",
  "auditedAt": "2026-09-20T03:30:55.498Z"
}
```

### Pricing

Pay-per-event, provisional. Starting reference: USD 0.05 per page audited
(`03-plan.md` §2) — this is the most compute-heavy of the 12 Actors (it
launches a real browser), so its margin gets extra scrutiny before the
final price is set (see `build/README.md` → "Calibrar precios").

### How to call it

```bash
curl "https://api.apify.com/v2/acts/cuantic-data~page-speed-lighthouse-audit/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}'
```

### Terms and limits

See [`TERMS.md`](./TERMS.md): uses Google Lighthouse (Apache License 2.0),
running against the user's own page, with no third-party data involved.

### What it does NOT do

- The `desktop` profile changes the `formFactor` but doesn't hand-tune every
  Lighthouse network/CPU throttling setting — disclosed in `TERMS.md`, not a
  hidden bug.
- It doesn't fix anything automatically: it gives you the diagnosis, not the
  fix.
- It can take 15-40 seconds per page (it launches a real browser) — don't
  use it for very high-frequency monitoring of the same URL.

### FAQ

**Why does the score shift slightly between runs of the same page?**
Lighthouse measures real load times; there's normal network and CPU
variability between runs, same as with PageSpeed Insights. It's not an
Actor error.

**Found a bug?**
Email `cuanticwindows@gmail.com` — we reply within 72 hours.

***

See `build/README.md` for how to run tests and publish this Actor.

# Actor input Schema

## `url` (type: `string`):

Public http(s) URL of a single page.

## `device` (type: `string`):

Lighthouse applies a different network/CPU profile depending on the device. 'mobile' is Lighthouse's and Google PageSpeed Insights' default.

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

Subset of Lighthouse categories. If left empty, runs all 4: performance, seo, accessibility, best-practices.

## Actor input object example

```json
{
  "url": "https://example.com",
  "device": "mobile"
}
```

# Actor output Schema

## `results` (type: `string`):

Scores, Core Web Vitals metrics and opportunities for the audited URL.

## `runSummary` (type: `string`):

Audited URL and the 0-100 score per category.

# 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 = {
    "url": "https://example.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("cuantic_data/page-speed-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 = { "url": "https://example.com" }

# Run the Actor and wait for it to finish
run = client.actor("cuantic_data/page-speed-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 '{
  "url": "https://example.com"
}' |
apify call cuantic_data/page-speed-lighthouse-audit --silent --output-dataset

```

## MCP server setup

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