agentleFS
gaznilgaznil/seo-skills-by-gaznil/skills/core-web-vitals/SKILL.md

core-web-vitals

Skill0 starsChanged 3 months agoMITView on GitHub

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.

37 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use javascript-seo, web-quality-audit and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MYehia565Skill

    javascript-seo

    Diagnoses JS rendering, lazy-loading, and indexing gaps for client-rendered pages. Use when content appears in the browser but not in fetched HTML or Search.

    Also in 4 projects that use this

  • RodrigoTomeESSkill

    web-quality-audit

    Comprehensive web quality audit covering performance, accessibility, SEO, and best practices. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".

    Also in 12 projects that use this

  • MYehia565Skill

    ecommerce-seo

    Applies Google ecommerce SEO guidance: IA/URLs, product data, and shopping-related structured data. Use when building or fixing product/category/store search presence.

    Also in 3 projects that use this

  • huiferSkill

    structured-data

    生成和验证 JSON-LD 结构化数据,支持 Article、BlogPosting、Organization、WebPage、Product、LocalBusiness 等 Schema.org 类型。自动检测页面类型,验证语法,检查必需字段,提供 Google Rich Results 测试工具链接和 Next.js 组件代码示例。

    Also in 3 projects that use this

  • kpbraySkill

    best-practices

    Applies Power BI best practices, BPA rules, and enterprise standards. Use for quality validation, naming conventions, and performance optimization.

    Also in 7 projects that use this

  • nilssonrSkill

    seo

    Full SEO workflow for auditing pages and creating SEO-optimized content. Provides checklists with educational explanations aligned with Google Search Central documentation.

    Also in 10 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for site URL.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

MetricTargetGoodNeeds ImprovementPoor
LCP≤2.5s≤2.5s2.5–4.0s>4.0s
INP≤200ms≤200ms200–500ms>500ms
CLS<0.1≤0.10.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:

  1. Tools: GSC Core Web Vitals report, PageSpeed Insights, Chrome DevTools
  2. Metrics: Which metric is failing (LCP, INP, CLS)
  3. 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.

CauseFix
Slow server responseReduce TTFB; use CDN; optimize server
Render-blocking resourcesDefer non-critical CSS/JS; inline critical CSS
Large imagesWebP/AVIF; compress; width/height to prevent CLS; see image-optimization
Client-side renderingSSR/SSG for above-fold content; see rendering-strategies
Third-party scriptsLoad 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.

CauseFix
Long-running JSBreak tasks >50ms; use requestIdleCallback; Web Workers
Heavy event handlersDebounce/throttle; defer non-critical work
Main thread blockingReduce third-party scripts; defer non-critical JS
Layout thrashingBatch DOM reads/writes; avoid forced reflows

CLS Optimization

CLS measures unexpected layout shifts.

CauseFix
Images without dimensionsAlways set width and height attributes
Dynamic contentReserve space for ads, embeds; use min-height
Web fontsfont-display: optional or swap; preload critical fonts
AnimationsUse 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

ToolUse
GSCCore Web Vitals report; URL grouping; field data
PageSpeed InsightsLab + field data; mobile + desktop
Chrome DevToolsPerformance 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.