gezel Gezel Handboek

Performance Audit

Audit an application or page for performance problems with measurements, then produce a report of the highest-impact optimizations. First scopes the workloads and locks a performance budget and checklist (load time and Core Web Vitals, bundle/asset weight, render and main-thread cost, network waterfall and request count, server/query latency, memory and re-render churn), then MEASURES each against a baseline using real profiling rather than guessing, then writes a report that ranks bottlenecks by impact-vs-effort with a specific fix and the expected gain for each. Use this for a performance audit, speed optimization, finding bottlenecks, a Lighthouse-style review, reducing load time, or profiling slowness — it grounds every recommendation in a measured number and an estimated payoff, not 'it feels slow'.

How it runs

#StepWho runs itWhat happens
1Scope the perf budgetReviewerlock workloads, a budget, and a metrics checklist
2Measure the baselineDeveloperprofile each workload, locate the real bottlenecks
3Write the perf reportReviewerrank optimizations by impact vs effort
4EvaluateReviewerGrade the deliverable against every acceptance criterion. All pass → finish; any fail → loop back and fix the gap.
5FinishDeveloperAll acceptance criteria met. Stamp a short summary and report DONE.

Say something like "performance audit" or "why is this slow" or "find the bottleneck" or "optimize load time" or "speed this up" or "profile the app" in chat to start it.

Watch this article as a slideshow