performance-audit

To audit web performance bottlenecks, you establish a baseline using Lighthouse and WebPageTest, analyze your bundle size, and profile runtime in Chrome DevTools to pinpoint slow pages. This repeatable workflow identifies key metrics for optimization.

The best way to profile runtime and analyze bundle size is to use Chrome DevTools for runtime profiling alongside bundle-size analysis. This approach pinpoints specific bottlenecks causing slow pages in your web application.

Yes, you can use this performance audit workflow for pre-release gates, post-release reviews, and ongoing optimization of slow pages across production sites. It establishes baselines to verify improvements and catch regressions.

You establish a baseline to optimize Core Web Vitals by running Lighthouse audits to identify slow pages and key metrics. Comparing baseline results over time verifies improvements and prevents performance regressions.

You do not necessarily need to run Chrome DevTools and Lighthouse simultaneously to fix web performance issues. Lighthouse drives baseline audits, while DevTools handles runtime profiling, and WebPageTest provides additional baseline data.

A limitation of using Lighthouse for web performance audits is that it provides baseline metrics but may not fully capture runtime bottlenecks. You must combine it with bundle-size analysis and Chrome DevTools profiling to pinpoint all slow pages.