skills.rest
mgd34msu
mgd34msuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

performance-audit

Audit web application performance across bundles, databases, rendering, network, memory, and Core Web Vitals.

6|3|Updated Jan 2, 2026
Search Tags:#performance#database#web vitals#optimization#rendering#audit#bundle analysis
One-click install
npx skills add https://github.com/mgd34msu/goodvibes-plugin --skill performance-audit-mgd34msu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: performance-audit
Source: https://github.com/mgd34msu/goodvibes-plugin/tree/main/plugins/goodvibes/skills/quality/performance-audit
Command: npx skills add https://github.com/mgd34msu/goodvibes-plugin --skill performance-audit-mgd34msu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses slow loading times, poor user experience, and inefficient resource usage in web applications by providing a systematic methodology and automated checks for performance bottlenecks.

Core Features & Use Cases

  • Comprehensive Auditing: Covers bundle analysis, database optimization, rendering, network, memory, server-side performance, and Core Web Vitals.
  • Automated Checks: Utilizes precision tools to identify specific anti-patterns and suggest optimizations.
  • Use Case: A developer can use this Skill to diagnose why their Next.js application is performing poorly, identify the root cause (e.g., large bundle size, N+1 queries), and receive actionable steps to fix it before deployment.

Quick Start

Run a full performance audit on the current project to identify optimization opportunities.

Frequently Asked Questions about performance-audit

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

FAQPage Schema
How do I conduct a web app performance audit to find bottlenecks?▼

A web app performance audit systematically identifies bottlenecks across bundle analysis, database optimization, rendering, network, memory, server-side performance, and Core Web Vitals. It employs automated tool workflows for checks and provides actionable optimization insights.

Why is my Next.js application rendering slowly and experiencing poor Core Web Vitals?▼

Poor Core Web Vitals and slow rendering often stem from large bundle sizes, N+1 database queries, or network bottlenecks. A systematic performance audit uses precise automated checks to diagnose these specific anti-patterns.

Can I use this performance audit on any web application framework?▼

The performance audit methodology applies to web applications generally, analyzing bundle size, database queries, and server-side performance. It is particularly effective for diagnosing framework-specific issues like Next.js rendering bottlenecks.

What is the best way to identify N+1 queries and database optimization opportunities?▼

The best way to identify database optimization issues like N+1 queries is through a systematic performance audit. It checks database interactions alongside rendering and network metrics to isolate root causes and suggest fixes.

Does bundle analysis help reduce large bundle sizes before deployment?▼

Yes, bundle analysis identifies large bundle sizes and resource inefficiencies before deployment. The performance audit workflow targets these specific anti-patterns, providing actionable steps to optimize loading times and resource usage.

Related Skills

Explore More Software Engineering Skills→
josuenavarroaguadojosuenavarroaguado

performance-optimization

Diagnose and fix web performance bottlenecks using Lighthouse, RUM, and profiling data.

Community
Advanced
simoabidsimoabid
1

performance-profiling

Measure Core Web Vitals and analyze runtime and bundle sizes with Lighthouse CLI.

Community
Intermediate
fsollafsolla

high-perf-browser

Analyze network protocols and rendering paths to optimize Core Web Vitals.

Community
Advanced
4lerman4lerman

performance-profiler

Profile Node.js, Python, and Go applications for CPU, memory, and I/O bottlenecks.

Community
Advanced