跳到主内容
智客 ZICQ

技能库 智客分类:Agent 工作流 debug-optimize-lcp

Debug Optimize Lcp

使用 Chrome DevTools MCP 工具的引导调试并优化最大内容绘画(LCP). 当用户询问LCP的性能,缓慢的页面负载,Core Web Vitals优化,或想了解为何他们的页面主要内容需要太长才能出现时,就使用这一技能. 当用户提到"最大内容的油漆","页面负载速度","CWV",或者想改善他们的英雄形象或主要内容产生的速度时,也会使用.

2575 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

使用 Chrome DevTools MCP 工具的引导调试并优化最大内容绘画(LCP). 当用户询问LCP的性能,缓慢的页面负载,Core Web Vitals优化,或想了解为何他们的页面主要内容需要太长才能出现时,就使用这一技能. 当用户提到"最大内容的油漆","页面负载速度","CWV",或者想改善他们的英雄形象或主要内容产生的速度时,也会使用.

何时用

用户提及“最大内容的油漆”、“页面载荷速度”、“CWV”,或希望改善其英雄形象或主要内容的速度

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:What is LCP and why it matters、LCP Subparts Breakdown、Debugging Workflow、Step 1: Record a Performance Trace、Step 2: Analyze LCP Insights、Step 3: Identify the LCP Element。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/lcp-snippets.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions "largest contentful paint", "page load speed", "CWV", or wants to improve how fast their hero image or main content renders.

What is LCP and why it mattersLCP Subparts BreakdownDebugging WorkflowStep 1: Record a Performance TraceStep 2: Analyze LCP InsightsStep 3: Identify the LCP ElementStep 4: Check the Network WaterfallStep 5: Inspect HTML for Common IssuesOptimization Strategies1. Eliminate Resource Load Delay (target: <10%)2. Eliminate Element Render Delay (target: <10%)3. Reduce Resource Load Duration (target: ~40%)

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
debug-optimize-lcp
description
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions "largest contentful paint", "page load speed", "CWV", or wants to improve how fast their hero image or main content renders.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 1
  • references/lcp-snippets.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「debug-optimize-lcp」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-d977c3b5a145205d-%E9%99%A4%E9%94%99%E4%BC%98%E5%8C%96-Lcp.html
请存为 .cursor/skills/debug-optimize-lcp/SKILL.md 或 .claude/skills/debug-optimize-lcp/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/chromedevtools/chrome-devtools-mcp 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/chromedevtools/chrome-devtools-mcp' --list

npx skills add 'https://github.com/chromedevtools/chrome-devtools-mcp' --skill 'debug-optimize-lcp'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: debug-optimize-lcp description: Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions "largest contentful paint", "page load speed", "CWV", or wants to improve how fast their hero image or main content renders. --- ## What is LCP and why it matters Largest Contentful Paint (LCP) measures how quickly a page's main content becomes visible. It's the time from navigation start until the largest image or text block renders in the viewport. - **Good**: 2.5 seconds or less - **Needs improvement**: 2.5–4.0 seconds - **Poor**: greater than 4.0 seconds LCP is a Core Web Vital that directly affects user experience and search ranking. On 73% of mobile pages, the LCP element is an image. ## LCP Subparts Breakdown Every page's LCP breaks down into four sequential subparts with no gaps or overlaps. Understanding which subpart is the bottleneck is the key to effective optimization. | Subpart | Ideal % of LCP | What it measures | | ----------------------------- | -------------- | ---------------------------------------------- | | **Time to First Byte (TTFB)** | ~40% | Navigation start → first byte of HTML received | | **Resource load delay** | <10% | TTFB → browser starts loading the LCP resource | | **Resource load duration** | ~40% | Time to download the LCP resource | | **Element render delay** | <10% | LCP resource downloaded → LCP element rendered | The "delay" subparts should be as close to zero as possible. If either delay subpart is large relative to the total LCP, that's the first place to optimize. **Common Pitfall**: Optimizing one subpart (like compressing an image to reduce load duration) without checking others. If render delay is the real bottleneck, a smaller image won't help — the saved time just shifts to render delay. ## Debugging Workflow Follow these steps in order. Each step builds on the previous one. ### Step 1: Record a Performance Trace Navigate to the page, then record a trace with reload to capture the full page load including LCP: 1. `navigate_page` with `pageId` to the target URL. 2. `performance_start_trace` with `pageId`, `reload: true` and `autoStop: true`. The trace results will include LCP timing and available insight sets. Note the insight set IDs from the output — you'll need them in the next step. ### Step 2: Analyze LCP Insights Use `performance_analyze_insight` to drill into LCP-specific insights. Look for these insight names in the trace results: - **LCPBreakdown** — Shows the four LCP subparts with timing for each. - **DocumentLatency** — Server response time issues affecting TTFB. - **RenderBlocking** — Resources blocking the LCP element from rendering. - **LCPDiscovery** — Whether the LCP resource was discoverable early. Call `performance_analyze_insight` with `pageId`, the insight set ID, and the insight name from the trace results. ### Step 3: Identify the LCP Element Use `evaluate_script` (with `pageId`) and the **"Identify LCP Element" snippet** found in [references/lcp-snippets.md](references/lcp-snippets.md) to reveal the LCP element's tag, resource URL, and raw timing data. The `url` field tells you what resource to look for in the network waterfall. If `url` is empty, the LCP element is text-based (no resource to load). ### Step 4: Check the Network Waterfall Use `list_network_requests` to see when the LCP resource loaded relative to other resources: - Call `list_network_requests` with `pageId` filtered by `resourceTypes: ["Image", "Font"]` (adjust based on Step 3). - Then use `get_network_request` with `pageId` and the LCP resource's request ID for full details. **Key Checks:** - **Start Time**: Compare against the HTML document and the first resource. If the LCP resource starts much later than the first resource, there's resource load delay to eliminate. - **Duration**: A large resource load duration suggests the file is too big or the server is slow. ### Step 5: Inspect HTML for Common Issues Use `evaluate_script` (with `pageId`) and the **"Audit Common Issues" snippet** found in [references/lcp-snippets.md](references/lcp-snippets.md) to check for lazy-loaded images in the viewport, missing fetchpriority, and render-blocking scripts. ## Optimization Strategies After identifying the bottleneck subpart, apply these prioritized fixes. ### 1. Eliminate Resource Load Delay (target: <10%) The most common bottleneck. The LCP resource should start loading immediately. - **Root Cause**: LCP image loaded via JS/CSS, `data-src` usage, or `loading="lazy"`. - **Fix**: Use standard `` with `src`. **Never** lazy-load the LCP image. - **Fix**: Add `` if the image isn't discoverable in HTML. - **Fix**: Add `fetchpriority="high"` to the LCP `` tag. ### 2. Eliminate Element Render Delay (target: <10%) The element should render immediately after loading. - **Root Cause**: Large stylesheets, synchronous scripts in ``, or main thread blocking. - **Fix**: Inline critical CSS, defer non-critical CSS/JS. - **Fix**: Break up long tasks blocking the main thread. - **Fix**: Use Server-Side Rendering (SSR) so the element exists in initial HTML. ### 3. Reduce Resource Load Duration (target: ~40%) Make the resource smaller or faster to deliver. - **Fix**: Use modern formats (WebP, AVIF) and responsive images (`srcset`). - **Fix**: Serve from a CDN. - **Fix**: Set `Cache-Control` headers. - **Fix**: Use `font-display: swap` if LCP is text blocked by a web font. ### 4. Reduce TTFB (target: ~40%) The HTML document itself takes too long to arrive. - **Fix**: Minimize redirects and optimize server response time. - **Fix**: Cache HTML at the edge (CDN). - **Fix**: Ensure pages are eligible for back/forward cache (bfcache). ## Verifying Fixes & Emulation - **Verification**: Re-run the trace (`performance_start_trace` with `pageId` and `reload: true`) and compare the new subpart breakdown. The bottleneck should shrink. - **Emulation**: Lab measurements differ from real-world experience. Use `emulate` to test under constraints: - `emulate` with `pageId`, `networkConditions: "Fast 3G"` and `cpuThrottlingRate: 4`. - This surfaces issues visible only on slower connections/devices.

相关技能

Agent 工作流

Skill Creator

创造有效技能指南。 当用户想创造出新的技能(或更新现有的技能),以专业知识,工作流程,或工具集成来扩展克洛德的能力时,应该使用这种技能.

Agent 工作流

Clawdhub

使用ClawdHub CLI搜索,安装,更新并发布从taladhub.com的代理技能. 需要获取苍蝇上的新技能时使用,将安装的技能同步到最新版本或特定版本,或者发布 npm-instainddhub CLI 的新/更新的技能文件夹.

Agent 工作流

Agent Team Orchestration

管弦乐团多代理团队,任务设定周期,交接协议,审查工作流程. 使用时间: (1)建立2+特派员队伍,具有不同专业,(2)确定任务路线和生命周期(收录框_ spec_建设_审查_完成),(3)在特派员之间制定交接协议,(4)建立审查和质量关口,(5)管理特派员之间的交流和文物共享.

Agent 工作流

Superpowers

Spec-first,TDD,子代理驱动的软件开发工作流程. 当:(1)构建任何新功能或应用——触发脑暴_计划_子代理执行回路,(2)调试出一个bug或测试失败——触发系统性的根起过程,(3)用户说"让我们构建","帮助我计划","我想添加X",或"这个被打破",(4)完成一个功…