seo-core-web-vitals
Audit Core Web Vitals & page performance — measure LCP, INP, and CLS against p75 field thresholds, diagnose render-blocking resources, unoptimized images, and layout-shift sources, and produce prioritized, advisory-only remediation guidance. Module M15. Feeds the Search SEO score (heavily) and the AI Visibility score (minimally).
Works with
---
name: seo-core-web-vitals
description: Audit Core Web Vitals & page performance — measure LCP, INP, and CLS against p75 field thresholds, diagnose render-blocking resources, unoptimized images, and layout-shift sources, and produce prioritized, advisory-only remediation guidance. Module M15. Feeds the Search SEO score (heavily) and the AI Visibility score (minimally).
license: MIT
---
# seo-core-web-vitals (M15)
Core Web Vitals are a confirmed Google ranking signal and a proxy for page quality. Thresholds, field-vs-lab honesty rules, and LCP decomposition: `references/cwv-thresholds.md` (follow it exactly).
## Audits
Working from the PageSnapshot (`rendered_dom` if present, else `raw_html`):
1. **Field CWV at p75** — LCP ≤ 2.5 s, INP ≤ 200 ms (INP replaced FID), CLS ≤ 0.1, all at the 75th percentile of real-user data. All three must pass for a "good" rating. Use the proactive-warning thresholds (LCP > 2.0 s, INP > 160 ms, CLS > 0.08) to `warn` before failing.
2. **Render-blocking resources** — synchronous `<script>` in `<head>` (no `defer`/`async`/`type=module`), blocking `<link rel="stylesheet">`, and `@import` chains that delay first render (LCP/INP risk).
3. **Unoptimized images** — missing `width`/`height` (or `aspect-ratio`), no `loading="lazy"` below the fold, no responsive `srcset`/`sizes`, legacy formats where AVIF/WebP would serve, and a non-preloaded LCP image.
4. **Layout-shift sources** — images/iframes/ads/embeds without reserved dimensions, web-font swap without `font-display`/size-adjust, and content injected above existing content (CLS risk).
5. **LCP decomposition** — attribute LCP to TTFB vs resource load delay vs load duration vs render delay (see `references/cwv-thresholds.md`) so each finding targets the dominant subpart.
## Fixes (fixable: advisory)
**Advisory only.** Performance fixes touch build config, server, CDN, and runtime JavaScript — high breakage risk — so the tool **diagnoses and prioritizes** but never auto-edits performance code. For each failing metric, name the specific resource/element causing it and rank fixes by expected leverage (e.g. preload the LCP image, defer non-critical JS, reserve image dimensions). Give framework-specific direction where the stack is known. **Never fabricate measured values** — if field data is absent, ask the user to supply a PSI/CrUX key or leave a clearly-marked TODO placeholder rather than guessing a metric.
## Verification
- Field (Tier 1): `node ${CLAUDE_SKILL_DIR}/../../scripts/psi-client.mjs --url <u>` calls the PageSpeed Insights API (`loadingExperience`, method `psi_api`); CrUX History via the same client (`crux_api`) for p75 trends. Requires a free API key.
- Tier 0 (no key): emit `status: needs_api` for every field-CWV finding, plus clearly-labeled **lab heuristics** (render-blocking count, missing image dimensions, bundle weight). Label lab signals "lab data — not what Google ranks on"; never present a heuristic as a measured field value.
- When the required data tier is unavailable, status is `needs_api` — **never** a false `pass`.
## Findings
Emit findings per `schema/finding.schema.json`. Examples:
- `M15.lcp.exceeds_p75` — field LCP > 2.5 s at p75 (status `fail`, severity 4, `fixable: advisory`, axis `search`, confidence `established`). `evidence.observed` quotes the measured p75 value and the LCP element; `verification.reproduce` runs the psi-client command.
- `M15.cls.unsized_image` — image with no `width`/`height` shifting layout (status `warn`, severity 4, `fixable: advisory`, axis `search`, confidence `directional`). `evidence.observed` quotes the `<img>` tag.
- `M15.field.needs_api` — no PSI/CrUX key, field CWV unverifiable (status `needs_api`, severity 4, `fixable: advisory`, axis `search`, confidence `established`).
Each finding: `evidence.observed` quotes the page/measurement; `verification.reproduce` is the runnable command; `expected_impact` is banded + confidence-tagged (no naked %).
## Honesty
- **Lab ≠ field.** A single local Lighthouse run is diagnostic only; Google ranks on field (CrUX) p75. Never let a lab number drive the Search score or masquerade as a field result.
- CWV is a real but **modest tie-breaker** signal — it does not override relevance/content quality. Don't promise ranking jumps from a green score; report it as banded `expected_impact`, not a predicted percentage gain.
- A "100" lab performance score is not a pass if field p75 fails; only field data settles a CWV finding.Related free tools on this site
More Performance skills
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
competitor-profiling
coreyhaines31/marketingskills
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
vercel-optimize
vercel-labs/agent-skills
Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests.
