# PageSpeed Insights Integration

Let your AI agent audit page speed, Core Web Vitals, accessibility and SEO with Google PageSpeed Insights, using your own Google Cloud API key.

---

Connect Google PageSpeed Insights to your Chipp AI so it can audit any public page on mobile and desktop, explain what is slow or broken, and tell you what to fix first -- all through natural conversation.

This is the first integration in Chipp's SEO and AEO (answer engine optimization) toolkit. The agent only recommends changes. You approve each one, and approved changes go to your normal Builder / site-edit workflow. Nothing is published automatically.

## What the AI Can Do

Once connected, your agent gains two tools:

| Tool | Description |
|------|-------------|
| **pagespeed_analyze_url** | Audit a public page URL. Runs one mobile and one desktop analysis by default and returns scores, Core Web Vitals, speed opportunities, failing audits, and a ranked list of what to fix first |
| **pagespeed_compare_runs** | Re-run an audit and compare it with an earlier run, to see what improved or got worse after a change |

### What an audit returns

For each device (mobile and desktop):

- **Lighthouse scores** from 0 to 100 for performance, accessibility, best practices and SEO
- **Lab metrics**: First Contentful Paint, Largest Contentful Paint, Total Blocking Time, Cumulative Layout Shift, Speed Index, Time to Interactive and server response time
- **Core Web Vitals from real users** (Chrome User Experience Report) when Google has enough data for the page or its site, with a passed or failed verdict
- **Top opportunities**, with Google's estimated time and size savings
- **Failing audits** for performance, accessibility, best practices and SEO
- **Prioritized findings**: a ranked list of fixes, each with Google's evidence, across both devices

Results are trimmed to the most useful items, so a long audit never floods the conversation.

## Connecting PageSpeed Insights


  **1.** 
    <strong>Create your own Google Cloud API key</strong>

    In the Google Cloud Console, enable the **PageSpeed Insights API** for a project, then create an API key under **APIs & Services > Credentials**. You can restrict the key to the PageSpeed Insights API. Chipp shows the exact steps in the connect dialog.
  


  **2.** 
    <strong>Open Integrations</strong>

    In your app's builder, go to **Brain > Integrations** and find **PageSpeed Insights** (under **SEO & AEO**).
  


  **3.** 
    <strong>Paste your key</strong>

    Paste the key into **Google Cloud API key** and click **Connect**. Chipp checks the key with Google before saving it. If Google rejects it, or the API is not enabled for the key's project, Chipp tells you and saves nothing.
  


  **4.** 
    <strong>Try it</strong>

    Ask your agent:
    - "Audit https://example.com on mobile and desktop and tell me what to fix first"
    - "Run the audit again and compare it with the last one"
  


## Whose credentials are used

You bring your own key. Chipp does not hold a PageSpeed Insights key for you and never uses one of its own for your audits.

- Audits use **your Google Cloud project's** quota and appear in your project's usage.
- The key is stored encrypted, belongs to your app, and is never shown again or sent to the AI model.
- To stop access, disconnect the integration in **Brain > Integrations**. Chipp deletes the stored key. You can also delete the key in Google Cloud Console. To use a different key, disconnect and connect again.

## Comparing runs

Chipp does not keep a history of past audits. To compare, the agent keeps the earlier run's scores and metrics from the conversation and passes them to **pagespeed_compare_runs**, which makes a fresh audit and reports what improved, regressed or stayed the same. Lab results vary a little from run to run, so small changes are reported as noise.

## Limits

- **Public pages only.** Google loads the page itself. Pages behind a login, on a private network, or blocking automated browsers cannot be audited. Local, private and non-http(s) addresses are refused.
- **Time.** One audit takes 10 to 40 seconds.
- **Quota.** Google limits how many audits your project can run per minute and per day. When the limit is reached, the agent tells you to try later.
- **Lab data varies.** Lab scores are a simulated page load, not what every visitor experiences.
- **Field data is not always available.** Core Web Vitals from real users exist only for pages and sites with enough Chrome traffic.
- **Recommendations only.** The integration never edits or publishes your site.

## Troubleshooting

| Message | What to do |
|---------|-----------|
| The key was rejected | Create a new key in Google Cloud Console, disconnect, and connect again |
| The key cannot use the PageSpeed Insights API | Enable the API for the key's project and make sure the key is not restricted away from it |
| Quota is used up | Wait, or raise the quota in Google Cloud Console |
| Lighthouse could not analyze that page | Check that the address is public, loads without a login, and does not block automated browsers |

## Billing

PageSpeed Insights tool calls use your standard Chipp LLM token billing. Google's own usage is governed by your Google Cloud project.