# Bulk Core Web Vitals & PageSpeed Audit (`webdatatools/core-web-vitals-audit`) Actor

Bulk Core Web Vitals and PageSpeed audit: Lighthouse performance, SEO and accessibility scores, LCP, CLS, INP, TBT and the top fixes — one row per URL and device.

- **URL**: https://apify.com/webdatatools/core-web-vitals-audit.md
- **Developed by:** [Murat Uzun](https://apify.com/webdatatools) (community)
- **Categories:** SEO tools, Developer tools, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### What is Bulk Core Web Vitals & PageSpeed Audit?

Bulk Core Web Vitals & PageSpeed Audit is an Apify Actor that runs Google PageSpeed Insights (Lighthouse plus Chrome UX Report field data) over a whole list of URLs and returns **one flat row per URL and device** — Lighthouse performance, SEO, accessibility and best-practices scores, LCP, CLS, INP, TBT, FCP, Speed Index and TTFB, a pass/fail on Google's Core Web Vitals thresholds, and the five biggest fixes Lighthouse found. It is the same data pagespeed.web.dev shows you one URL at a time, for 500 URLs in one run, straight into a dataset, CSV or your API.

### What data does the Core Web Vitals audit extract?

Every row mixes **lab data** (a fresh Lighthouse run on Google's hardware) with **field data** (real Chrome users, trailing 28 days, when the origin has enough traffic to be in CrUX):

| Field                                                    | Type    | Description                                                                                                           |
| -------------------------------------------------------- | ------- | --------------------------------------------------------------------------------------------------------------------- |
| `url` / `finalUrl`                                       | string  | Submitted URL and the URL Lighthouse measured after redirects                                                         |
| `strategy`                                               | string  | `mobile` or `desktop`                                                                                                 |
| `performanceScore`                                       | integer | Lighthouse performance, 0–100                                                                                         |
| `accessibilityScore` / `bestPracticesScore` / `seoScore` | integer | 0–100, `null` when the category was not requested                                                                     |
| `lcpMs` / `cls` / `tbtMs`                                | number  | Lab Largest Contentful Paint, Cumulative Layout Shift, Total Blocking Time                                            |
| `fcpMs` / `speedIndexMs` / `ttiMs` / `ttfbMs`            | integer | Lab First Contentful Paint, Speed Index, Time to Interactive, server response time                                    |
| `fieldData`                                              | object  | Real-user `lcpMs`, `cls`, `inpMs`, `fcpMs`, `ttfbMs`, `overallCategory` — `null` when CrUX has no data for the origin |
| `passesCoreWebVitals`                                    | boolean | True when field LCP ≤ 2500 ms, CLS ≤ 0.1 and INP ≤ 200 ms                                                             |
| `labGrade`                                               | string  | `good` (≥ 90), `needs-improvement` (≥ 50), `poor`                                                                     |
| `topOpportunities`                                       | array   | Up to 5 failed Lighthouse opportunities as `{id, title, savingsMs}`, biggest saving first                             |
| `lighthouseVersion` / `fetchedAt`                        | string  | Lighthouse version and the timestamp of Google's run                                                                  |
| `error` / `scrapedAt`                                    | string  | Why a URL has no metrics (e.g. a rate limit), and when the row was produced                                           |

### How to use Bulk Core Web Vitals & PageSpeed Audit

1. Get a **free Google PageSpeed Insights API key** (one click, no billing: https://developers.google.com/speed/docs/insights/v5/get-started) and paste it into **Google PageSpeed Insights API key**. Without a key Google's shared anonymous quota is almost always exhausted and every row comes back with an HTTP 429 `error`.
2. Paste your URLs into **URLs to audit** — one per row, full URLs, the exact pages you care about.
3. Pick the **Device strategy** (`mobile` is what Google ranks on; `both` returns two rows per URL) and any extra **Lighthouse categories**.
4. Leave **Max concurrency** at 2–3, click **Start**, then download JSON, CSV, Excel or HTML from the Output tab.

### Example input

```json
{
    "urls": ["https://apify.com", "https://example.com"],
    "apiKey": "YOUR_FREE_PSI_API_KEY",
    "strategy": "mobile",
    "categories": ["performance", "seo"],
    "maxConcurrency": 2
}
```

### Example output

```json
{
    "url": "https://apify.com",
    "finalUrl": "https://apify.com/",
    "strategy": "mobile",
    "performanceScore": 62,
    "seoScore": 92,
    "lcpMs": 4219,
    "cls": 0.041,
    "tbtMs": 891,
    "ttfbMs": 310,
    "fieldData": { "lcpMs": 2212, "cls": 0.04, "inpMs": 152, "ttfbMs": 612, "overallCategory": "AVERAGE" },
    "passesCoreWebVitals": true,
    "labGrade": "needs-improvement",
    "topOpportunities": [
        { "id": "unused-javascript", "title": "Reduce unused JavaScript", "savingsMs": 2150 },
        { "id": "render-blocking-resources", "title": "Eliminate render-blocking resources", "savingsMs": 780 }
    ],
    "lighthouseVersion": "12.2.1",
    "fetchedAt": "2026-09-12T15:28:41.903Z",
    "error": null,
    "scrapedAt": "2026-09-12T15:30:00.000Z"
}
```

### Input parameters

| Parameter        | Type            | Default                 | Description                                             |
| ---------------- | --------------- | ----------------------- | ------------------------------------------------------- |
| `urls`           | array           | `["https://apify.com"]` | Page URLs to audit, one row per URL × device            |
| `apiKey`         | string (secret) | none                    | Free Google PSI API key — 25,000 requests/day           |
| `strategy`       | enum            | `mobile`                | `mobile`, `desktop` or `both`                           |
| `categories`     | array           | `["performance"]`       | `performance`, `accessibility`, `best-practices`, `seo` |
| `locale`         | string          | `en`                    | Language of Lighthouse titles                           |
| `maxConcurrency` | integer         | 2                       | Parallel PSI requests (1–5)                             |

### Pricing

Pay-per-event: **$0.005 per audited URL × device** ($5 per 1,000 rows), plus a negligible $0.00005 actor-start fee, platform usage included. All the heavy lifting happens on Google's servers, so compute stays tiny — auditing 1,000 URLs costs $5 and a few cents of usage. `strategy: "both"` doubles the row count, so it doubles the price. Set **Maximum cost per run** and the Actor trims the list to what the budget covers instead of overspending.

### Bulk Core Web Vitals audit vs. pagespeed.web.dev and monitoring subscriptions

pagespeed.web.dev tests one URL per click and keeps no history. SEO monitoring suites (SpeedCurve, DebugBear, Semrush Site Audit) sell monthly seats. This Actor is pay-per-event with no subscription: run 500 prospect homepages overnight, schedule the same 50 URLs weekly to watch a regression, or call it from your own code — results land in a dataset you can join to anything else.

### Using Bulk Core Web Vitals & PageSpeed Audit with AI agents and MCP

The Actor is pay-per-event with limited permissions, the two requirements for an Actor to be callable through the Apify MCP server at mcp.apify.com. An agent passes `urls` (and ideally `apiKey`) and gets flat, numeric rows back — no HTML, no nesting to unpack — and the same call works from n8n, Make, Zapier or LangChain through Apify's integrations.

### FAQ

**Do I need a Google API key?**
Runs of up to 5 URLs work without a key on a shared demo quota, so you can try the Actor straight away. For bigger batches paste your own free PageSpeed Insights API key (25,000 requests per day) into the API key field - Google's anonymous quota is shared by everyone and is usually exhausted.

**Do I really need an API key?** For anything beyond a smoke test, yes. The keyless quota is shared by every anonymous caller on the internet and is usually spent; those rows come back with `error` set and null metrics instead of failing the run. A key is free and allows 25,000 requests/day.

**Why is `fieldData` null?** CrUX only has data for origins with enough real Chrome traffic. Small sites get lab data only — `passesCoreWebVitals` is then `null`, because INP cannot be measured in a lab run.

**Why does the score differ between two runs of the same URL?** Lighthouse is a live measurement on shared hardware; performance scores move a few points between runs. Field data is stable, lab data is directional.

**How long does a run take?** 10–30 seconds per URL × device, two or three in parallel — about 5–10 minutes per 100 URLs.

**Is this legal?** The Actor only calls Google's public PageSpeed Insights API and collects no personal data.

**Can I export to CSV or Excel?** Yes, from the Output tab or the API, and every field is flat except `fieldData` and `topOpportunities`.

### Related Actors

Part of the **webdatatools** web-intelligence suite — every Actor is pay-per-event, runs without
proxies or a headless browser, and returns one clean row per entity:

**Website & domain intelligence**

- [Website Contact & Social Extractor](https://apify.com/webdatatools/contact-extractor) — e-mails, phones and social profiles per domain
- [Website Tech Stack Detector](https://apify.com/webdatatools/tech-stack-detector) — CMS, e-commerce, analytics, pixels and payments per domain
- [Domain DNS & Email Security Checker](https://apify.com/webdatatools/dns-email-security-checker) — SPF, DKIM, DMARC, MX provider, registrar and domain age
- [Domain Security Audit](https://apify.com/webdatatools/domain-security-audit) — TLS expiry, security headers, redirect chain, robots and llms.txt
- [Subdomain Finder (Certificate Transparency)](https://apify.com/webdatatools/subdomain-finder) — every subdomain seen in CT logs, with a live DNS check
- [On-Page SEO Audit](https://apify.com/webdatatools/seo-page-audit) — title, meta, headings, links, images and schema issues per page
- [Sitemap URL Extractor & Change Monitor](https://apify.com/webdatatools/sitemap-extractor) — every sitemap URL, or new and removed pages between runs
- [Wayback Machine Snapshot & Page Change Tracker](https://apify.com/webdatatools/wayback-page-diff) — how a page changed over time, or every archived snapshot

**Content for AI, LLMs and RAG**

- [AI Web Search & Read](https://apify.com/webdatatools/ai-web-search) — a query turned into clean Markdown from the top search results
- [Website to Markdown Crawler for LLM & RAG](https://apify.com/webdatatools/website-to-markdown) — any site as clean Markdown per page, no browser
- [Article & News Extractor](https://apify.com/webdatatools/article-extractor) — clean article text, author, date and Markdown per URL
- [Structured Data & JSON-LD Extractor](https://apify.com/webdatatools/structured-data-extractor) — Schema.org and Open Graph data from any page
- [Google News Scraper](https://apify.com/webdatatools/google-news-scraper) — news results by keyword, topic or site
- [Press Release Monitor](https://apify.com/webdatatools/press-release-monitor) — PR Newswire, Business Wire and GlobeNewswire releases

**Search, video and social**

- [Google Search Results Scraper](https://apify.com/webdatatools/google-search-scraper) — organic SERP results per keyword and country
- [YouTube Comments Scraper](https://apify.com/webdatatools/youtube-comments-scraper) — comments and replies with likes, no API key
- [YouTube Channel Latest Videos](https://apify.com/webdatatools/youtube-channel-videos) — the latest 15 videos of any channel from RSS
- [YouTube Channel Videos Scraper](https://apify.com/webdatatools/youtube-channel-scraper) — a channel's full video, shorts and stream list
- [YouTube Search Results Scraper](https://apify.com/webdatatools/youtube-search-scraper) — videos, channels and playlists per query
- [YouTube Video Details Scraper](https://apify.com/webdatatools/youtube-video-details) — views, likes, description, tags and chapters per video
- [Apple Podcasts Lookup & Episodes Scraper](https://apify.com/webdatatools/podcast-lookup) — podcast metadata and episodes from iTunes and RSS
- [Bluesky Scraper](https://apify.com/webdatatools/bluesky-scraper) — posts, profiles, followers and threads from the AT Protocol API

**Leads, jobs and company data**

- [Company 360](https://apify.com/webdatatools/company-360) — one row per domain: contacts, tech, security, hiring and company facts
- [Hiring Signals Scraper](https://apify.com/webdatatools/hiring-signals) — open jobs and hiring velocity from 10 public ATS boards
- [Y Combinator Companies & Founders Scraper](https://apify.com/webdatatools/yc-companies-scraper) — YC startups by batch, industry and hiring status
- [Wikidata Entity & Company Enrichment](https://apify.com/webdatatools/wikidata-entity-enrichment) — HQ, founders, employees, revenue and social IDs per company
- [Bulk Email Validator](https://apify.com/webdatatools/email-validator) — syntax, MX, disposable, role and free-provider checks
- [OpenStreetMap POI Extractor](https://apify.com/webdatatools/overpass-poi-extractor) — shops and amenities by radius, bbox or area

**Developer, app and research data**

- [npm, PyPI & Crates.io Package Health Checker](https://apify.com/webdatatools/package-health-checker) — releases, downloads, deprecation and a health score
- [GitHub Repository Health & Activity Report](https://apify.com/webdatatools/github-repo-health) — stars, commits, contributors and risk flags per repo
- [VS Code Marketplace Extension Scraper](https://apify.com/webdatatools/vscode-marketplace-extensions) — installs, ratings and versions per extension
- [Chrome Web Store Extension Scraper](https://apify.com/webdatatools/chrome-web-store-extensions) — users, rating, version and developer per extension
- [Google Play Store Scraper](https://apify.com/webdatatools/google-play-scraper) — apps, ratings, installs, developer contact and reviews
- [App Store (iOS) App Metadata & Top Charts](https://apify.com/webdatatools/app-store-lookup) — ratings, price, version and charts per app
- [CrossRef DOI & Citation Metadata Lookup](https://apify.com/webdatatools/crossref-doi-lookup) — papers, authors, journals and citation counts
- [FDA Recalls & Adverse Events Monitor](https://apify.com/webdatatools/openfda-recall-monitor) — food, drug and device recalls from openFDA
- [iCal / ICS Calendar Feed to Events Extractor](https://apify.com/webdatatools/ical-calendar-extractor) — any public calendar feed as event rows
- [Shopify Store Products Scraper](https://apify.com/webdatatools/shopify-products-scraper) — catalog, prices, variants and stock per store

### Support and feedback

Missing a metric or an opportunity you need in the row? Open an issue on the **Issues** tab.

# Actor input Schema

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

Enter the page URLs to audit, one per row, e.g. https://apify.com. Each URL returns one row per device strategy. Audit the exact URL you care about (a landing page, not only the homepage) - PageSpeed Insights follows redirects but scores the page it lands on.

## `apiKey` (type: `string`):

Paste your free Google PageSpeed Insights API key (https://developers.google.com/speed/docs/insights/v5/get-started), e.g. AIzaSy... Runs of up to 5 URLs work without a key on a shared demo quota; larger batches need your own key (25,000 requests/day, free).

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

Select the device Lighthouse should emulate, e.g. mobile. Google ranks on mobile, so audit mobile unless you specifically need desktop numbers. Choose 'Both' to get one row per device (two billable rows per URL).

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

Select which Lighthouse categories to score, e.g. performance, seo. Every extra category makes the Google request slower; performance alone already returns all Core Web Vitals and the optimisation opportunities.

## `locale` (type: `string`):

Enter the language for Lighthouse titles and display values, e.g. en, de or tr. Only the wording of titles changes, never the metrics.

## `maxConcurrency` (type: `integer`):

Enter how many PageSpeed Insights requests may run in parallel, e.g. 2. Google rate-limits hard and one Lighthouse run takes 10-30 seconds, so keep this at 2-3 unless you have your own API key.

## Actor input object example

```json
{
  "urls": [
    "https://apify.com",
    "https://example.com"
  ],
  "strategy": "mobile",
  "categories": [
    "performance",
    "seo"
  ],
  "locale": "en",
  "maxConcurrency": 2
}
```

# Actor output Schema

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

All audited URLs — download as JSON, CSV, Excel or HTML.

# 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://apify.com",
        "https://example.com"
    ],
    "strategy": "mobile",
    "categories": [
        "performance",
        "seo"
    ],
    "locale": "en",
    "maxConcurrency": 2
};

// Run the Actor and wait for it to finish
const run = await client.actor("webdatatools/core-web-vitals-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://apify.com",
        "https://example.com",
    ],
    "strategy": "mobile",
    "categories": [
        "performance",
        "seo",
    ],
    "locale": "en",
    "maxConcurrency": 2,
}

# Run the Actor and wait for it to finish
run = client.actor("webdatatools/core-web-vitals-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://apify.com",
    "https://example.com"
  ],
  "strategy": "mobile",
  "categories": [
    "performance",
    "seo"
  ],
  "locale": "en",
  "maxConcurrency": 2
}' |
apify call webdatatools/core-web-vitals-audit --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,webdatatools/core-web-vitals-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/FM0Kfh5kY4KVsuHVe/builds/K08CJmlJnbA7IFysC/openapi.json
