# Bulk Lighthouse & Core Web Vitals Checker (No API Key) (`impenetrable_sesame/bulk-lighthouse-core-web-vitals`) Actor

Run Google Lighthouse on hundreds of landing pages at once. Performance, SEO, accessibility scores, LCP, CLS, TBT, top speed fixes and PPC landing-page flags. Mobile and desktop. No API key needed.

- **URL**: https://apify.com/impenetrable_sesame/bulk-lighthouse-core-web-vitals.md
- **Developed by:** [Degeore Marketing](https://apify.com/impenetrable_sesame) (community)
- **Categories:** SEO tools, Marketing, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

## 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 Checker (No API Key)

Run **Google Lighthouse** on a whole list of landing pages in one go, on mobile, desktop, or both. You get Performance, SEO, Accessibility, and Best Practices scores, Core Web Vitals lab metrics, the top speed fixes for each page, and **PPC landing-page flags**. No Google API key or quota limits.

Slow landing pages waste paid clicks. Use this to audit every ad destination URL across an account, compare competitors' pages, or track speed over time on a schedule.

### What you get per URL and device

- **Scores (0-100):** performance, SEO, accessibility, best practices
- **Metrics:** LCP, FCP, Total Blocking Time, CLS, Speed Index, server response time
- **Top 5 opportunities** with estimated savings in ms (e.g. unused JavaScript, image sizes, render-blocking resources)
- **Ad landing-page flags**, e.g. "LCP over 4.0s (Core Web Vitals poor)" or "Total Blocking Time over 600ms: heavy JS (often tag bloat)"
- Optional **real-user (CrUX) field data** if you add your own free PageSpeed Insights API key

### How it works

The Actor runs the open-source Lighthouse engine in headless Chrome inside Apify, so you don't need an API key. Lab results vary a little from run to run, as they do in Chrome DevTools.

#### Input example

```json
{
  "startUrls": [{ "url": "https://www.example.com" }, { "url": "https://www.allbirds.com" }],
  "strategy": "both",
  "categories": ["performance", "seo", "accessibility", "best-practices"]
}
```

#### Output example (real Apify run, 2026-10-18, trimmed)

```json
{
  "url": "https://www.allbirds.com",
  "strategy": "mobile",
  "scores": { "performance": 32, "seo": 100 },
  "metrics": { "lcpMs": 14905, "fcpMs": 2802, "tbtMs": 2563, "cls": 0, "speedIndexMs": 10807, "ttfbMs": 16 },
  "adLandingPageFlags": [
    "LCP over 4.0s (Core Web Vitals \"poor\"): slow landing pages lose paid clicks.",
    "Total Blocking Time over 600ms: heavy JS (often tag bloat)."
  ],
  "topOpportunities": [{ "id": "unused-javascript", "title": "Reduce unused JavaScript", "savingsMs": 790 }]
}
```

### Pricing

Pay per event: **$0.02 per audit** (one URL on one device) plus **$0.001 per GB of memory per run** (default 4 GB = $0.004). 100 URLs on mobile = $2.00 + $0.004. Failed URLs are **not charged** and are listed in `FAILED_URLS`.

### FAQ

**Why not just use the PageSpeed Insights API?** Its keyless quota runs out fast, and bulk use needs a Google Cloud key. This Actor runs Lighthouse itself. If you want field data too, add your own key.

**How long does it take?** About 5-75 seconds per URL per device, depending on how heavy the page is. Pages are audited one at a time for stable results.

# Actor input Schema

## `startUrls` (type: `array`):

List of pages to process. Paste URLs or upload a text/CSV file.

## `strategy` (type: `string`):

Audit as a mobile device, desktop, or both. Each URL × device is one audit.

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

Lighthouse categories to run. Performance only is fastest.

## `psiApiKey` (type: `string`):

Optional. Your own Google PageSpeed Insights API key, to add real-user (CrUX) field data. Lab data works without it.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.example.com"
    }
  ],
  "strategy": "mobile",
  "categories": [
    "performance",
    "seo",
    "accessibility",
    "best-practices"
  ]
}
```

# Actor output Schema

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

All result items in the default dataset (JSON; use format=csv or xlsx to export).

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

// Run the Actor and wait for it to finish
const run = await client.actor("impenetrable_sesame/bulk-lighthouse-core-web-vitals").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 = { "startUrls": [{ "url": "https://www.example.com" }] }

# Run the Actor and wait for it to finish
run = client.actor("impenetrable_sesame/bulk-lighthouse-core-web-vitals").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 '{
  "startUrls": [
    {
      "url": "https://www.example.com"
    }
  ]
}' |
apify call impenetrable_sesame/bulk-lighthouse-core-web-vitals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,impenetrable_sesame/bulk-lighthouse-core-web-vitals"
        }
    }
}
```

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/euZVjprGz8K6P4tDt/builds/9q49TinQwXpNARsvi/openapi.json