Google PageSpeed · Rate Limits

Google Pagespeed Rate Limits

Google publishes NO numeric rate limit or quota for the PageSpeed Insights API on any public documentation page. limit_count is 0 for that reason. What the API does expose is the quota machinery itself, in the 429 body — the metric name, the limit name and the unit — which was captured live and is recorded below. The numeric value of defaultPerDayPerProject is only visible on the Cloud Console quotas page for pagespeedonline.googleapis.com, which requires a signed-in Google account. Widely repeated third-party figures (25,000 queries/day, 240 queries/minute) are NOT recorded here because Google does not publish them.

Google Pagespeed Rate Limits is the machine-readable rate-limit profile for Google PageSpeed on the APIs.io network, conforming to the API Commons Rate Limits specification.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Core Web Vitals, Google, Lighthouse, Page Speed, and SEO.

0 Limits Throttle: 429 Quota: 429
Core Web VitalsGoogleLighthousePage SpeedSEOWeb PerformanceRate LimitingQuotas

Policies

Backoff Strategy
Exponential backoff with jitter is the only viable strategy, because no Retry-After or reset header is returned to time the retry against.
Quota Attribution
The `quotaUser` system parameter lets a caller attribute quota to an opaque end-user string when no Google user id is available, so one shared key can be apportioned across callers.
Quota Increase
Increases are requested through Cloud Console quotas, per the google.rpc.Help link returned in the 429 body.