Marketing Skills Directory PageSpeed Insights API
No fee listed
Quota-based. The docs list no charge.
Quota-based (see docs)
API key
API key is optional, recommended for frequent automated queries. Sent as key query parameter.
Lighthouse performance score and metrics
Accessibility, best-practices and SEO category scores
Chrome UX Report field data
Improvement suggestions per audit
Pricing checked on 23 Oct 2026 · Pricing page · Docs · Sign up
Description
The PageSpeed Insights API returns Lighthouse lab results and, where available, real-world data from the Chrome User Experience Report for a URL. Besides performance, you can request accessibility, best-practices and SEO categories, on mobile or desktop.
It works well for scheduled site speed monitoring, before and after checks on page changes, and agents that audit a list of landing pages.
It tests one URL per call and returns a large JSON response. Google’s page says it plans to discontinue the real-world data in this API and points to the CrUX API and CrUX History API for that.
Key endpoints
GET /runPagespeed: Lighthouse and CrUX results for a URL (params: url, category, strategy, locale)
Example request
curl "https://www.googleapis.com/pagespeedonline/v5/runPagespeed?url=https://web.dev/&strategy=mobile&category=performance&category=seo&key=YOUR_API_KEY"
Tech details
- API style
- REST
- Base URL
- https://www.googleapis.com/pagespeedonline/v5
- Rate limits
- Quota numbers are in your Google Cloud console.
- Official SDKs
- Python, Node.js
Use Cases
Lighthouse performance score and metrics
Accessibility, best-practices and SEO category scores
Chrome UX Report field data
Improvement suggestions per audit
Editor’s note What our review found
Editorial research, reviewed 23 Oct 2026. We read Google's PageSpeed Insights API getting-started and reference pages. We did not run live calls. This listing is not an endorsement.
Cost: Google's pages list no charge for the API. Quota numbers are not published on those pages; check your Google Cloud console.
Credentials and data: an API key is optional but recommended for frequent automated use. Keep the key in an environment variable or secret manager, not in code. The URLs you test are sent to Google.
Good to know: Google says the real-world data in this API is planned for discontinuation, so build field-data features on the CrUX API instead.