debug-optimize-lcp

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

Updated Feb 8, 2023
One-click install
npx skills add https://github.com/mvellandi/winky --skill debug-optimize-lcp-mvellandi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-optimize-lcp
Source: https://github.com/mvellandi/winky/tree/main/.agents/skills/debug-optimize-lcp
Command: npx skills add https://github.com/mvellandi/winky --skill debug-optimize-lcp-mvellandi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps developers diagnose and optimize Largest Contentful Paint (LCP) to improve perceived speed and Core Web Vitals.

Core Features & Use Cases

  • Performance tracing and diagnostics to identify LCP bottlenecks.
  • Identify the LCP element and resource timing to guide fixes.
  • Guidance on applying optimization strategies (preloads, fetchpriority, and reducing render-blocking resources).
  • Use Case: Improve LCP on hero image-heavy landing pages across desktop and mobile.

Quick Start

Analyze the page with a performance trace and then apply recommended LCP optimizations.

Frequently Asked Questions about debug-optimize-lcp

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

FAQPage Schema
How do I diagnose a slow Largest Contentful Paint using Chrome DevTools?

To diagnose a slow Largest Contentful Paint (LCP), record a performance trace in Chrome DevTools, analyze LCP insights to identify the LCP element, and inspect network activity to find resource loading bottlenecks impacting page rendering.

What is the best way to optimize Largest Contentful Paint for Core Web Vitals?

The best way to optimize Largest Contentful Paint for Core Web Vitals is to apply proven strategies like adding preloads, setting fetchpriority on hero images, and reducing render-blocking resources to speed up initial page rendering.

Why is my LCP element loading slowly on mobile landing pages?

Your LCP element may be loading slowly due to hero image latency or render-blocking resources. Analyzing network activity and resource timing with Chrome DevTools diagnostics identifies the specific bottlenecks delaying initial rendering on mobile.

Can I use Chrome DevTools MCP to fix frontend performance issues on any web page?

Yes, you can use Chrome DevTools MCP to fix frontend performance issues on any web page experiencing slow initial rendering or Core Web Vitals concerns, provided you can record a performance trace to analyze LCP insights and network activity.

What are the limitations of using performance traces to debug LCP?

Performance traces debug LCP by identifying resource timing and render-blocking issues, but they require manual implementation of the suggested optimizations like preloads and fetchpriority to actually speed up page rendering and resolve the bottlenecks.