optimizing-performance

Start by measuring baseline performance using profiling tools: Node.js profiler for backend code, Python's cProfile for backend services, and Lighthouse for frontend metrics. These tools pinpoint which functions, queries, or assets consume the most time, revealing where to focus optimization efforts.

Profile your database layer to find slow queries, then apply targeted optimizations like adding indexes, reducing N+1 queries, and rewriting inefficient SQL. Re-measure after each change to confirm improvements using baseline comparisons.

Use Lighthouse to measure TTFB and load times, identify large assets in your bundle, then apply fixes like code splitting, lazy loading, and asset compression. Verify improvements by re-measuring with the same tools to confirm performance gains.

Yes. Performance optimization spans all layers: profile frontend assets and rendering, backend CPU and memory usage, and database queries. This skill enforces a data-driven workflow baseline → bottleneck identification → targeted fixes → re-measurement across your entire stack.

No. This skill guides you through common profiling tools like Node.js profiler, Python's cProfile, and Lighthouse with a structured workflow: establish baseline metrics, identify bottlenecks, apply optimizations, then re-measure to validate results.

Optimization without baseline measurement risks wasting effort on non-critical bottlenecks. This skill enforces measurement before and after changes so you target real problems, avoid premature optimization, and verify that fixes actually improve performance.