Running a speed test is easy. Most tools will give you a score and a list of recommendations in under a minute. Understanding what those results actually mean - and which recommendation to prioritize - is where most people get stuck. Each of these tools answers a slightly different question about your site's performance.
PageSpeed Insights
pagespeed.web.dev - Google's tool, directly tied to how Google evaluates your site
PageSpeed Insights analyzes your page and returns separate scores for mobile and desktop, each on a scale of 0–100. More importantly, it measures your Core Web Vitals: Largest Contentful Paint (how long until the main content loads), Cumulative Layout Shift (how much the page jumps around as it loads), and Interaction to Next Paint (how quickly the page responds to user input).
These Core Web Vitals scores are the same signals Google uses in its ranking algorithm. A green score across all three on mobile is meaningful for SEO, not just user experience.
PageSpeed Insights also distinguishes between field data (real user measurements from Chrome users who have visited your site) and lab data (a controlled synthetic test run from Google's infrastructure). Field data is more representative of actual visitor experience. If you have enough traffic, prioritize improving your field data scores.
Start with PageSpeed Insights. It is the most directly relevant tool for search ranking implications.
GTmetrix
gtmetrix.com - Best for waterfall charts and historical tracking
GTmetrix provides a waterfall chart - a visual timeline showing every request the browser makes to load your page, in chronological order. Each bar represents one resource (an HTML file, CSS file, JavaScript file, image, font, or API request), and the bar's position and length show when the request started and how long it took.
The waterfall is where you find bottlenecks. Look for:
- Long bars - resources that took a long time to load individually
- Bars that start late - resources blocked from loading until something else finished
- Long chains - one request waiting for another, waiting for another
GTmetrix also tracks your score over time, which is useful for confirming that a change you made actually improved performance.
A free GTmetrix account lets you run tests from Vancouver, Dallas, and a few other locations. Testing from a Canadian server location gives you results more representative of Canadian visitor experience.
WebPageTest
webpagetest.org - Advanced multi-location testing and detailed diagnostics
WebPageTest is the most powerful of these tools and also the most complex. It lets you run tests from dozens of locations worldwide, simulate specific connection speeds and devices, run tests multiple times and report median results, and capture video of the page loading.
The filmstrip view - a series of screenshots taken at regular intervals during the load - is particularly useful for diagnosing visual performance. You can see exactly when content becomes visible versus when the page is fully loaded, and compare your page to competitors side by side.
WebPageTest is overkill for initial diagnostics but valuable when you need to understand a specific problem in depth or verify performance for users in a specific geographic region.
Pingdom Website Speed Test
tools.pingdom.com - Simple, clean, good for monitoring and quick checks
Pingdom's speed test tool is the most beginner-friendly of the group. It provides a clear performance grade, load time, page size, and a list of recommendations sorted by impact. The interface is less overwhelming than WebPageTest and the results are straightforward to interpret.
Pingdom also offers an uptime monitoring product (paid) that pings your site regularly and alerts you if it goes down. This is separate from the speed test tool but worth knowing about.
Chrome DevTools Lighthouse
Built into Chrome - accessible offline, no external service required
Press F12 in Chrome, go to the Lighthouse tab, and run an audit. Lighthouse runs locally in your browser and generates a performance report along with scores for accessibility, best practices, and SEO. Because it runs locally, it reflects your current network conditions - which can be both useful (you can throttle to simulate slow connections) and misleading (a fast office connection will show faster results than a mobile user experiences).
How to Read a Waterfall Chart
The waterfall chart is the most information-dense output across these tools. A few patterns to recognize:
A big gap at the start before any resources load indicates slow server response time (Time to First Byte). This points to server-side performance - caching, database query time, or hosting resource limits.
Many requests loading in sequence rather than in parallel suggests render-blocking resources or scripts that prevent other resources from loading until they finish.
Large images appearing late in the waterfall are often the cause of poor Largest Contentful Paint scores. The fix is compressing images, using modern formats like WebP, and ensuring images are properly sized for the screen they will display on.
Use these tools together: PageSpeed Insights for the Google-relevant score, GTmetrix for the waterfall investigation, and Pingdom for a quick sanity check after you make changes.
