performance-engineer

To resolve performance degradation, follow a symptom-to-baseline-to-hotspot-to-verify workflow that guides profiling and optimization across frontend, backend, and database layers until target metrics are satisfied.

Reducing p95 and p99 latency requires disciplined load testing using realistic data, peak scenarios, warmups, and multiple iterations, paired with prioritized optimizations across algorithms, caching, and database queries.

Improving web vitals involves aligning concrete frontend thresholds like LCP, INP, and CLS through a measurement-to-optimization plan that profiles hotspots and validates responsiveness improvements against your defined metric goals.

Yes, you can verify database tuning changes through regression monitoring and load test verification, ensuring query and index optimizations yield measurable latency, reliability, and responsiveness improvements in production-like scenarios.

When optimizing slow database queries and application latency, follow an ordered optimization approach prioritizing algorithms first, then caching, database queries, code changes, and finally infrastructure adjustments to maximize impact.

Yes, this approach diagnoses slow user experiences by profiling latency, errors, and resource bottlenecks in production-like scenarios, applying repeatable load testing discipline to ensure measurable and reliable system improvements.