SEO Technical: Core Web Vitals
Guides optimization of Core Web Vitals (CWV)—Google's user experience metrics that affect search ranking. CWV are confirmed ranking factors for mobile and desktop.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Scope (Technical SEO)
- LCP (Largest Contentful Paint): Loading performance; time to render largest content element
- INP (Interaction to Next Paint): Responsiveness; replaced FID on March 12, 2024
- CLS (Cumulative Layout Shift): Visual stability; unexpected layout shifts
Target Thresholds (75th percentile, field data)
| Metric |
Target |
Good |
Needs Improvement |
Poor |
| LCP |
≤2.5s |
≤2.5s |
2.5–4.0s |
>4.0s |
| INP |
≤200ms |
≤200ms |
200–500ms |
>500ms |
| CLS |
<0.1 |
≤0.1 |
0.1–0.25 |
>0.25 |
Source: Google Page Experience
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site URL.
Identify:
- Tools: GSC Core Web Vitals report, PageSpeed Insights, Chrome DevTools
- Metrics: Which metric is failing (LCP, INP, CLS)
- Page type: Hero, article, product, list—LCP candidate differs
LCP Optimization
LCP measures the time until the largest content element (image, video, or text block) is visible.
| Cause |
Fix |
| Slow server response |
Reduce TTFB; use CDN; optimize server |
| Render-blocking resources |
Defer non-critical CSS/JS; inline critical CSS |
| Large images |
WebP/AVIF; compress; width/height to prevent CLS; see image-optimization |
| Client-side rendering |
SSR/SSG for above-fold content; see rendering-strategies |
| Third-party scripts |
Load async; defer non-critical |
LCP candidates: Hero image, large text block, video poster. Ensure above-fold images use loading="eager" (default); never lazy-load LCP.
INP Optimization
INP measures responsiveness—time from user interaction to next paint. Replaced FID on March 12, 2024.
| Cause |
Fix |
| Long-running JS |
Break tasks >50ms; use requestIdleCallback; Web Workers |
| Heavy event handlers |
Debounce/throttle; defer non-critical work |
| Main thread blocking |
Reduce third-party scripts; defer non-critical JS |
| Layout thrashing |
Batch DOM reads/writes; avoid forced reflows |
CLS Optimization
CLS measures unexpected layout shifts.
| Cause |
Fix |
| Images without dimensions |
Always set width and height attributes |
| Dynamic content |
Reserve space for ads, embeds; use min-height |
| Web fonts |
font-display: optional or swap; preload critical fonts |
| Animations |
Use transform instead of top/left/width |
Reserve space: For images, ads, embeds—define dimensions before load. Avoid inserting content above existing content without reserved space.
Tools & Monitoring
| Tool |
Use |
| GSC |
Core Web Vitals report; URL grouping; field data |
| PageSpeed Insights |
Lab + field data; mobile + desktop |
| Chrome DevTools |
Performance panel; LCP element; layout shift overlay |
Output Format
Related Skills
- image-optimization: LCP image optimization; WebP; lazy loading (below-fold only)
- google-search-console: CWV report; field data monitoring
- mobile-friendly: Mobile-first indexing; mobile CWV targets
- rendering-strategies: SSR/SSG for LCP; content in initial HTML
- site-crawlability: Redirect chains waste crawl; fix for performance
1---2name: core-web-vitals3description: When the user wants to optimize Core Web Vitals, fix LCP, INP, or CLS issues. Also use when the user mentions "Core Web Vitals," "CWV," "LCP," "INP," "CLS," "FID," "page speed," "page performance," "Largest Contentful Paint," "Interaction to Next Paint," "Cumulative Layout Shift," or "Page Experience." For GSC CWV, use google-search-console.4---56# SEO Technical: Core Web Vitals78Guides optimization of Core Web Vitals (CWV)—Google's user experience metrics that affect search ranking. CWV are confirmed ranking factors for mobile and desktop.910**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.1112## Scope (Technical SEO)1314- **LCP** (Largest Contentful Paint): Loading performance; time to render largest content element15- **INP** (Interaction to Next Paint): Responsiveness; replaced FID on March 12, 202416- **CLS** (Cumulative Layout Shift): Visual stability; unexpected layout shifts1718## Target Thresholds (75th percentile, field data)1920| Metric | Target | Good | Needs Improvement | Poor |21|--------|--------|------|-------------------|------|22| **LCP** | ≤2.5s | ≤2.5s | 2.5–4.0s | >4.0s |23| **INP** | ≤200ms | ≤200ms | 200–500ms | >500ms |24| **CLS** | <0.1 | ≤0.1 | 0.1–0.25 | >0.25 |2526**Source**: [Google Page Experience](https://developers.google.com/search/docs/appearance/page-experience)2728## Initial Assessment2930**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for site URL.3132Identify:331. **Tools**: GSC Core Web Vitals report, PageSpeed Insights, Chrome DevTools342. **Metrics**: Which metric is failing (LCP, INP, CLS)353. **Page type**: Hero, article, product, list—LCP candidate differs3637## LCP Optimization3839LCP measures the time until the largest content element (image, video, or text block) is visible.4041| Cause | Fix |42|-------|-----|43| **Slow server response** | Reduce TTFB; use CDN; optimize server |44| **Render-blocking resources** | Defer non-critical CSS/JS; inline critical CSS |45| **Large images** | WebP/AVIF; compress; `width`/`height` to prevent CLS; see **image-optimization** |46| **Client-side rendering** | SSR/SSG for above-fold content; see **rendering-strategies** |47| **Third-party scripts** | Load async; defer non-critical |4849**LCP candidates**: Hero image, large text block, video poster. Ensure above-fold images use `loading="eager"` (default); never lazy-load LCP.5051## INP Optimization5253INP measures responsiveness—time from user interaction to next paint. Replaced FID on March 12, 2024.5455| Cause | Fix |56|-------|-----|57| **Long-running JS** | Break tasks >50ms; use `requestIdleCallback`; Web Workers |58| **Heavy event handlers** | Debounce/throttle; defer non-critical work |59| **Main thread blocking** | Reduce third-party scripts; defer non-critical JS |60| **Layout thrashing** | Batch DOM reads/writes; avoid forced reflows |6162## CLS Optimization6364CLS measures unexpected layout shifts.6566| Cause | Fix |67|-------|-----|68| **Images without dimensions** | Always set `width` and `height` attributes |69| **Dynamic content** | Reserve space for ads, embeds; use `min-height` |70| **Web fonts** | `font-display: optional` or `swap`; preload critical fonts |71| **Animations** | Use `transform` instead of `top`/`left`/`width` |7273**Reserve space**: For images, ads, embeds—define dimensions before load. Avoid inserting content above existing content without reserved space.7475## Tools & Monitoring7677| Tool | Use |78|------|-----|79| **GSC** | Core Web Vitals report; URL grouping; field data |80| **PageSpeed Insights** | Lab + field data; mobile + desktop |81| **Chrome DevTools** | Performance panel; LCP element; layout shift overlay |8283## Output Format8485- **Current state**: Which metrics fail (LCP, INP, CLS)86- **Prioritized fixes**: By impact87- **References**: [Web Vitals](https://web.dev/vitals/), [Page Experience](https://developers.google.com/search/docs/appearance/page-experience)8889## Related Skills9091- **image-optimization**: LCP image optimization; WebP; lazy loading (below-fold only)92- **google-search-console**: CWV report; field data monitoring93- **mobile-friendly**: Mobile-first indexing; mobile CWV targets94- **rendering-strategies**: SSR/SSG for LCP; content in initial HTML95- **site-crawlability**: Redirect chains waste crawl; fix for performance
gaznil