debug-optimize-lcp

Diagnose and optimize Largest Contentful Paint using Chrome DevTools MCP performance traces.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill debug-optimize-lcp-pgooone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-optimize-lcp
Source: https://github.com/Pgooone/oh-pgone-claudecode/tree/main/.claude/plugins/cache/chrome-devtools-plugins/chrome-devtools-mcp/0.20.3/skills/debug-optimize-lcp
Command: npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill debug-optimize-lcp-pgooone

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Slow Largest Contentful Paint (LCP) hurts user experience and search rankings, but finding the root cause requires deep performance analysis. This Skill provides a structured workflow to record performance traces, break LCP into its four subparts, identify the bottleneck, and apply targeted fixes. ## Core Features & Use Cases - LCP Subpart Analysis: Breaks LCP into TTFB, resource load delay, resource load duration, and element render delay to pinpoint the exact bottleneck. - Guided Debugging Workflow: Uses Chrome DevTools MCP tools (performance traces, insight analysis, network waterfall inspection, and JavaScript evaluation snippets) in a five-step diagnostic sequence. - Prioritized Optimization Strategies: Provides concrete fixes for each subpart, including fetchpriority hints, preload directives, critical CSS inlining, image format optimization, and CDN caching. - Use Case: A developer notices their landing page's hero image takes 5 seconds to appear. Using this Skill, they record a trace, discover a large resource load delay caused by a lazy-loaded LCP image, remove loading="lazy", add fetchpriority="high", and verify the improvement with a follow-up trace. ## Quick Start Ask the AI to debug why my page's LCP is slow by recording a performance trace and analyzing the LCP breakdown.

Frequently Asked Questions about debug-optimize-lcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug slow Largest Contentful Paint on my website?▼

Record a performance trace with reload enabled, then analyze the LCPBreakdown insight to see which of the four subparts (TTFB, resource load delay, resource load duration, element render delay) is the bottleneck. Apply the targeted fix for that subpart and re-run the trace to verify.

What is a good LCP score for Core Web Vitals?▼

A good LCP is 2.5 seconds or less, measured from navigation start until the largest image or text block renders. Scores between 2.5 and 4.0 seconds need improvement, and anything above 4.0 seconds is considered poor.

Why is my LCP image loading late even though it is in the HTML?▼

Common causes include loading="lazy" on the LCP image, images loaded via JavaScript or data-src attributes, and missing fetchpriority hints. The LCP resource should be discoverable in the initial HTML and start loading immediately.

Does lazy loading affect LCP performance?▼

Yes, applying loading="lazy" to the LCP image delays its loading and directly increases resource load delay. Never lazy-load images in the initial viewport; instead add fetchpriority="high" to prioritize the LCP image.

How do I test LCP under slow network conditions?▼

Use the emulate tool with networkConditions set to "Fast 3G" and cpuThrottlingRate set to 4. This surfaces issues that only appear on slower connections and devices, since lab measurements often differ from real-world experience.