web-perf

Render-blocking resources delay first paint and can be detected by profiling resource timing and mapping network request chains. Analyzing these network dependencies helps stabilize load times by identifying exactly which assets are bottlenecking the initial page render.

Yes, you can analyze network dependencies by listing network requests and getting individual request details during a performance trace. This maps out request chains and caching gaps that delay loading, providing actionable guidance to stabilize page load times.

The best way to debug slow Largest Contentful Paint is to generate a performance trace and analyze the LCPBreakdown insight. This isolates the specific elements and network requests causing the bottleneck, delivering concrete optimization recommendations with estimated impact.

Yes, MCP tooling availability is required to measure web performance metrics like Speed Index. The analysis relies on specific commands such as navigate_page, performance_start_trace, and performance_analyze_insight to perform end-to-end profiling and auditing.

Your web page experiences layout shifts due to dynamically rendered content, quantified as CLS in Core Web Vitals. You can identify them by taking snapshots and running a performance trace to measure CLS, while also checking for common accessibility gaps.