skills.rest
ak-eyther
ak-eytherCOMMUNITY
Explore all skills by this author →
GitHub

performance-testing-patterns

Identify web performance bottlenecks from Lighthouse audits and Core Web Vitals.

Updated Nov 23, 2025
Search Tags:#lighthouse#bundle analysis#performance testing#core web vitals#web optimization#browser profiling
One-click install
npx skills add https://github.com/ak-eyther/model-project --skill performance-testing-patterns-ak-eyther
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: performance-testing-patterns
Source: https://github.com/ak-eyther/model-project/tree/main/codex/skills/performance-testing-patterns
Command: npx skills add https://github.com/ak-eyther/model-project --skill performance-testing-patterns-ak-eyther

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you diagnose slow pages, failing budgets, and regressions before users feel them, turning raw performance signals into clear optimization priorities.

Core Features & Use Cases

  • Lighthouse auditing for performance and accessibility checks.
  • Core Web Vitals monitoring for LCP, FID, and CLS during testing.
  • Bundle analysis and budget tracking for frontend release validation.
  • Use it when you need to compare builds, spot heavy scripts, or confirm a page meets performance targets.

Quick Start

Ask the skill to audit a page or app and summarize the main performance bottlenecks, their likely causes, and the highest-impact fixes.

Frequently Asked Questions about performance-testing-patterns

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

FAQPage Schema
How do I identify web performance bottlenecks using Lighthouse audits?▼

To identify web performance bottlenecks with Lighthouse audits, you process raw audit data to spot slow page elements, heavy scripts, and failing performance budgets, turning those signals into clear optimization priorities and actionable fixes.

What is the best way to measure Core Web Vitals like LCP and CLS during testing?▼

The best way to measure Core Web Vitals like LCP and CLS during testing is to establish repeatable metric collection, allowing you to monitor these vitals, validate performance targets, and detect regressions before users experience them.

How do I track bundle size and validate performance budgets for a frontend release?▼

You track bundle size and validate performance budgets by analyzing your frontend bundle to spot heavy scripts, enabling you to compare builds and confirm the page meets performance targets before a release.

Does this performance testing approach work with Next.js and similar frontend stacks?▼

Yes, this performance testing approach works with Next.js and similar frontend stacks, applying Lighthouse audits, Core Web Vitals measurement, and bundle analysis to ensure compatibility during your development and release checks.

Why do I need repeatable metric collection for browser profiling?▼

Repeatable metric collection for browser profiling is needed to accurately compare builds, validate performance budgets, and confirm optimization fixes actually resolved the web performance bottlenecks without measurement noise.

Related Skills

Explore More Software Engineering Skills→
pekralpekral

benchmark

Measure Laravel performance baselines and detect regressions via standardized tests.

Community
Advanced
namninhndnamninhnd

performance-profiling

Analyze web performance with Lighthouse audits and optimization scripts.

Community
Intermediate
robotijnrobotijn
3

bundle-analyzer

Analyze JavaScript and Blazor WebAssembly bundle sizes for bloat and budget violations.

Community
Advanced
nangyak4415-sudonangyak4415-sudo

optimize

Identify and fix web performance issues in frontend applications.

Community
Intermediate