Performance Profiler & Optimizer FAQs

Question 1

Does it help find memory leaks?

Accepted Answer

Yes, it includes analysis patterns for the DevTools Memory tab to identify growing heaps, retained references, and detached DOM nodes that cause memory bloat.

Question 2

Can I use this for automated performance audits?

Accepted Answer

Yes, the skill includes runtime scripts for automated Lighthouse audits, allowing you to generate performance reports programmatically.

Question 3

What metrics does this skill help monitor?

Accepted Answer

It focuses on industry-standard Core Web Vitals including Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for interactivity, and Cumulative Layout Shift (CLS) for visual stability.

Question 4

How does it help with large JavaScript bundle sizes?

Accepted Answer

It provides a framework for identifying duplicate dependencies, large libraries, and missing code-splits, offering specific actions like tree-shaking and module imports to reduce size.

Question 5

What is the recommended profiling workflow?

Accepted Answer

The skill follows a strict 4-step process: 1. Baseline (measure current state), 2. Identify (find the bottleneck), 3. Fix (apply targeted changes), and 4. Validate (confirm the improvement).

Performance Profiler & Optimizer

主要功能

使用场景

Performance Profiler & Optimizer

主要功能

使用场景