web-perf

You can audit Core Web Vitals by measuring LCP, INP, and CLS metrics alongside network traces to pinpoint render-blocking resources and layout shift culprits. This requires capturing Chrome DevTools performance tracing to identify specific elements causing poor Lighthouse scores.

LCP regressions are typically caused by render-blocking resources, slow network dependency chains, or delayed rendering of the primary page element. Analyzing the LCPBreakdown trace helps identify the specific network requests delaying your page's largest visual element.

Investigate CLS culprits by capturing a performance trace during page rendering to identify the specific DOM elements shifting during load. Layout shift analysis isolates unstable elements, allowing you to target page optimization efforts toward fixing those specific render behaviors.

Yes, you can capture an accessibility snapshot alongside web performance tracing. It generates an accessibility tree to surface high-level gaps like missing accessible names and focus issues, allowing you to validate both page speed and accessibility health during the same audit.

No, this page optimization audit requires Chrome DevTools performance tracing and insight extraction. It relies on DevTools data to enumerate network requests, analyze LCPBreakdown, and identify render-blocking resources to measure Core Web Vitals accurately.