Page speed regression check

What you get

• What got slower, by how much, since when
• Before/after conversion rate from GA4
• Likely cause and the top fixes

Install

claude.ai and Claude Desktop

1. Download the .zip.
2. In Claude, go to Settings, Capabilities, Skills, and upload it.
3. Connect Caybl.ai from the connector directory if you haven’t already.

Claude Code

The skill

This is the full SKILL.md - the same file you download. View raw.

---
name: page-speed-regression-check
description: Work out whether and when a website got slower for real visitors, what likely changed that week, and whether it affected traffic or conversions. Use when someone says their site feels slower, their Core Web Vitals turned red in Search Console, or conversions dropped and they suspect speed. Needs the Caybl.ai connector (pagespeed_ tools; Google Analytics optional).
---

# Page speed regression check

Uses the Caybl.ai connector. If its `pagespeed_` tools aren't available, tell the user to add Caybl.ai (https://caybl.ai) as a connector and stop.

## 1. Find when it changed

Call `pagespeed_core_web_vitals_history` for the whole site (bare domain, e.g. `example.com`) with `formFactor: "PHONE"` and `weeks: 25`. If the user named specific pages or templates, also run it for one URL of each.

The tool's `summary` lists the weeks a metric changed rating and the overall change. Each point is a rolling 28-day window, so a sudden change on a given day shows up gradually over about four weekly points; the change started around the **first** week that moved.

If nothing changed rating and nothing moved 10% or more, say so plainly: real visitors haven't seen a slowdown. Then check current status with `pagespeed_core_web_vitals` in case it was always slow.

## 2. Check whether it mattered

If Google Analytics is connected, call `run_report` with dimension `week` (or `date`), metrics `sessions`, `keyEvents` and `sessionKeyEventRate`, covering four weeks either side of the change. Compare the conversion rate before and after. Report correlation as correlation, not proof.

## 3. Find what changed

Run `pagespeed_audit` (mobile) on the most affected page and name the top 3 fixes. Ask the user what was deployed, installed or changed around the start week (theme update, new plugin, tag, chat widget, hero image, A/B test). Third-party code in the audit's diagnostics is a common culprit.

## 4. Report

One sentence: what got slower, by how much, starting when. Then the evidence (trend points), the business impact if GA was available, the likely cause, and the fixes. Keep it short.

More SEO skills

• SEO audit from Search Console - An SEO audit from your own Search Console, Bing and GA4 data: indexation, decaying pages, CTR fixes, striking-distance keywords and cannibalization.
• SEO rank tracking - Winners, losers, new and lost queries from Search Console over the last 28 days or around a Google update - with Bing alongside.
• SEO vs Google Ads overlap - Finds what you pay for in Google Ads while already ranking top 3 organically, and the paid winners SEO should build pages for.