Technical
How to watch for Core Web Vitals regressions
cwv-regression-watch a saved expert workflow your assistant follows, in Claude, ChatGPT or Cursor
Watch Core Web Vitals for regressions: what got slower period-over-period, which pages are weakest, mobile vs desktop split, plus the honest "does page speed correlate with clicks HERE" read.
Try it
any CWV regressions
Private beta Part of the quattr-ai-search plugin, rolling out org by org. Request access ↗
Say any of these
CWV regressionsdid vitals get worsecore web vitals watchpage speed regressionsLCP got slower?vitals trend this monthis site speed hurting us
You never name the skill or a tool, the assistant routes on what you asked. These are the phrasings it recognises for this one.
And when it stays out of the way
Not for the full technical sweep (technical-health-audit), or for "why did clicks drop" (anomaly-investigator, which includes a vitals step).
Use it instead of technical-health-audit when vitals are the whole subject; use technical-health-audit instead for the all-systems audit.
What it runs
site_health_cwv_checkcorrelate_domains
2 governed analyses, composed and scoped for you. Named here for transparency, not because you have to ask for them.
The numbers behind it
Metrics it reads, each defined in the reference
Cumulative Layout ShiftInteraction to Next PaintLargest Contentful PaintOverall page-experience verdictPerformance scoreVital gradeVital grade distributionWeakest vital
Reports these numbers feed
What it refuses to do
- Vitals values and grades come from the tool; no invented thresholds, and your measurement cadence is always stated.
- The correlation read never graduates to "speed cost us X clicks", that claim needs the controlled test.
What the answer looks like
Did vitals get worse?
Analysis plan, every step, resolved for you
- Routed to the governed workflow
cwv-regression-watch - Dates bound explicitly
Jul 1 to Jul 31, 2026 - 3 analyses queued in parallel
site_health_cwv_check · correlate_domains · get_data_freshness - Honesty gates armed
scope echo · freshness
Mobile LCP regressed 0.4s on the month; desktop held, 11 pages slipped out of 'good'.
- LCP (mobile)
- 3.1s ▲ +0.4s slower desktop holds at 2.2s
- Pages now needs-improvement
- 11 were 'good' in June, all on the Comparison-page template
- Speed↔clicks read
- no significant link here r = −0.21, p = 0.34 on this site, an honest null
Jul 1 to Jul 31, 2026 vs Jun 2026
⚠ Observationalas of Aug 1, 2026 (CWV refresh cadence varies by page set)IllustrativeOpen in Quattr ↗
Fix the Comparison-page template regression, and don't promise a traffic lift from it.
A simulated conversation on fictional data. Scope, freshness and the ⚠ Observational marker are attached by the same director that renders every demo here, not written by hand.
See this Skill inside a real analysis
All runs →A recorded run where this Skill does the work, the prompts as typed, and the decision that came back.
Want this Skill running on your own accounts? Every Quattr customer works with an AI Search Strategist who sets it up with you.