debug-optimize-lcp

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

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/rithm84/Manor --skill debug-optimize-lcp-rithm84
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-optimize-lcp
Source: https://github.com/rithm84/Manor/tree/main/.agents/skills/browser-related/chrome-devtools-mcp/debug-optimize-lcp
Command: npx skills add https://github.com/rithm84/Manor --skill debug-optimize-lcp-rithm84

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Slow Largest Contentful Paint hurts user experience and search rankings, but finding the real bottleneck among TTFB, resource load delay, load duration, and render delay is difficult without a structured debugging process. ## Core Features & Use Cases - LCP Subpart Breakdown: Records a performance trace with reload and analyzes LCPBreakdown, DocumentLatency, RenderBlocking, and LCPDiscovery insights to pinpoint the bottleneck subpart. - Element and Network Inspection: Identifies the exact LCP element via PerformanceObserver snippets and checks the network waterfall for late-starting or slow-loading resources. - Prioritized Optimization Guidance: Provides targeted fixes per subpart, such as fetchpriority hints, preload links, critical CSS inlining, modern image formats, and CDN caching, plus Fast 3G and CPU throttling emulation for verification. - Use Case: A developer notices a landing page's hero image takes 5 seconds to appear. The skill records a trace, reveals a large resource load delay caused by a lazy-loaded image, and recommends removing loading="lazy" and adding fetchpriority="high". ## Quick Start Ask the agent to debug why my page's Largest Contentful Paint is slow and suggest optimizations using Chrome DevTools.

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 a slow Largest Contentful Paint score?

Record a performance trace with reload enabled, then analyze the LCPBreakdown insight to see which of the four subparts (TTFB, resource load delay, load duration, render delay) dominates. Targeted fixes depend on which subpart is the bottleneck.

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 optimized?

Late loading usually means resource load delay: the image is loaded via JavaScript or CSS, uses data-src, or has loading="lazy". Use a standard img tag with src, add fetchpriority="high", or preload the image so it is discoverable in the initial HTML.

Does lazy loading affect LCP performance?

Yes, applying loading="lazy" to the LCP image delays its discovery and load start, directly increasing LCP. Never lazy-load images visible in the initial viewport; reserve lazy loading for below-the-fold images.

How can I test LCP under real-world network conditions?

Use the emulate tool with networkConditions set to Fast 3G and a cpuThrottlingRate of 4 to simulate slower devices and connections. This surfaces LCP issues that lab measurements on fast machines often hide.