Website Performance Audit: How to Use Lighthouse, PageSpeed Insights, and WebPageTest

You know your website is slow, but you don’t know why. Or maybe you think it’s fast because it loads quickly on your office’s fiber connection. The truth is buried in data — and three free tools can extract it in minutes: Google Lighthouse, PageSpeed Insights, and WebPageTest. Together, they provide a complete picture of your website’s performance, identify specific bottlenecks, and prioritize the fixes that will have the most impact.

Website performance isn’t just a technical concern — it directly impacts revenue. A 1-second delay in load time reduces conversions by 7%, according to Akamai. For a site generating $10,000/month in revenue, that’s $700/month lost to slow pages. The first step in fixing the problem is measuring it accurately.

Google Lighthouse: The Comprehensive Audit

Lighthouse is built into Chrome DevTools and runs a thorough audit scoring your site on Performance, Accessibility, Best Practices, and SEO. Each category scores 0-100, with detailed recommendations for improvement.

Key Performance Metrics

Lighthouse measures six performance metrics, but three matter most for business impact: Largest Contentful Paint (LCP) measures when the main content becomes visible — target under 2.5 seconds. Interaction to Next Paint (INP) measures responsiveness to user input — target under 200 milliseconds. Cumulative Layout Shift (CLS) measures visual stability — target under 0.1. These three metrics are Google’s Core Web Vitals, and they directly influence search rankings.

Running a Lighthouse Audit

Open Chrome DevTools (F12), navigate to the Lighthouse tab, select “Performance” and “Mobile” (mobile is what Google uses for ranking), and click “Analyze page load.” The audit takes 30-60 seconds and produces a detailed report with scores, metric values, and prioritized improvement opportunities. Run the audit three times and use the median score — network and CPU variability can cause single-run results to fluctuate.

PageSpeed Insights: Real-World Data

PageSpeed Insights (pagespeed.web.dev) provides two datasets: lab data (a Lighthouse test run on Google’s servers) and field data (real user measurements collected from Chrome users who visit your site). Field data is more valuable because it reflects actual user experience, not a simulated test environment.

If field data shows your LCP is 4.2 seconds but lab data shows 2.8 seconds, the real-world experience is worse than your test suggests — probably due to users on slower connections or older devices. Always prioritize field data when it’s available.

WebPageTest: The Deep Dive

WebPageTest (webpagetest.org) offers the most detailed performance analysis of any free tool. It provides filmstrip views (showing exactly what the visitor sees at each point during page load), waterfall charts (showing every network request in sequence), connection views (showing server response times, DNS lookups, and TLS handshakes), and repeat visit testing (showing the impact of caching).

The Waterfall Chart

The waterfall chart is the most diagnostic view. Each horizontal bar represents a resource (HTML, CSS, JavaScript, image, font) and its loading timeline. Long bars indicate slow resources. Resources that don’t start loading until after others complete indicate render-blocking dependencies. The waterfall reveals the specific resources causing bottlenecks — knowledge that turns vague “make it faster” goals into specific, actionable tasks.

Common Performance Issues and How to Fix Them

After running all three tools, you’ll likely see a pattern. The most common issues for business websites are unoptimized images (the fix: compress and serve modern formats), too many third-party scripts (analytics, chat widgets, social embeds — each one adding hundreds of milliseconds), render-blocking CSS and JavaScript (the fix: defer non-critical resources), no caching (the fix: set appropriate cache headers for static assets), and slow server response time (the fix: upgrade hosting or implement a CDN). For more on this topic, see our guide on caching strategies. Addressing just the top three issues typically improves load time by 40-60%, which translates directly to better conversion rates and revenue.

Building a Performance Budget

A performance budget sets maximum thresholds for page weight, number of requests, and load time. For example: maximum page weight of 1.5MB, maximum of 50 HTTP requests, LCP under 2.5 seconds on 4G connections. When a new feature or content change exceeds the budget, something else needs to be optimized or removed to compensate. Performance budgets prevent the gradual bloat that turns a fast site into a slow one over months and years.

Making Performance Audits Routine

A performance audit isn’t a one-time event. Run monthly audits to catch regressions, set up automated monitoring with tools like SpeedCurve or Calibre for continuous tracking, and test after every significant change (new plugin, design update, content addition). The businesses with consistently fast websites aren’t lucky — they measure regularly and fix issues before they compound.

The difference between a website that loads in 1.5 seconds and one that loads in 4 seconds might seem small, but it represents a 100%+ difference in bounce rate and a significant ranking disadvantage. Performance optimization is one of the highest-ROI improvements any website can make, and building for speed from the architecture level is something Studio Aurora prioritizes in every project.