PageSpeed Insights API – Website Speed Test & Core Web Vitals avatar

PageSpeed Insights API – Website Speed Test & Core Web Vitals

Pricing

from $5.00 / 1,000 page testeds

Go to Apify Store
PageSpeed Insights API – Website Speed Test & Core Web Vitals

PageSpeed Insights API – Website Speed Test & Core Web Vitals

Run Google PageSpeed Insights on a list of URLs: Lighthouse performance, accessibility, best-practices and SEO scores, LCP, CLS, TBT and INP, real-user Chrome data, Core Web Vitals pass/fail and the top slow-downs. Mobile and desktop.

Pricing

from $5.00 / 1,000 page testeds

Rating

0.0

(0)

Developer

Rowfeed

Rowfeed

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Run Google PageSpeed Insights on a list of pages and get one clean row per page: the four Lighthouse scores (performance, accessibility, best practices, SEO), lab speed metrics (LCP, FCP, TBT, CLS, Speed Index), real-user Chrome data (LCP, INP, CLS) with a Core Web Vitals pass/fail, and the biggest slow-downs with the time each one costs. Mobile, desktop or both. Built for SEO audits, agencies reporting on client sites, developers checking releases and anyone tracking site speed over time. A bulk PageSpeed Insights tool: no Google API key or quota of your own needed.

What you get

  • Lighthouse scores 0-100: performance_score, accessibility_score, best_practices_score, seo_score.
  • Lab metrics from a fresh Lighthouse test: lcp_ms, fcp_ms, tbt_ms, cls, speed_index_ms, tti_ms, server_response_ms.
  • Real-user field data from the Chrome UX Report (last 28 days): field_lcp_ms, field_inp_ms, field_cls, field_fcp_ms, field_ttfb_ms, each with a FAST / AVERAGE / SLOW rating. When a page has too little traffic, the whole site's data is used (field_data_source: "origin"); when the site has too little traffic too, it is null.
  • passes_core_web_vitals: true when real users get LCP ≤ 2.5 s, INP ≤ 200 ms and CLS ≤ 0.1.
  • top_issues: the five biggest slow-downs (unused JavaScript, render-blocking requests, image delivery, ...) with estimated savings in milliseconds.

Example output

{
"url": "https://www.fender.com/",
"final_url": "https://www.fender.com/",
"device": "mobile",
"performance_score": 32,
"accessibility_score": 100,
"best_practices_score": 73,
"seo_score": 85,
"lcp_ms": 17808,
"fcp_ms": 2605,
"tbt_ms": 3620,
"cls": 0.011,
"speed_index_ms": 11878,
"tti_ms": 28813,
"server_response_ms": 11,
"field_data_source": "url",
"field_lcp_ms": 3472,
"field_lcp_rating": "AVERAGE",
"field_inp_ms": 265,
"field_inp_rating": "AVERAGE",
"field_cls": 0.03,
"field_cls_rating": "FAST",
"field_fcp_ms": 1565,
"field_fcp_rating": "FAST",
"field_ttfb_ms": 671,
"field_ttfb_rating": "FAST",
"passes_core_web_vitals": false,
"top_issues": [
{ "id": "unused-javascript", "title": "Reduce unused JavaScript", "savings_ms": 4500 },
{ "id": "mainthread-work-breakdown", "title": "Minimize main-thread work", "savings_ms": 3600 },
{ "id": "bootup-time", "title": "Reduce JavaScript execution time", "savings_ms": 3350 }
],
"lighthouse_version": "13.6.0",
"checked_at": "2026-10-30T10:52:00+00:00"
}

Input

FieldWhat it does
urlsPages to test, e.g. https://example.com/ or example.com/pricing. Up to 1,000 per run.
devicemobile (default, what Google ranks on), desktop, or both (two rows per page).

Pricing

Pay per event, no subscription:

  • $5 per 1,000 tests ($0.005 per page per device). A page that cannot be tested (DNS error, site down) is free and comes back as an error row.
  • $0.001 per run start.

Examples: 100 pages on mobile cost $0.501. 100 pages on mobile and desktop cost $1.001. Cap the cost of a run with the maximum charge setting; the Actor never starts a test the budget cannot pay for. On the free Apify plan a run does up to 5 tests (5 pages on one device); any paid plan lifts the limit.

Good to know

  • Each test is a real Lighthouse run by Google and takes 10 to 90 seconds; up to 8 pages are tested at the same time.
  • Lab scores move a few points between runs, as they do on pagespeed.web.dev; the real-user field data is steadier.
  • Runs from the API, n8n/Make/Zapier, AI agents through MCP (rowfeed-seo-mcp) or on a schedule to track speed over time.

More SEO tools from Rowfeed

Uses Google's official PageSpeed Insights API. Not affiliated with Google.