How to Test Website Speed: The Tools and Metrics That

Why You Should Actually Test Your Speed (Not Just Guess)

Most contractors think their website is fast because it opens quickly on their office Wi-Fi with a brand new laptop. That is the worst possible test environment. Your customers are on phones, on cell networks, in trucks, at job sites. What feels instant to you can feel painfully slow to a buyer who is debating between you and the next listing.

Testing your speed gives you real numbers. Numbers tell you what to fix. Without numbers, you are just guessing while your slow site quietly bleeds leads to faster competitors. Site speed is also a direct ranking factor through Google's Core Web Vitals, so this is not a vanity exercise. Slow sites lose visibility too.

The Tools That Matter in 2026

You do not need expensive monitoring software. Three free tools cover 95 percent of what a local business needs to know.

Google PageSpeed Insights

The default. Go to pagespeed.web.dev, paste a URL, and Google runs both a mobile and desktop test using Lighthouse and real-world Chrome User Experience Report (CrUX) data. You get a 0 to 100 score, your Core Web Vitals, and a prioritized list of fixes.

Test the URLs that actually drive traffic and leads: your homepage, your top 3 service pages, your busiest location page, and your highest-traffic blog post. Not just the homepage.

Google Search Console

Search Console has a Core Web Vitals report under the Experience section. Unlike PageSpeed Insights (which tests one page at a time), Search Console aggregates real visitor data across your whole site and groups pages by performance. This is how you find which templates or page types are dragging you down. Pair this with the broader website audit process for the full picture.

WebPageTest

When you need to dig deeper, webpagetest.org gives you waterfall charts, filmstrips, and the ability to test from specific cities, browsers, and connection speeds. It is the tool to use when PageSpeed says your site is slow but you cannot see why. The filmstrip view alone is worth learning - you can literally watch your page paint frame by frame.

Pingdom, GTmetrix, and Others

These work fine too, but they often use different scoring methods than Google. If you have to pick one source of truth, pick Google. Google is what ranks you.

The Metrics That Actually Matter

Forget the 0 to 100 score for a second. Focus on the specific metrics underneath it, because those are what Google uses to rank and what users actually feel.

Largest Contentful Paint (LCP). How long it takes for the biggest visible element on the page (usually the hero image or headline) to render. Good is under 2.5 seconds. If your LCP is 4 seconds, your visitor stared at a half-loaded page for 4 seconds before seeing anything useful.

Interaction to Next Paint (INP). Replaced First Input Delay in 2024. Measures how responsive your page is to taps and clicks across the whole session. Good is under 200 milliseconds. Bad means buttons feel laggy.

Cumulative Layout Shift (CLS). Measures unexpected layout shifts during page load - the kind that make you tap the wrong button because the content jumped. Good is under 0.1. Common causes are images without dimensions and late-loading ads or banners.

Time to First Byte (TTFB). How long the server takes to start responding. Good is under 800 milliseconds. High TTFB usually means slow hosting or a bloated CMS.

The Core Web Vitals deep dive breaks down each metric in plain English with real fixes. The website speed business case covers what those scores cost you in actual revenue.

How to Run a Real Test (Not a Vanity One)

Here is the playbook to actually get useful data out of any speed test.

1. Use an incognito or private window. Cached pages give you better numbers than real visitors see.
2. Test on mobile first. Mobile is what Google indexes and what most of your visitors use.
3. Test from a slow network. PageSpeed Insights simulates 4G. WebPageTest lets you pick 3G or worse. Most real cell connections are not as fast as you assume.
4. Test the right pages. Homepage, top service pages, top service area pages, top blog posts. Run each one at least twice and average the scores.
5. Test before and after every major change. New plugin? Re-test. New hero image? Re-test. New chat widget? Definitely re-test.

What the Score Actually Tells You

A PageSpeed score of 90+ does not mean your site is perfect. It means it scored well on a synthetic test. Real-world data from Search Console matters more in the long run.

A score of 50 is not a death sentence. Most contractor sites built on bloated template platforms score in the 30 to 60 range on mobile. The path to improvement is mechanical: compress images, reduce JavaScript, fix layout shifts, host on faster infrastructure. None of it requires hiring a research team.

Pay more attention to the diagnostics section than the headline number. PageSpeed tells you specifically which images are oversized, which scripts are blocking rendering, and which fonts are slowing first paint. That is your to-do list.

The Most Common Speed Killers on Contractor Sites

Across hundreds of contractor sites, the same five issues come up over and over:

• Massive, uncompressed images. A 4 MB hero photo from a phone is the single most common offender. Compressing and resizing to a few hundred KB usually cuts LCP in half. The image optimization guide walks through how to do this cleanly.
• No content delivery network. If your site is hosted in one location and served to visitors across multiple states, every visitor pays a network penalty. A CDN fixes this in an afternoon.
• Page builders and plugin bloat. WordPress sites with 30 plugins and a heavy page builder are doomed to score poorly. The Next.js vs WordPress comparison covers the platform tradeoffs.
• Third-party scripts. Chat widgets, popups, tracking pixels, social media embeds. Each one adds weight. Audit which ones actually drive revenue and remove the rest.
• Slow shared hosting. $5 a month hosting saves you nothing if it costs you leads. Decent hosting starts in the $20 to $50 range.

Turning Test Results Into Real Fixes

Speed testing is only useful if you act on what it tells you. Here is the priority order most contractor sites should follow:

1. Fix images first. Biggest single win, lowest effort. Compress, resize, convert to WebP or AVIF, lazy-load below the fold.
2. Audit third-party scripts. Remove every script that does not produce traceable revenue.
3. Move to fast hosting with a CDN. If your TTFB is over 1 second, your infrastructure is the bottleneck.
4. Reduce JavaScript. This is harder and may require rebuilding on a modern stack.
5. Address layout shift. Set width and height on every image, reserve space for ads and embeds.
6. Re-test and document. Keep a spreadsheet of scores before and after each change.

If the audit reveals deeper issues, the complete website rebuild from webIQ ships sites with PageSpeed scores in the 95+ range out of the gate, with CDN, image optimization, and modern stack baked in. Each industry build gets the same performance baseline. If you want to see what a fast site does for your numbers, get started here.

Frequently Asked Questions

What is a good website speed score?

On Google PageSpeed Insights, aim for 90+ on desktop and 80+ on mobile. More importantly, all three Core Web Vitals should pass: LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1. The headline score is less important than the underlying metrics.

How often should I test my website speed?

Monthly at minimum, and after every significant change to your site (new images, new plugins, new tracking scripts, new pages). Google Search Console will alert you to ongoing issues, but proactive testing catches problems before they cost rankings.

Why does my site score differently each time I test it?

Speed tests have natural variance because they depend on network conditions, server load, and which assets are cached. Run each test 2 or 3 times and use the median score. Big jumps usually mean something changed on your site or your hosting environment.

Does mobile speed matter more than desktop speed?

Yes, by a wide margin. Google uses mobile-first indexing, meaning your mobile site is what gets ranked. Most local searches happen on phones. A fast desktop site with a slow mobile site is still a slow site as far as Google is concerned.

Can I just hire someone to fix my site speed?

You can, but the underlying causes (bad hosting, bloated CMS, untrained image uploads) tend to come back if the platform is the problem. A one-time speed audit fixes today's issues. A faster foundation fixes them permanently.