performance-engineer

To identify performance bottlenecks across the full stack, you can run an end-to-end profiling pass to measure API latency, frontend render times, and database query efficiency under production-like workloads.

The best way to measure API latency in staging is by running a load test using tools like k6 or Artillery against your deployment, which helps validate scale and identify top latency hotspots under stress.

To profile frontend render times and validate core web vitals, you use browser profiling tools like Chrome DevTools and Lighthouse to measure rendering efficiency against a defined performance budget.

Yes, a defined performance budget is required to validate improvements, check for regressions during CI, and ensure that frontend render times and API latency meet acceptable thresholds before release.

Yes, you can use k6 or Artillery to execute load testing scripts for capacity planning, validating system scale and generating an optimization plan with measurable improvements and CI regression checks.

You should not rely on flamegraphs for memory analysis when lacking a staging environment or production-like workloads, as baseline profiling requires representative deployment conditions to accurately locate bottlenecks.