Google PageSpeed Connector

Run automated PageSpeed Insights audits for customer URLs, collect Lighthouse and CrUX metrics, trigger alerts on Core Web Vitals regressions, and embed white-labelled performance reports inside your SaaS using Cyclr.

Build with this Connector Talk to an integration expert

Automated audits

Schedule and run PageSpeed audits across tenant URLs.

Actionable data

Receive Lighthouse audits and CrUX metrics for remediation.

Built-in governance

Control credentials, quotas and access per tenant.

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

Overview

Integrate PageSpeed Insights to run Lighthouse lab audits and retrieve CrUX field metrics for any URL, then automate monitoring, report generation and remediation workflows. Cyclr calls the PageSpeed runPagespeed endpoint to return lighthouseResult, loadingExperience and originLoadingExperience for each analysed URL. PageSpeed Insights API documentation. (developers.google.com)

PRODUCT USE CASES

Top use cases

Ship customer-facing speed checks, scheduled audits and automated remediation workflows. Publish PageSpeed analysis tools inside your embedded marketplace for self-serve activation and tenant-specific configuration. (cyclr.com)

Tenant performance monitoring

Schedule runPagespeed for each customer URL, store lighthouseResult and loadingExperience, and trigger alerts when LCP or CLS regress.

White-labelled performance reports

Generate PDF or in-app reports from runPagespeed lighthouseResult audits and distribute per tenant or account manager.

Automated remediation workflows

Use audit findings to open tickets or kick off optimization flows in downstream systems.

ORCHESTRATION

How Google PageSpeed works with Cyclr

Cyclr sits between your SaaS product and Google PageSpeed to handle authentication, govern access and orchestrate every API call per customer, at scale.

1
Your SaaS product
Your app requests an action for a specific customer.
2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
3
Google PageSpeed
Google PageSpeed processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore Google PageSpeed methods you can orchestrate through Cyclr.

Page Speed1

Analyze Page Speed

Action

Runs Page Speed analysis of the specified page.

TECHNICAL DETAILS

Google PageSpeed integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing Google PageSpeed integrations in Cyclr.

API and authentication

API host: https://www.googleapis.com/pagespeedonline/v5
Authentication: API key; OAuth 2.0
Credentials: API key, or OAuth client ID and client secret; Cyclr Service Domain for OAuth redirect; enable PageSpeed API in Google Cloud.
Method categories: Run page analysis; retrieve Lighthouse audits, labData, loadingExperience and originLoadingExperience.

View vendor API documentation →

Pagination and rate limits

Pagination

No pagination — each runPagespeed request returns a single analysis JSON (lighthouseResult plus loadingExperience). (developers.google.com)

Rate limits

Quotas are governed in Google Cloud Console. Projects commonly observe ~25,000 requests/day and ~400 requests/100 seconds; confirm per project quotas in Console. (unlighthouse.dev)

IMPLEMENTATION

Authentication at a glance

PageSpeed calls accept a Google Cloud API key (recommended for automated server-to-server use) or an OAuth 2.0 token for user-scoped flows. Cyclr OAuth setup requires a Google Project and a Cyclr Service Domain redirect. Confirm the enabled option in Console. (developers.google.com)

Authentication method: API key; OAuth 2.0
Credential required: API key, or OAuth client ID and client secret; Cyclr Service Domain for OAuth redirect; enable PageSpeed API in Google Cloud.

Before you begin:

View setup guide

COMMON QUESTIONS

Frequently asked questions

It runs PageSpeed Insights analyses for URLs and returns Lighthouse and CrUX data you can use to automate monitoring, generate reports, send alerts and drive remediation workflows. The connector calls the runPagespeed endpoint to retrieve lighthouseResult and loadingExperience. (developers.google.com)

Use a Google Cloud API key for server-to-server automation or OAuth 2.0 for user-scoped access. Cyclr’s Google setup requires registering a Google Project and adding your Cyclr Service Domain redirect URI. Confirm the Cyclr Console options when installing. (developers.google.com)

Yes. Cyclr supports multi-tenant embedded delivery and marketplace installation so you can present self-serve PageSpeed tools per customer, manage credentials and isolate tenant data. Use tenant-specific keys or tokens per account. (cyclr.com)

Yes. You can package runPagespeed-based workflows and expose them as MCP Servers or tools in Cyclr’s embedded marketplace with governance, RBAC and audit logging. Confirm available method mappings in your Cyclr Console. (cyclr.com)

KEEP EXPLORING

Related resources and connectors

Documentation