PageSpeed Audit: Bulk Core Web Vitals and Lighthouse Scores avatar

PageSpeed Audit: Bulk Core Web Vitals and Lighthouse Scores

Pricing

from $21.60 / 1,000 audits

Go to Apify Store
PageSpeed Audit: Bulk Core Web Vitals and Lighthouse Scores

PageSpeed Audit: Bulk Core Web Vitals and Lighthouse Scores

Bulk PageSpeed and Lighthouse audit for a list of URLs, mobile and desktop: performance, accessibility, best practices and SEO scores, Core Web Vitals (LCP, CLS, TBT, FCP) and the top fixes. No API key needed; add your own Google key for real user INP and field data.

Pricing

from $21.60 / 1,000 audits

Rating

0.0

(0)

Developer

The Mine Works

The Mine Works

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

13 days ago

Last modified

Features

Limited permissions

Share

Lighthouse scores, Core Web Vitals and the top fixes for a list of URLs, one row per page

From The Mine Works, makers of Website to Markdown Crawler and B2B Leads Finder, with over 305,000 runs across 310+ public actors.

Updated 4 Nov 2026: first release. Lighthouse 13 audits for a list of URLs, mobile, desktop or both: four category scores, lab Core Web Vitals with ratings, the top performance fixes and the failed checks, one flat row per page and device. Bookmark this Actor on its Store page so it is one click away next time.

Why choose this actor?

  • No API key needed. Google's PageSpeed API no longer answers without a key: every call we tried on 4 Nov 2026 came back 429 with a quota of 0. This actor runs Lighthouse itself in its own Chrome, so a list of URLs and a click is enough.
  • Scores you can act on. Every row has performance, accessibility, best practices and SEO from 0 to 100, LCP, CLS, TBT and FCP with good, needs-improvement or poor ratings, the fixes with the biggest savings first, and the checks that failed.
  • Pay per audit, nothing for pages that cannot be audited. A dead domain, a 404, a PDF or a page that refuses automated visits is checked with one plain request first and comes back as a free row saying why.

Run it on Apify

Part of The Mine Works Marketing, SEO and reviews family: Facebook Ad Library Scraper, Google Ads Transparency Scraper, Similarweb Scraper, Google News Scraper, Trustpilot Reviews Scraper, Google Trends Scraper.

Try it in one minute

Paste this into the input (JSON view) and press Start:

{
"urls": ["https://www.python.org", "https://developer.mozilla.org/en-US/"],
"strategy": "mobile"
}

Pages are audited one at a time, because Lighthouse scores suffer when audits share a machine. Allow 10 to 80 seconds per page.

Copy to your AI assistant

themineworks/pagespeed-audit on Apify. Runs Lighthouse on a list of public URLs and returns one flat row per URL and device with performance, accessibility, best practices and SEO scores, lab Core Web Vitals (LCP, CLS, TBT, FCP), the top fixes and failed checks, with no API key. Call ApifyClient("TOKEN").actor("themineworks/pagespeed-audit").call(run_input={"urls": ["https://example.com"], "strategy": "both"}), then client.dataset(run["defaultDatasetId"]).list_items().items. Audit rows have status "ok" and no _type field. Rows with _type "not_audited" say why a page was not audited and are free. Optional apiKey: the caller's own Google PageSpeed key, which adds real user field data.

Key features

  • Mobile, desktop or both for each URL.
  • Four Lighthouse categories, with lab LCP, CLS, TBT, FCP, Speed Index and page weight.
  • Good, needs-improvement or poor ratings at Google's own thresholds.
  • The top performance fixes with estimated savings, and the accessibility, best practices and SEO checks that failed.
  • A free row with the reason for any page that cannot be audited.
  • benchmark_index on every row: Lighthouse's measure of the machine, because scores depend on CPU.
  • Optional: your own Google key adds real user INP, LCP and CLS when Google has them.

How to use it

One page, both devices

{ "urls": ["https://example.com"], "strategy": "both" }

A client's key pages, performance and SEO only

{ "urls": ["https://example.com", "https://example.com/pricing", "https://example.com/blog"], "categories": ["performance", "seo"] }

With your own Google key, for real user data

{ "urls": ["https://example.com"], "apiKey": "YOUR_GOOGLE_KEY" }

To get a key: in Google Cloud, create a project, enable the PageSpeed Insights API, and create an API key. Google gives 25,000 queries a day for free. If Google refuses the key, or its quota runs out, the run stops with a message and that audit is not charged.

Input parameters

FieldTypeWhat it does
urlslistPages to audit, up to 1,000. https:// is added if missing. Duplicates run once.
strategychoicemobile (default), desktop or both.
categorieslistAny of performance, accessibility, best-practices, seo. The price stays the same.
maxOpportunitiesnumberPerformance fixes per page, 0 to 30, default 5.
pageLoadTimeoutSecsnumberHow long Lighthouse waits for a page, 15 to 90, default 45.
apiKeysecret textYour own Google key. Empty means our Chrome.

What data do you get?

FieldWhat it holds
url, final_url, strategy, statusThe page, where it ended, the device, and ok
performance_score, accessibility_score, best_practices_score, seo_score0 to 100
lcp_ms, cls, tbt_ms, fcp_ms and their _rating fieldsLab Core Web Vitals and ratings
speed_index_ms, tti_ms, server_response_msOther timings, when Lighthouse reports them
total_byte_weight, request_count, dom_sizePage weight
opportunitiesFixes: id, title, display_value, savings_ms, savings_bytes
failed_auditsFailed checks: category, id, title, item_count
field_lcp_ms, field_inp_ms, field_cls, field_fcp_ms, field_ttfb_ms, field_overallReal user data for the URL, only with your own key
origin_lcp_ms, origin_inp_ms, origin_cls, origin_overallReal user data for the site, only with your own key
engine, form_factor, throttling_method, benchmark_index, lighthouse_version, run_warnings, audited_atHow the audit ran

Stable fields for automations

Audit rows have status: "ok" and no _type. Rows with _type: "not_audited" carry url, status and note, and are free. summary, info and error rows are also free. The summary is saved as OUTPUT in the run's key-value store.

Pricing

Pay per event, with a flat fee per run.

EventWhen it is chargedFree planBronze (Starter)Silver (Scale)Gold (Business)
auditOne page on one device audited in our Chrome$0.027$0.0254$0.0235$0.0216
audit-own-keyOne page on one device audited with your own Google key$0.0135$0.0127$0.01175$0.0108
run-startOnce per run, after the first audit row reached your dataset$0.008$0.008$0.008$0.008

Both devices on one URL are two audits. Never charged:

  • a page stopped by the plain first request: dead domain, 404, a file that is not a web page, a page that refuses automated visits;
  • an audit Lighthouse could not finish or score;
  • duplicates, invalid addresses, the summary, info and error rows;
  • a run with no finished audit: the start fee follows the first audit row;
  • anything past your "Max cost per run": the budget is checked before each audit.

Run it on a schedule

In Apify Console open this Actor, choose Schedules, add a schedule, and pick how often it runs. Compare a page with itself over time: Lighthouse scores move by several points between runs even when nothing changed.

FAQ

Are these the same numbers as pagespeed.web.dev?

They are the same tool, Lighthouse, with the same mobile settings, but on a different machine. Performance scores depend on CPU, so they can differ from pagespeed.web.dev by some points. benchmark_index on each row shows the speed of the machine. With your own key, Google runs the audit itself, which is what pagespeed.web.dev shows.

Why is there no INP without a key?

INP needs real visitors. A page load in a lab cannot measure it, so lab rows use TBT as the stand-in. Real user INP comes from Google's field data, which needs your own key and enough traffic on the page.

Why was my page not audited?

The note on its row says why. A site that blocks automated visits answers our first request with an error such as 403, and we stop there rather than charge you for a blocked audit.

How long does a run take?

8 to 81 seconds per page and device in our test of 16 sites, about 25 on average, one at a time. With your own key, 4 pages run at once.

Do I need an account, cookies or a proxy?

No. Only public pages can be audited: sign-in pages and private network addresses are not.

Which formats can I download?

JSON, CSV, Excel, XML and RSS from the dataset, or through the API.

Can I use it from Claude, ChatGPT or Cursor (MCP)?

Yes, through Apify's MCP server. Connector URL: https://mcp.apify.com/?tools=themineworks/pagespeed-audit

  • Claude: Settings > Connectors > Add custom connector, paste the URL, sign in with Apify.
  • ChatGPT: turn on developer mode, add an MCP connector with the URL, sign in with Apify.
  • Cursor or VS Code: add it as an HTTP MCP server with that URL.
  • Claude Code: claude mcp add -t http pagespeed-audit "https://mcp.apify.com/?tools=themineworks/pagespeed-audit"

An audit loads a public page once, as a visitor would. You are responsible for how you use the results and for the terms of the sites you audit. This is general information, not legal advice.

Integrations

  • Google Sheets: send each run's audits to a sheet; one row per page and device fits as is.
  • Make, Zapier and n8n: start a run and read its dataset, for example "alert Slack when a key page drops below 50".
  • Webhooks: have Apify call your URL when a run succeeds, then fetch the dataset.
  • API and SDKs: run it from Python or JavaScript with the Apify client, or with a plain HTTP call.
  • MCP clients: Claude, ChatGPT, Cursor and VS Code can run it as a tool through the connector URL in the FAQ.

More from The Mine Works

Marketing, SEO and reviews

Social media and video

Leads and business directories

LinkedIn

Real estate

Science, health and government data

Jobs and hiring

Company and business data

E-commerce and marketplaces

Food and local services

Developer and AI tools

More tools

Support

Found a page that should audit but does not, or a field that comes back empty? Open an issue in the Issues tab with the input and the run ID, and we will look at it. For a field you need or a new source, email dmineworks@gmail.com.

Give it a list of URLs and get Lighthouse scores, Core Web Vitals and the top fixes back as one row per page and device, mobile and desktop, no API key.