What is a good website load time?

Under 2 seconds is considered fast. Under 3 seconds is acceptable. Over 3 seconds on mobile will cause significant abandonment. Under 1 second is excellent and achievable for well-optimised sites.

What causes slow load times?

The most common causes are: large uncompressed images, no CDN, slow hosting/TTFB, render-blocking JavaScript, too many HTTP requests, no browser caching, and unminified CSS/JS files.

Does load time affect bounce rate?

Yes, significantly. Google research shows a page that loads in 1 second has a 3x lower bounce rate than a page that takes 5 seconds. Every second of load time directly impacts how many visitors stay.

Browse tools

Free · Fast · Privacy-first

Check Website Load Time

Understanding exactly how long your website takes to load — and at which stages it stalls — is the first step to improving it. FixTools measures total load time and breaks it down into key stages: DNS lookup, server response, and page rendering.

⚡ Use Tool Now How it works

Cost: Free forever
Sign-up: Not required
Processing: In your browser
Privacy: Files stay local

⚡

Total load time measurement

🔒

Stage-by-stage timing (DNS, TTFB, FCP, LCP)

✨

Waterfall-style breakdown

Web Tool

Website Speed Test

All processing happens in your browser — your files are never uploaded to any server.

🚀Open Website Speed Test

100% Free · No account · Works on any device

How to use this tool

💡

Enter your URL to get a detailed breakdown of every stage of your page load time.

How It Works

Step-by-step guide to check website load time:

1
Enter the page URL
Paste the full URL including https:// of the specific page you want to time.
2
Run the test
Click Test and wait for the tool to fully load your page and record all timing events.
3
Review the timing breakdown
Check DNS time, TTFB, FCP, and total load time. Identify which stage takes the most time.
4
Prioritise the bottleneck
High TTFB: investigate hosting, server config, or database queries. Long render time: investigate large images, render-blocking JavaScript, or CSS.

Real-world examples

Common situations where this approach makes a real difference:

Hosting provider comparison

A site owner compares load times on their current shared hosting versus a new VPS by testing the same page on both and observing a TTFB reduction from 1.2 seconds to 180ms — confirming the upgrade is worthwhile.

CDN effectiveness check

A developer enables a CDN for the first time and re-tests load time from multiple geographic locations. The timing breakdown confirms CDN is serving assets and reducing download time by 60%.

Slow page investigation

A site owner receives complaints about one page being "really slow". The load time checker reveals a 4.2-second total load time driven by a 2.8MB unoptimised hero image, giving a clear fix to implement.

When to use this guide

Use this when investigating why a page feels slow to users — the stage-by-stage breakdown reveals whether the bottleneck is at the server, network, or browser rendering stage.

Pro tips

Get better results with these expert suggestions:

Identify which stage is the bottleneck

High TTFB (>600ms) points to slow server or hosting. Long render time after TTFB points to large or render-blocking resources. The timing breakdown helps you focus fixes on the right layer.

Under 3 seconds total load time is the target

Google research shows 53% of mobile visitors abandon a page that takes more than 3 seconds to load. A sub-2-second load time is excellent. Sub-1-second is exceptional and achievable with aggressive optimisation.

Compare before and after optimisation

Benchmark load time before making any changes. After each optimisation (compressing images, adding caching, enabling CDN), re-test to measure the exact improvement.