performance-optimization

Establish performance baselines, diagnose frontend and backend bottlenecks, and verify fixes.

2|Updated May 3, 2026
One-click install
npx skills add https://github.com/Rosetears520/aili-workflows --skill performance-optimization-rosetears520
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-optimization
Source: https://github.com/Rosetears520/aili-workflows/tree/main/skills/performance-optimization
Command: npx skills add https://github.com/Rosetears520/aili-workflows --skill performance-optimization-rosetears520

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you improve application performance by preventing guesswork and focusing on evidence-based bottleneck identification.

Core Features & Use Cases

  • Measure before optimizing: Establish a performance baseline using synthetic tools (e.g., Lighthouse/DevTools) and real-user monitoring (e.g., web-vitals/CrUX).
  • Identify and fix the true bottleneck: Diagnose frontend (LCP/CLS/INP, main-thread work, render-blocking, image/layout issues) and backend (slow queries, N+1 patterns, caching gaps, CPU/memory/latency spikes).
  • Verify and guard against regressions: Re-measure after changes, set performance budgets, and add monitoring/tests to prevent backsliding.

Quick Start

Use performance-optimization when you have evidence of slow load times or Core Web Vitals below target, and you want an evidence-driven plan to measure, fix, verify, and prevent regressions.

Frequently Asked Questions about performance-optimization

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

FAQPage Schema
How do I identify the true bottleneck causing slow load times and poor Core Web Vitals?

To identify performance bottlenecks, establish a baseline using synthetic tools like Lighthouse and real-user monitoring, then diagnose frontend issues like LCP and CLS or backend patterns like N+1 queries to find the true root cause.

What's the best way to fix a low INP score and slow interactions on my web app?

Fixing low INP scores requires profiling main-thread work to diagnose render-blocking resources and slow interactions, applying targeted fixes, and then re-measuring with real-user monitoring to verify the interaction delay is resolved.

How do I prevent performance regressions after optimizing my application?

Prevent performance regressions by re-measuring after changes, setting strict performance budgets, and adding guardrails like monitoring and tests to ensure your Core Web Vitals and load times do not backslide.

Does this profiling-first workflow support diagnosing backend CPU and memory latency spikes?

Yes, the profiling-first workflow supports diagnosing backend bottlenecks including slow queries, N+1 patterns, caching gaps, and CPU, memory, or latency spikes across both web and API workloads.

When should I use real-user monitoring versus synthetic tools like Lighthouse for performance optimization?

Use synthetic tools like Lighthouse to establish initial baselines and diagnose specific bottlenecks, while real-user monitoring like web-vitals captures actual field data to verify Core Web Vitals improvements and catch regressions.