performance-profiling

Measure and analyze web performance using Lighthouse audits and Core Web Vitals profiling workflows.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/DucCuong159/Realtime-chatapp --skill performance-profiling-duccuong159
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-profiling
Source: https://github.com/DucCuong159/Realtime-chatapp/tree/main/.agent/skills/performance-profiling
Command: npx skills add https://github.com/DucCuong159/Realtime-chatapp --skill performance-profiling-duccuong159

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lighthouse, and includes scripts (resource) components.

What problem does it solve? Web applications often suffer from slow load times, janky interactions, and memory leaks, but developers frequently guess at causes instead of measuring. This Skill provides a structured measure-analyze-optimize workflow so performance fixes target real bottlenecks rather than assumptions. ## Core Features & Use Cases - Automated Lighthouse Audits: Run scripts/lighthouse_audit.py against any URL to get JSON scores for performance, accessibility, best practices, and SEO. - Core Web Vitals Guidance: Reference targets for LCP, INP, and CLS, plus tool selection for page load, bundle size, runtime, memory, and network problems. - Bottleneck Diagnosis: Symptom-to-cause tables map issues like slow initial load, jank during scroll, and growing memory to likely root causes and prioritized quick wins. - Use Case: A React app feels sluggish after a release. Run the Lighthouse audit to baseline scores, use the profiling workflow to identify a large unsplit bundle, apply code splitting, then re-audit to validate the improvement. ## Quick Start Run a Lighthouse performance audit on https://example.com and tell me which Core Web Vitals need improvement.

Frequently Asked Questions about performance-profiling

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

FAQPage Schema
How do I run a Lighthouse performance audit from the command line?

Run the lighthouse_audit.py script with a target URL, for example: python scripts/lighthouse_audit.py https://example.com. It requires the Lighthouse CLI installed globally via npm and returns JSON scores for performance, accessibility, best practices, and SEO.

What are good Core Web Vitals thresholds for LCP, INP, and CLS?

LCP should be under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 to be considered good. Values above 4.0 seconds for LCP, 500 milliseconds for INP, or 0.25 for CLS are rated poor.

Which profiling tool should I use for different performance problems?

Use Lighthouse for page load issues, a bundle analyzer for bundle size, DevTools Performance tab for runtime problems, DevTools Memory tab for leaks, and DevTools Network tab for request issues. Match the tool to the symptom before optimizing.

Why does the Lighthouse audit script fail with a command not found error?

The script depends on the Lighthouse CLI being installed globally. Install it with npm install -g lighthouse, then rerun the script. The script also times out if the audit exceeds 120 seconds.

What are the limitations of automated Lighthouse audits?

Lighthouse runs in a simulated lab environment, so scores may differ from real user experience. Combine it with Real User Monitoring in production and always validate optimizations against actual user data rather than lab scores alone.