A fast website isn't optional anymore. Google uses page speed as a direct ranking factor, and your visitors make snap judgments about your site within the first second of loading. If your pages take longer than 2.5 seconds to become visually complete, you're bleeding traffic, rankings, and revenue without even knowing it.

The short answer: use Google PageSpeed Insights to check your website speed for free. Enter your URL, and you'll get a performance score from 0 to 100 along with real-world data from actual Chrome users. A score of 90 or above is considered good. Below 50 means your site has serious performance problems that are actively hurting your SEO.

But a single score only tells part of the story. In this guide, we'll walk through the three best free tools to test your site speed, explain what every metric means in plain language, and show you exactly how to interpret the results so you can take action. If you want all of this done automatically alongside 140+ other SEO checks, run a TrackSEO report for $2.99 and get a complete performance breakdown in minutes.

Why Does Website Speed Matter for SEO?

Let's get specific about why speed deserves your attention. It's not just about impatient visitors.

Google uses speed as a ranking signal. Since 2021, Core Web Vitals have been part of Google's page experience ranking system. Pages that meet the "good" thresholds for LCP, INP, and CLS get a ranking boost compared to slower competitors. In competitive niches, this can be the difference between page one and page two.

Slow pages kill conversions. Research from Google and Deloitte consistently shows that every extra second of load time reduces conversions by roughly 7-12%. A site loading in 1 second converts at nearly 3x the rate of one loading in 5 seconds. For an e-commerce store doing $100,000 per month, shaving one second off load time could mean an extra $7,000 to $12,000 in monthly revenue.

Bounce rates skyrocket with slow loads. Google's data shows that as page load time goes from 1 second to 3 seconds, the probability of bounce increases by 32%. At 5 seconds, it jumps to 90%. Your content might be incredible, but nobody will see it if the page doesn't load fast enough.

Mobile performance is even more critical. Over 60% of all web traffic now comes from mobile devices, where connections are often slower and processors less powerful. A page that loads in 2 seconds on desktop might take 5 or 6 seconds on a phone over a 4G connection. Google's mobile-first indexing means your mobile speed score is what matters most for rankings.

The 3 Best Free Tools to Check Your Website Speed

You don't need to pay for speed testing. These three tools give you everything you need, and each one offers a slightly different perspective on your performance.

1. Google PageSpeed Insights (Best for SEO-Focused Testing)

PageSpeed Insights (PSI) is the gold standard for website speed testing because it combines two types of data: lab data (simulated tests) and field data (real user measurements from the Chrome User Experience Report). The field data is what Google actually uses in its ranking algorithm, making PSI the most directly relevant tool for SEO.

How to use it step by step:

  1. Go to pagespeed.web.dev in your browser.
  2. Enter your full URL (include https://) in the search bar.
  3. Click Analyze and wait 15-30 seconds for results.
  4. Review your Performance score (0-100) at the top. This is your lab score based on simulated conditions.
  5. Scroll to the "Discover what your real users are experiencing" section. This shows field data from actual visitors. If your site doesn't have enough traffic, this section may say "not enough data."
  6. Check whether your Core Web Vitals pass or fail the assessment.
  7. Scroll down to the Diagnostics section for specific recommendations like "Reduce unused JavaScript" or "Serve images in next-gen formats."

Pro tip: Always test both mobile and desktop. Toggle between them using the tabs at the top. Mobile scores are almost always lower, and that's the score Google cares about most.

2. GTmetrix (Best for Detailed Waterfall Analysis)

GTmetrix shines when you need to understand exactly which files and resources are slowing your page down. Its waterfall chart shows every single HTTP request in order, with timing bars that make bottlenecks obvious.

How to use it step by step:

  1. Go to gtmetrix.com and create a free account (required since 2023).
  2. Enter your URL and click Test your site.
  3. Wait 30-60 seconds for the test to complete.
  4. Review the GTmetrix Grade (A through F) and the Web Vitals scores at the top.
  5. Click the Waterfall tab. This is where the real value is. Look for long bars, especially on JavaScript and CSS files loaded early in the sequence.
  6. Check the Structure tab for prioritized recommendations with estimated impact ratings.
  7. Use the History feature to track your scores over time after you make changes.

Pro tip: Free accounts test from Vancouver, Canada by default. If your audience is in a different region, this affects results. Paid plans let you choose from 30+ test locations.

3. WebPageTest (Best for Advanced and Multi-Step Testing)

WebPageTest is the most powerful free speed testing tool available, though it has a steeper learning curve. It's the tool that performance engineers use for deep analysis, and it offers features the other tools don't, like testing from 40+ global locations, simulating specific connection speeds, and running multi-step tests (like testing what happens after a user logs in).

How to use it step by step:

  1. Go to webpagetest.org and enter your URL.
  2. Before running the test, click Advanced Configuration.
  3. Select a Test Location closest to where most of your visitors are located.
  4. Choose a Browser (Chrome is standard) and a Connection speed (4G is a good baseline for mobile testing).
  5. Set Number of Tests to Run to 3. This gives you a median result that's more reliable than a single test.
  6. Click Start Test and wait 1-3 minutes.
  7. Review the filmstrip view at the top, which shows screenshots of your page at each half-second interval during loading. This is incredibly useful for seeing what users actually experience.
  8. Check the Web Vitals section and the detailed waterfall below.

Pro tip: Pay attention to the "First View" vs "Repeat View" results. First View simulates a new visitor with no cached assets. Repeat View simulates a returning visitor. If there's a big gap between the two, your caching strategy needs work.

What Does Each Speed Metric Mean?

Speed testing tools throw a lot of acronyms at you. Here's what each one actually measures, in plain language. For a deeper technical dive, read our full guide on Core Web Vitals explained.

LCP (Largest Contentful Paint)

LCP measures how long it takes for the largest visible element on the page to fully render. This is usually a hero image, a large heading, or a video poster. It answers the question: "When does the main content appear?"

A good LCP is 2.5 seconds or faster. If your LCP is above 4 seconds, Google considers it poor. This is the metric most closely tied to the user perception of "this page loaded."

INP (Interaction to Next Paint)

INP replaced FID (First Input Delay) as a Core Web Vital in March 2024. While FID only measured the delay of the first interaction, INP measures responsiveness across the entire page lifecycle. It tracks every click, tap, and keyboard input, then reports the worst-case latency (with some outlier filtering).

A good INP is 200 milliseconds or less. If users click a button and nothing happens for 500ms or more, that's a poor INP. This metric catches problems that FID missed, like pages that load quickly but become sluggish as users interact with them.

CLS (Cumulative Layout Shift)

CLS measures visual stability. Have you ever tried to tap a link on your phone, only for the page to shift at the last second and you end up tapping an ad instead? That's a layout shift. CLS adds up all unexpected layout shifts that happen during the page's lifetime.

A good CLS score is 0.1 or less. Common causes include images without width/height attributes, dynamically injected ads, and web fonts that cause text to reflow when they load.

TTFB (Time to First Byte)

TTFB measures the time between the browser requesting your page and receiving the first byte of data back from the server. It reflects your server's processing speed, your hosting quality, and your DNS lookup time.

A good TTFB is 800 milliseconds or less. If your TTFB is consistently above 1 second, the problem is almost certainly server-side. No amount of frontend optimization can fix a slow server. Common fixes include upgrading hosting, enabling server-level caching, and using a CDN.

FCP (First Contentful Paint)

FCP marks the moment when the browser renders the first piece of DOM content, whether that's text, an image, or an SVG. It's the point where users see something other than a blank white screen.

A good FCP is 1.8 seconds or less. A slow FCP usually means render-blocking CSS or JavaScript is preventing the browser from painting anything until large files finish downloading.

Speed Index

Speed Index measures how quickly the visible area of the page is populated with content. Unlike LCP (which tracks a single element), Speed Index considers the entire viewport and how it fills in over time. A page where content appears gradually scores better than one that stays blank until everything loads at once.

A good Speed Index is 3.4 seconds or less. This metric is especially useful for comparing pages against each other or tracking improvements over time.

What's a Good Score? The Complete Thresholds Table

Here's a reference table with the exact thresholds that Google and testing tools use to classify your performance. Bookmark this for quick reference.

Metric Good Needs Improvement Poor
LCP ≤ 2.5s 2.5s – 4.0s > 4.0s
INP ≤ 200ms 200ms – 500ms > 500ms
CLS ≤ 0.1 0.1 – 0.25 > 0.25
TTFB ≤ 800ms 800ms – 1800ms > 1800ms
FCP ≤ 1.8s 1.8s – 3.0s > 3.0s
Speed Index ≤ 3.4s 3.4s – 5.8s > 5.8s
PageSpeed Score 90 – 100 50 – 89 0 – 49

Important note: These thresholds apply to the 75th percentile of page loads. That means 75% of your visitors need to experience "good" performance for Google to consider the metric as passing. Having fast speeds for most users but terrible speeds for the bottom 25% still counts as a fail.

The 6 Most Common Website Speed Killers

Now that you know how to measure speed and what the numbers mean, let's look at what's most likely slowing your site down. These are the issues we see over and over again in TrackSEO audit reports.

1. Unoptimized Images

This is the number one speed killer on the web. A single uncompressed hero image can be 3-5 MB, which alone can take 5+ seconds to load on a mobile connection. The fix is straightforward:

  • Convert images to WebP or AVIF format (40-60% smaller than JPEG with equal quality).
  • Resize images to the actual display size. Don't upload a 4000px wide image if it only displays at 800px.
  • Use lazy loading (add loading="lazy" to img tags) so images below the fold don't load until the user scrolls to them.
  • Use responsive images with srcset to serve different sizes to different screen widths.

2. Render-Blocking JavaScript and CSS

When the browser encounters a <script> or <link rel="stylesheet"> tag in the <head>, it stops rendering the page until that file downloads and executes. If you have 10 JavaScript files and 5 CSS files loading before any content appears, your FCP and LCP will suffer.

  • Add defer or async attributes to non-critical scripts.
  • Inline critical CSS (the styles needed for above-the-fold content) and load the rest asynchronously.
  • Audit your plugins and third-party scripts. Every chat widget, analytics tool, and social sharing button adds render-blocking resources.

3. No Browser Caching

Without proper cache headers, returning visitors have to re-download every resource on every page load. Setting appropriate Cache-Control headers tells the browser to store static assets (images, CSS, JS) locally for a specified period.

  • Set static assets to cache for at least 1 year (use versioned filenames when you update them).
  • Set HTML pages to a shorter cache duration or use no-cache with revalidation.
  • Enable gzip or Brotli compression on your server to reduce file transfer sizes by 60-80%.

4. Too Many HTTP Requests

Every file your page needs to load requires a separate HTTP request, and each request has overhead from DNS lookups, TCP connections, and TLS handshakes. A typical slow page might make 100+ requests.

  • Combine and minify CSS and JavaScript files where possible.
  • Use CSS sprites or inline SVGs instead of many small image files.
  • Remove unused plugins, fonts, and third-party scripts. Every one you remove eliminates multiple requests.

5. Too Many Redirects

Each redirect (301 or 302) adds a full round-trip to the server before the actual page loads. A chain of redirects (like http:// to https:// to www to non-www) can add 500ms to 1 second of wasted time before your page even starts loading.

  • Audit your redirect chains and collapse them into single redirects.
  • Update internal links to point directly to the final URL.
  • Make sure your canonical URL is consistent across your entire site.

6. Slow Server Response (High TTFB)

If your server takes more than a second to respond, everything downstream is delayed. Common causes include cheap shared hosting, unoptimized database queries, and lack of server-side caching.

  • Upgrade to better hosting. This is the most impactful change if your TTFB is above 800ms.
  • Use a CDN (Cloudflare, Fastly, or Amazon CloudFront) to serve cached content from servers closer to your visitors.
  • Enable server-side caching (object caching, opcode caching, full-page caching).
  • Optimize slow database queries, especially on dynamic pages.

Quick Wins to Improve Your Website Speed

If you've just tested your site and the results aren't great, here are the highest-impact changes you can make right now, ordered by effort vs. reward.

Fix Effort Impact Typical Improvement
Enable compression (gzip/Brotli) 5 min High 60-80% smaller file transfers
Convert images to WebP 15-30 min High 40-60% smaller images
Add lazy loading to images 10 min Medium-High 1-3s faster initial load
Defer non-critical JavaScript 15 min Medium-High 0.5-2s faster FCP
Set cache headers 10 min Medium 50-70% faster repeat visits
Enable a CDN 20 min Medium-High 200-500ms faster TTFB
Remove unused plugins/scripts 30 min Medium Fewer requests, smaller page size

Running WordPress? We wrote an entire step-by-step guide on this. Check out How to Improve Page Speed on WordPress for plugin recommendations, hosting comparisons, and WordPress-specific optimizations.

For a comprehensive walkthrough of everything you should be checking beyond just speed, see our complete website audit checklist.

How TrackSEO Checks Your Website Speed Automatically

The tools above are great for one-off testing. But when you need a complete picture of your site's health, testing speed in isolation isn't enough. Slow performance is often a symptom of deeper technical SEO issues, like bloated HTML, missing compression headers, excessive redirects, or unminified resources.

That's exactly what TrackSEO is built for. When you run a report, the speed analysis is just one piece of a comprehensive technical audit. Here's what the $2.99 report covers related to performance:

  • Core Web Vitals assessment: LCP, INP, and CLS scores with pass/fail status against Google's thresholds.
  • Server response time: TTFB measurement to flag hosting and server-side issues.
  • Resource analysis: Identifies render-blocking scripts, uncompressed files, and oversized assets.
  • Caching audit: Checks whether your static assets have proper cache headers configured.
  • Redirect chain detection: Finds redirect chains and loops that add unnecessary latency.
  • Image optimization check: Flags images that aren't using modern formats or are served at unnecessary resolutions.

Unlike subscription-based tools that charge $100+ per month, TrackSEO is pay-per-report. You pay $2.99 per audit with no recurring subscription and no commitment. Run a report when you need it, fix the issues, and run another one to verify. It's that simple.

Curious how TrackSEO stacks up against other options? See our SEO audit tool comparison or browse our roundup of the best SEO tools available right now.

Frequently Asked Questions

What is a good website speed score?

A Google PageSpeed Insights score of 90-100 is considered good. A score of 50-89 means there's room for improvement. Below 50 is poor and likely hurting your SEO and user experience. Focus on the individual Core Web Vitals metrics (LCP under 2.5s, INP under 200ms, CLS under 0.1) rather than just the overall score, since those are what Google actually uses for rankings.

How fast should a website load in 2026?

Your page should reach its Largest Contentful Paint (main content visible) within 2.5 seconds. The First Contentful Paint (first visual element) should happen within 1.8 seconds. Total page load time should ideally be under 3 seconds, though this varies by page complexity. Mobile load times are typically 1.5x to 2x slower than desktop, so optimizing for mobile is essential.

Does page speed directly affect Google rankings?

Yes. Google has confirmed that Core Web Vitals (LCP, INP, CLS) are ranking signals as part of the page experience system. While content relevance and backlinks still carry more weight, page speed acts as a tiebreaker between pages of similar quality. In competitive search results, even small speed advantages can move you up several positions.

Why is my mobile speed score so much lower than desktop?

PageSpeed Insights simulates mobile testing on a mid-tier device (Moto G Power) with a throttled 4G connection. This is much slower than the powerful desktop computer and fast broadband connection used for the desktop test. The gap between scores is normal. Focus on the mobile score since that's what Google uses for mobile-first indexing, and most of your traffic is likely mobile.

How often should I test my website speed?

Test after every significant change to your site: new plugins, theme updates, content additions, or server migrations. Beyond that, a monthly check is a good cadence. Speed can degrade gradually as you add content, install plugins, and accumulate third-party scripts. Running a TrackSEO report monthly gives you a performance baseline plus full SEO health monitoring.

Are free speed testing tools accurate?

Google PageSpeed Insights, GTmetrix, and WebPageTest are all accurate and widely trusted in the SEO industry. However, lab tests (simulated conditions) can vary between runs, so always run 3 or more tests and look at the median result. The field data in PageSpeed Insights is the most reliable because it reflects actual user experiences collected from millions of Chrome users. For a list of additional options, see our guide on free SEO audit tools.