performance-optimization

Fix N+1 queries by replacing per-record lookups with a single query using a join or include clause, such as findMany with include in an ORM. Confirm the fix by checking the database query log before and after the change.

Improve Core Web Vitals by measuring with Lighthouse and the web-vitals library, then targeting the specific bottleneck: optimize hero images and render-blocking resources for LCP, reduce main-thread long tasks for INP, and set explicit image dimensions for CLS.

Add an index only after running EXPLAIN ANALYZE to confirm the query plan lacks a usable index. Index for the query shape with equality columns first, and re-run the plan after, since indexes that do not change the plan still tax every write.

Raising pool size fails because a pool larger than the database can serve just moves the queue somewhere less visible. Find what holds connections first, and for serverless or autoscaling workloads use a multiplexing proxy like pgbouncer instead.

Do not optimize without measurement evidence of a problem. Premature optimization adds complexity that costs more than the performance it gains, and changes that land within run-to-run variance should be reverted rather than kept.