performance-analyzer

Analyze performance bottlenecks by evaluating profiling data, code traces, and Core Web Vitals metrics to identify slowdowns across code, database queries, and rendering workflows, which generates focused optimization steps.

Optimizing slow database queries involves analyzing the query execution to suggest indexing or caching strategies, providing before and after metrics to validate the performance improvement.

Core Web Vitals metrics guide rendering optimizations by pinpointing expensive operations in page rendering paths, allowing for focused performance checks that target and resolve specific visual bottlenecks.

Yes, profiling data and code traces are required to accurately identify expensive operations, enabling the system to generate focused recommendations for improving code and rendering performance.

Yes, you can trigger a focused performance analysis on a specific component, page, or query to isolate and address rendering paths or expensive operations without evaluating the entire application.

Performance analysis requires code traces and profiling metrics because user reports of slowdowns only indicate symptoms, while traces and metrics are needed to pinpoint exact bottlenecks and generate actionable improvements.