performance-profiling

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

41|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/DevayoshaUS/Women-scholarship --skill performance-profiling-devayoshaus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: performance-profiling
Source: https://github.com/DevayoshaUS/Women-scholarship/tree/main/hackathon-main%20%281%29/hackathon-main/.agent/skills/performance-profiling
Command: npx skills add https://github.com/DevayoshaUS/Women-scholarship --skill performance-profiling-devayoshaus

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. ## Core Features & Use Cases - Lighthouse Audits: Run automated Lighthouse audits on any URL and receive JSON scores for performance, accessibility, best practices, and SEO. - Core Web Vitals Guidance: Reference targets for LCP, INP, and CLS along with tool selection for page load, bundle, runtime, memory, and network profiling. - Bottleneck Diagnosis: Map symptoms like slow initial load or growing memory to likely causes and prioritized quick-win fixes. - Use Case: A developer notices a page feels slow, runs the Lighthouse audit script to get a baseline score, identifies a large bundle as the bottleneck, applies code splitting, and re-audits to validate the improvement. ## Quick Start Ask the assistant to run a Lighthouse performance audit on your site URL and interpret the scores using the Core Web Vitals targets.

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 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 install -g lighthouse and returns JSON scores for performance, accessibility, best practices, and SEO.

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

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

Which profiling tool should I use for different performance problems?▼

Use Lighthouse for page load issues, a bundle analyzer for bundle size, and Chrome DevTools Performance, Memory, and Network tabs for runtime, memory, and network problems respectively. Match the tool to the symptom before making changes.

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 Lighthouse performance audits?▼

Lighthouse runs in a controlled lab environment, so scores may not reflect real user conditions. The skill recommends complementing it with RUM (Real User Monitoring) data in production to capture actual user experience.