performance-profiling

Identify web application performance bottlenecks using Lighthouse and Core Web Vitals.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/capaas2/Site-teste --skill performance-profiling-capaas2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-profiling
Source: https://github.com/capaas2/Site-teste/tree/main/.agent/skills/performance-profiling
Command: npx skills add https://github.com/capaas2/Site-teste --skill performance-profiling-capaas2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps identify and fix performance issues in web applications by guiding measurement first, then targeted analysis, and finally validation after improvements. It prevents guesswork and focuses effort on the biggest bottlenecks affecting speed, responsiveness, and stability.

Core Features & Use Cases

  • Core Web Vitals Guidance: Evaluate LCP, INP, and CLS against practical targets for loading, interactivity, and visual stability.
  • Profiling Workflow: Follow a repeatable baseline → identify → fix → validate process for page load, runtime, memory, and network issues.
  • Bundle and Runtime Analysis: Detect large dependencies, duplicate code, long tasks, layout thrashing, and memory leaks.
  • Use Case: A frontend team can use this Skill to audit a slow dashboard, identify the heaviest scripts, and prioritize the quickest wins that improve real user experience.

Quick Start

Ask the skill to profile your application and identify the top performance bottlenecks, then recommend the highest-impact fixes.

Frequently Asked Questions about performance-profiling

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

FAQPage Schema
How do I identify web application performance bottlenecks using Core Web Vitals?

To identify performance bottlenecks, evaluate Core Web Vitals like LCP, INP, and CLS against practical targets for loading, interactivity, and visual stability to find the biggest issues affecting speed.

What is the best way to profile a slow frontend dashboard and find heavy scripts?

The best way to profile a slow dashboard is running a bundle and runtime analysis to detect large dependencies, duplicate code, long tasks, and layout thrashing, prioritizing the quickest wins for users.

How does the baseline identify fix validate workflow work for runtime debugging?

The workflow for runtime debugging establishes a performance baseline, identifies bottlenecks, applies targeted fixes, and uses script-driven reporting to validate that improvements resolve the interactivity issues.

Can I use Lighthouse-based measurement to detect memory leaks and long tasks?

Yes, Lighthouse-based measurement and script-driven reporting can be applied to detect memory behavior issues like memory leaks, long tasks, and network problems during frontend debugging and audit workflows.

Does bundle analysis help fix page load and interactivity issues in frontend debugging?

Yes, bundle analysis helps fix page load issues by detecting large dependencies and duplicate code, which directly improves loading speed and runtime interactivity during the frontend debugging process.