perf

You can identify Core Web Vitals bottlenecks by running a frontend performance audit that analyzes LCP, CLS, and FID across critical routes and builds. The audit returns a structured report quantifying specific rendering delays and layout shifts.

The best way to reduce JavaScript bundle size is through an audit that analyzes build outputs against set thresholds. It provides optimization recommendations like code-splitting, lazy loading, and asset optimizations to minimize the final payload.

This performance audit works on both typical frontend applications and server-rendered pages. It evaluates critical routes, user interactions, and build outputs across these environments to detect performance issues accurately.

To generate a baseline performance report, you run an initial audit on your current web project. This evaluates Lighthouse patterns and Core Web Vitals to establish a starting point for subsequent optimization tracking.

A high First Input Delay often stems from heavy JavaScript execution blocking user interactions. Diagnose it by running a performance audit that quantifies FID across critical routes and identifies specific script execution bottlenecks.

A structured performance report specifies required outputs including LCP, CLS, and FID targets alongside bundle-size thresholds. It also provides recommended optimizations to meet these baseline performance goals.