Website speed test: how fast is your site, really?
Enter your address for a free check. No signup, no jargon — just what's slowing you down and what it's costing you.
Performance score
What your visitors experience
What is worth to you?
Rough numbers are fine — this is an order-of-magnitude estimate, not a forecast.
Widely cited industry studies — Walmart reported roughly 2% more conversions per second saved, Amazon about 1% per 100ms. The relationship is not linear and varies a lot by sector, so treat this as a range rather than a number.
Get the full list, with what to fix first and how much time each change saves.
Why is my website slow?
Almost every slow site is slow for one of four reasons, and they are not equally likely. In rough order of how often they turn out to be the culprit:
- Images that are too big. A photo exported straight from a camera or design tool can be several megabytes. Resized and compressed properly, the same image is often 95% smaller and looks identical.
- Third-party scripts. Chat widgets, analytics, ad tags, A/B testing tools. Each one is a request to someone else's server, and your page waits on it.
- A slow server. If the first byte takes a second to arrive, everything after it is late no matter how well built the page is.
- Render-blocking CSS and fonts. The browser has the content but refuses to paint it until the stylesheet and font have downloaded.
The point of testing is to find out which of these is costing you the most, because fixing the wrong one is a lot of work for nothing.
How to test your website speed
- 1. Test the page that matters. Not just your homepage — test the page people actually land on and the one where they buy or sign up.
- 2. Test on mobile. Most visitors are on a phone, on a worse connection than yours. A page that feels instant on your laptop can take eight seconds on a mid-range Android.
- 3. Test more than once. A single run can be thrown off by a slow moment on a network. Two or three runs tell you what is normal.
- 4. Write the number down. Today's score is only useful compared to last month's. Without a baseline you cannot tell whether a change helped.
Speed testing vs website speed monitoring
Sites rarely get slow all at once. They get slow the way a room gets untidy — one plugin, one tracking script, one uncompressed image at a time. By the time it is obvious, you have lost months of visitors and you have no idea which change caused it.
That is the difference between a test and website speed monitoring. A test is a photograph of one moment. Ongoing website performance monitoring tells you when something regressed and what changed that day — which is usually the more useful thing to know.
Common questions
Why is my website moving slowly?
Usually one of four things: oversized images, too many third-party scripts (chat widgets, analytics, ad tags), a slow server response, or fonts and CSS that block the page from rendering. The test above tells you which one is costing you the most time, so you fix the expensive thing first instead of guessing.
What is a common cause of slow website loading speed?
Images, more often than anything else. A single uncompressed hero image can weigh more than the rest of the page combined. Third-party scripts are the usual runner-up — each one is a request to someone else's server, and you inherit their bad day.
What is a reasonable page load time?
Aim for your main content to appear within 2.5 seconds on a normal mobile connection. That is the threshold Google treats as good. Past 4 seconds, people start leaving before they have seen anything.
How do I make my website run faster?
In the order that usually pays off: compress and correctly size your images, remove third-party scripts you no longer use, load the rest of them after the page renders, and make sure your host responds quickly. The first two are often enough to move a site from red to green.
How to monitor website performance?
Test the pages that matter — not just the homepage — on a schedule, and record the numbers each time so you can see the trend. A one-off test tells you where you are today; monitoring tells you when something has broken, which is usually the more useful thing to know.
What are the top 3 website performance metrics to monitor?
Largest Contentful Paint (how long until the main thing appears), Interaction to Next Paint (how quickly the page responds when someone taps or clicks) and Cumulative Layout Shift (how much the page jumps around while loading). Together they cover: did it show up, does it respond, does it stay still.
How to pass Core Web Vitals assessment?
You pass when 75% of real visits meet the threshold on all three metrics. That last part catches people out — it is measured on your actual visitors, not on a lab test, so a page that scores well on a fast laptop can still fail on real phones.
Which tool is commonly used to track website performance?
Google's PageSpeed Insights and Lighthouse are the usual starting points, and both are free. They are built for developers, though, which is why the report above is written in plain language instead.