PageSpeed Insights API logo

PageSpeed Insights API

PageSpeed Insights API

Analyze a page with runPagespeed and feed performance diagnostics into site quality tooling.

Visit site ↗Health checked 9h ago
Use it when

Simple surface centered on runPagespeed

Watch for

Very narrow surface, not a general website management API

First check

Start with a single runPagespeed request against a target URL, then decide how you want to store thresholds, regressions, and historical comparisons in your build pipeline.

Auth
oauth
CORS
No
HTTPS
Yes
Signup
Required
Latency
532 ms
Protocol
REST
Pricing

Uptime · 30-day window

Probes: 1Uptime: 100%Avg latency: 532ms
01

About this API

This API is intentionally narrow: the center of gravity is runPagespeed. Its value comes from turning page performance analysis into an automated check, release gate, or trend dashboard. In the published OpenAPI surface, the most concrete handles are "/pagespeedonline/v5/runPagespeed", backed by tags such as "pagespeedapi".

That makes the API practical for run page performance checks in ci, track regression on important urls, and pipe optimization suggestions into a site quality dashboard. The spec lists scopes such as "openid".

Very narrow surface, not a general website management API The spec exposes very little auth detail beyond a minimal scope listing

02

What you can build

  • 1Run page performance checks in CI
  • 2Track regression on important URLs
  • 3Pipe optimization suggestions into a site quality dashboard
03

Strengths & limitations

Strengths

  • Simple surface centered on runPagespeed
  • Easy to embed into developer tooling
  • Naturally fits scheduled analysis of target URLs

Limitations

  • Very narrow surface, not a general website management API
  • The spec exposes very little auth detail beyond a minimal scope listing
04

Example request

Generic template — replace <endpoint> with the real path from the docs.
curl https://google.com/<endpoint> \
  -H "Authorization: Bearer $ACCESS_TOKEN"
05

Getting started

Start with a single runPagespeed request against a target URL, then decide how you want to store thresholds, regressions, and historical comparisons in your build pipeline.

06

Technical details

CORS: NoHTTPS: YesSignup: YesOpen source: No
Auth type
oauth
Pricing
unknown
Protocols
REST
Response time
532 ms
Last health check
5/12/2026, 7:37:36 AM
07

Tags

08

More from Google