performance-profiling

Profile Node.js, browser, React, and database performance to rank bottlenecks.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill performance-profiling-cenredjun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-profiling
Source: https://github.com/CenredJun/openclaw-claudecode-setup-kit/tree/main/skills/performance-profiling
Command: npx skills add https://github.com/CenredJun/openclaw-claudecode-setup-kit --skill performance-profiling-cenredjun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Pinpoints where an application spends time or memory and turns profiling data into ranked, actionable remediation steps so teams stop guessing and start fixing true bottlenecks.

Core Features & Use Cases

  • Full-stack profiling: CPU and heap profiling for Node.js, flame graphs, event loop utilization, and heap snapshots to detect leaks.
  • Frontend analysis: Chrome Performance, Core Web Vitals, React Profiler and why-did-you-render guidance for render and layout issues.
  • Database and query diagnosis: EXPLAIN ANALYZE guidance and pg_stat_statements queries to find slow or excessive queries and N+1 problems.
  • Use Case: Diagnose a slow API endpoint by running a CPU profile, generating a flame graph, correlating slow SQL queries via EXPLAIN ANALYZE, and returning prioritized fixes with estimated impact.

Quick Start

Run a full-stack profiling session and return a ranked list of bottlenecks with concrete remediation steps and estimated impact.

Frequently Asked Questions about performance-profiling

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

FAQPage Schema
How do I find and fix application performance bottlenecks in a Node.js backend?

To find Node.js performance bottlenecks, apply CPU and memory profiling tools to generate flame graphs and heap snapshots. This identifies event loop utilization and memory leaks, producing prioritized remediation steps like offloading heavy CPU work to workers.

Why does my React component re-render so often and how can I profile it?

Profile React component re-renders using React Profiler traces and Chrome DevTools to detect layout issues. Interpreting these traces identifies unnecessary renders, yielding actionable fixes like memoizing components to improve Core Web Vitals.

What is the best way to diagnose slow PostgreSQL queries causing API latency?

Diagnose slow PostgreSQL queries by analyzing EXPLAIN ANALYZE output and querying pg_stat_statements. This identifies N+1 problems and missing indexes, returning prioritized fixes with estimated impact to resolve database bottlenecks.

Can I correlate frontend rendering issues with backend CPU profiles for a slow API endpoint?

Yes, you can correlate frontend rendering and backend CPU profiles during a full-stack profiling session. It correlates slow SQL queries via EXPLAIN ANALYZE with Chrome Performance traces to return a ranked list of full-stack bottlenecks.

Do I need heap snapshots to find memory leaks in Node.js?

Yes, generating heap snapshots is required to detect memory leaks in Node.js applications. Analyzing these snapshots alongside event loop utilization metrics pinpoints memory bottlenecks and yields clear next actions for remediation.