performance-optimizer

Topics in the source

• Performance Optimizer
• When to Use This Skill
• The Optimization Process
• 1. Measure First
• 2. Find the Bottleneck
• 3. Optimize
• Common Optimizations
• Database Queries

Find and fix performance bottlenecks. Measure, optimize, verify. Make it fast. App is slow or laggy User complains about performance Page load times are high API responses are slow Database queries take too long User mentions "slow", "lag", "performance", or "optimize" Never optimize without measuring: What to measure: Page load time API response time Database query time Function execution time Memory usage Network requests Use profiling tools to find the slow parts: Browser: Node.js: Database: Fix the slowest thing first (biggest impact). Problem: N+1 Queries Problem: Missing Index Problem: SELECT Problem: No Pagination Problem: No Caching Problem: Sequential Operations Problem: Large Payloads Problem: Unnecessary Re-renders Problem: Large Bundle Problem: No Code Splitting Problem: Unoptimized Images Problem: Inefficient Algorithm Problem: Repeated Calculations Problem: Memory Leak Problem: Large Data in Memory Always measure before and after: Set targets: Browser: Chrome DevTools Performance tab Lighthouse (audit) Network tab (waterfall) Node.js: node --prof (profiling) clinic (diagnostics) autocannon (load testing) Database: EXPLAIN ANALYZE (query plans) Slow query log Database

This is an excerpt. Refer to the complete source and its current requirements.