performance-optimization

Diagnose and fix frontend and backend performance bottlenecks using a measure-first optimization workflow.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/insightriot/signal --skill performance-optimization-insightriot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: performance-optimization
Source: https://github.com/insightriot/signal/tree/main/plugin/skills/review/performance-optimization
Command: npx skills add https://github.com/insightriot/signal --skill performance-optimization-insightriot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Slow applications and unmeasured optimization attempts waste effort and degrade user experience. This Skill enforces a disciplined measure-identify-fix-verify-guard cycle so performance work targets real bottlenecks instead of guesses. ## Core Features & Use Cases - Five-Step Optimization Workflow: Measure baselines with synthetic and real-user monitoring, profile to identify actual bottlenecks, fix them, verify with before/after numbers, and guard against regression with CI budgets. - Core Web Vitals Guidance: Concrete thresholds for LCP, INP, and CLS plus instrumentation examples using the web-vitals library. - Anti-Pattern Fixes: Ready-to-apply corrections for N+1 queries, unbounded data fetching, unoptimized images, unnecessary React re-renders, oversized bundles, and missing caching. - Use Case: Your dashboard's LCP regressed to 5 seconds after a release. Use this Skill to profile the page, find render-blocking resources and an N+1 query, apply fixes, and confirm LCP drops below 2.5 seconds. ## Quick Start Use the performance-optimization skill to profile my app's slow dashboard page and fix the bottlenecks you find.

Frequently Asked Questions about performance-optimization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix slow page load times in a web app?▼

Start by measuring with Lighthouse and real-user monitoring to establish a baseline, then profile to find the actual bottleneck. Common fixes include optimizing images with responsive srcset, code-splitting large bundles, and eliminating render-blocking resources.

How to fix N+1 queries in a database-backed application?▼

N+1 queries are fixed by replacing per-record lookups with a single query using joins or includes, such as Prisma's include option. Profile query logs first to confirm the pattern exists before rewriting data access code.

What are good Core Web Vitals thresholds?▼

Good thresholds are LCP at or under 2.5 seconds, INP at or under 200 milliseconds, and CLS at or under 0.1. Scores above 4.0 seconds LCP, 500 milliseconds INP, or 0.25 CLS are considered poor.

When should I not optimize performance?▼

Avoid optimizing before you have profiling evidence of a real problem. Premature optimization adds complexity without proven benefit, so measure first and only fix bottlenecks that data confirms.

How do I prevent performance regressions in CI?▼

Add bundle size checks, Lighthouse CI for Core Web Vitals, and performance budgets for critical paths to your pipeline. Backend latency alerts and query logging catch server-side regressions before users notice.