How to Run a Useful Website Performance Audit
A focused method for finding the website performance issues that affect real visitors and deciding what to fix first.
A performance audit should lead to a prioritized decision, not a long list of scores. Start with the pages people actually use: a key landing page, a high-intent service page, a representative article, and a conversion path.
Test a realistic experience
Run a lab test on a mobile-sized connection, then compare it with real-user data when available. Look at initial loading, interaction delay, layout movement, and the requests made before a visitor can act. A fast desktop on office Wi-Fi is not the whole story.
Identify the biggest contributors
Large unoptimized images, render-blocking font files, third-party scripts, excess JavaScript, and slow server work are common causes. Do not optimize a tiny resource while a hero image or tag manager dominates the page weight.
Link the issue to a visitor task
Translate technical work into the moment it affects: a form that becomes usable late, a price table that shifts, or a navigation control that ignores a tap. This gives product, design, and engineering a shared reason to prioritize the repair.
Retest after the change
Record the before and after result, test the same routes and device class, and confirm nothing important regressed. Performance is an operating practice, not a one-time launch activity.