# Bulk Lighthouse Audit: median of 3 runs, Core Web Vitals (`weio/lighthouse-mobile-median-audit`) Actor

Bulk Lighthouse and PageSpeed-style website speed audit: compare URLs with the median of 1-3 mobile or desktop runs, not a noisy one-off. Returns performance, SEO, accessibility, Core Web Vitals (LCP, CLS, TBT) and top fixes. Failed runs are free.

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

## Pricing

from $10.00 / 1,000 lighthouse runs

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 Mobile Audit (median of 3 runs)

Runs Google Lighthouse on each website in your list, with mobile emulation (or desktop), and returns the **median run** of up to 3 runs per site. A single Lighthouse run can swing 10+ points; the median is what Google itself recommends reporting.

### Output (one row per site)

- `performance`, `accessibility`, `bestPractices`, `seo` (0-100)
- Core Web Vitals lab values: `lcpMs`, `fcpMs`, `tbtMs`, `cls`, `speedIndexMs`
- `performanceAllRuns`: the score of every run, so you can see the spread
- `topFixes`: up to 5 Lighthouse opportunities ranked by estimated time saved
- `error` when a site could not be audited (not charged)

### Example row (real run, zingermans.com, mobile, 3 runs)

```json
{
  "url": "https://zingermans.com/",
  "device": "mobile",
  "runsCompleted": 3,
  "performanceAllRuns": [52, 31, 32],
  "performance": 32,
  "lcpMs": 8589,
  "tbtMs": 3563,
  "topFixes": [{"fix": "Eliminate render-blocking resources", "estimatedSavingsMs": 3571}]
}
```

The spread (52 vs 31) is why one run is not enough: the median is the number to report or compare.

### Input

- `websites`: domains or URLs, one per line (up to 500 per run)
- `runs`: 1-3 (default 3)
- `formFactor`: `mobile` (default) or `desktop`

### Pricing

Pay per event: one `lighthouse-run` per completed Lighthouse run. Runs that fail are free. Set `runs` to 1 for a cheaper single-run scan.

### Notes

- Lab data from the Apify cloud, not field data (CrUX). Scores differ from PageSpeed Insights because hardware and network differ; compare sites within one run.
- Public pages only. Nothing is submitted or logged into.

# Actor input Schema

## `websites` (type: `array`):

Domains or URLs, one per line (max 500 per run). A bare domain is audited as https://<domain>/.

## `runs` (type: `integer`):

Lighthouse scores vary between runs; with 3 runs you get the median run (by performance score), as Google recommends. Each run is one charged event.

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

mobile = Lighthouse's default Moto G Power emulation with slow 4G throttling; desktop = desktop preset.

## Actor input object example

```json
{
  "websites": [
    "zingermans.com"
  ],
  "runs": 3,
  "formFactor": "mobile"
}
```

# Actor output Schema

## `siteRows` (type: `string`):

The default dataset with one row per audited website.

# 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 = {
    "websites": [
        "zingermans.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("weio/lighthouse-mobile-median-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 = { "websites": ["zingermans.com"] }

# Run the Actor and wait for it to finish
run = client.actor("weio/lighthouse-mobile-median-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 '{
  "websites": [
    "zingermans.com"
  ]
}' |
apify call weio/lighthouse-mobile-median-audit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,weio/lighthouse-mobile-median-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/ruhsOAXJtSrCLY10O/builds/pm9ifkmMsajpBaRTY/openapi.json