Performance
Website Speed Audits: A Repeatable Process That Works
How to run consistent speed audits, interpret results, and prioritize fixes so improvements stick.
Speed audits only help if you run them the same way, interpret them correctly, and fix the right things. Here’s a repeatable process.
Define the test set
Pick a small set of URLs that represent the site: homepage, one key landing page, one list page (e.g. blog index), one content page (e.g. article). Test the same set every time so you can compare before/after. Use a consistent environment: same device/network profile (e.g. Lighthouse “Mobile” or “Desktop”) and same location if possible. Run each URL multiple times and take the median or a stable run so one-off spikes don’t drive decisions.
Tools and metrics
Use Lighthouse (in Chrome DevTools or CI) or PageSpeed Insights for LCP, INP (or TBT/FID in older Lighthouse), and CLS. Prefer field data (CrUX) when available—it reflects real users. Lab data is reproducible and good for debugging. Note both: “Lab says LCP is 2.1s; CrUX says 75th percentile is 2.8s.” Set a simple bar: e.g. “LCP under 2.5s, CLS under 0.1” and track whether the test set passes.
Interpret and prioritize
Lighthouse’s “Opportunities” and “Diagnostics” suggest fixes; prioritize by impact. Often: largest content (image or font), render-blocking resources, and main-thread work. Fix the item that moves the needle the most first (e.g. optimize the LCP image), then re-run. Don’t chase a perfect score; aim for “good” and stable. Document what you changed so the next audit can confirm the gain and so regressions are obvious.
Make it repeatable
Run audits on a schedule (e.g. after each release or monthly). Automate if you can: Lighthouse CI or a script that runs Lighthouse and fails if metrics regress. Store results (e.g. JSON or a dashboard) so you have history. Assign ownership: someone checks the report and follows up on regressions. With a fixed test set, consistent tools, clear priorities, and a schedule, speed audits become a repeatable process that actually improves the site.
Summary
Define a small, fixed set of URLs and test them the same way each time. Use Lighthouse and CrUX; focus on LCP, INP, CLS. Prioritize high-impact fixes and re-run to confirm. Automate and schedule audits so improvements stick and regressions get caught.