- Free, no sign-up
- Score out of 100
- Clear fix list
Free Website Speed Test
Get a 0–100 speed score from your server response time, page weight and request count, plus checks for compression, caching and render-blocking files.
0.0 0 ratings
Measures server response time, page weight and request count, plus compression, caching and render-blocking checks. One URL at a time.
How useful was this tool?
Be the first to rate it.
Why speed matters
Slow sites lose people
This tool is also called a page speed test, site speed checker or website performance test. Enter any URL and get a 0 to 100 score in seconds, with the things slowing your page down.
It does not matter how well written your blog is or how good your product looks. If the page takes too long to load, people leave before they see it.
Most site owners only take speed seriously when a competitor with weaker content starts to outrank them. That is usually the moment page speed stops being an afterthought and becomes a checklist item before every launch.
This test exists so you do not have to guess. Paste a URL, run it, and see what a browser gets from your server, before your visitors do.
How to use it
Test your page speed in three steps
Enter a URL
Any public page, yours or a competitor's: your homepage, a blog post, a product page. Test the pages that matter most.
Click Check Speed
We request the page live, time the server's answer, then size the CSS, JavaScript and images it links to.
Get your score and work through the checks
You get a score out of 100, three headline numbers and a list of checks showing what helps and what hurts. Fix the amber and red ones first.
Built forSite ownersWordPress usersAgencies and freelancersSEO specialistsDevelopers
What it checks
What the speed test measures
Every number comes from a real, live request to your page, not an estimate.
Time to first byte
How long your server takes to start answering, the base everything else builds on. Under 200 ms is good; over 600 ms visitors notice.
Page weight
The HTML plus the CSS, JavaScript and images it links to. Under 1.5 MB is good; over 3 MB is heavy.
Requests
How many files the page needs, split into CSS, JS and images. Under 40 is good; over 90 is a lot.
Compression and caching
Whether the HTML is sent with gzip or Brotli (and how much it saves), and whether it carries Cache-Control or Expires headers.
Render-blocking files
Scripts and stylesheets in the <head> that stop the browser from drawing the page until they load.
Redirect chain
Every hop your URL takes before the final page, with its status code. Each extra hop adds a round trip.
Image dimensions
Images without width and height, which make the page jump as they load.
Third-party domains
How many outside domains your page depends on, and which ones, plus your preconnect, preload and dns-prefetch hints.
Largest file
The single heaviest file we found, often the first thing worth shrinking.
The score
How the score is weighted
Not one number pulled from thin air. Eight factors, each scored 0 to 100, then weighted like this.
| Factor | Weight | Full marks when |
|---|---|---|
| Server response time | 25% | Under 200 ms (zero at 1.5 s) |
| Page weight | 20% | Under 1.5 MB (zero at 5 MB) |
| Request count | 15% | 40 files or fewer (zero at 120) |
| Compression | 10% | HTML sent with gzip or Brotli |
| Caching | 10% | Cache-Control or Expires header present |
| Render-blocking files | 10% | None in the head (each one costs 10 points) |
| Image dimensions | 5% | Every image has width and height |
| Third-party domains | 5% | 5 or fewer outside domains (zero at 20) |
Reading the results
What your score means
90 to 100: excellent
Fast server, light page, good habits. Keep an eye on it after adding plugins, fonts or tracking scripts.
75 to 89: good
Solid, with a few easy wins left. Look at the amber checks below the score.
60 to 74: needs improvement
Visitors on slower connections feel this. Start with page weight and the server response time.
Below 60: poor
Real delays for real people. Usually a slow host or uncached pages, heavy images, or too many scripts.
Honest limits
What this test does not do
Being upfront, because plenty of free speed tests are not.
What it is good for
- Real server-side numbers: response time, page weight, requests and headers.
- Spotting missing compression, missing caching or render-blocking scripts fast.
- Comparing your site with a competitor's in seconds.
- Checking again after every deploy, redesign or plugin update.
What it cannot do
- Measure Core Web Vitals. LCP, INP and CLS need a real browser rendering the page, which a server-side test cannot copy.
- Show a waterfall chart of how files load over time.
- Simulate a phone or a throttled 4G connection. It makes one request from our server with one user-agent, so there is no mobile vs desktop comparison.
- Show the HTTP protocol (HTTP/1.1, 2 or 3), the DNS, connect and SSL handshake times, or timings for each redirect hop. Those fields show "N/A".
- Size every file. It sizes the first 20 CSS, JavaScript and image files and stops after a few seconds. Fonts and files loaded later by scripts are not counted.
For the full picture, run this test first to catch server-level problems quickly, then check Google PageSpeed Insights for Core Web Vitals data from real Chrome users.
Core Web Vitals
What Google actually watches
This tool does not measure these directly, but they are the reason speed matters for SEO, whichever tool you use to check them.
LCP: Largest Contentful Paint
How long until the main content appears. In other words: is your page useful yet? Google's "good" mark is 2.5 seconds or less.
INP: Interaction to Next Paint
How fast the page responds when someone clicks or taps. Good is 200 ms or less.
CLS: Cumulative Layout Shift
Ever tried to tap a button and it jumped away just before you hit it? That is bad CLS. Good is 0.1 or less.
A fast server response and a light page help LCP. Fewer heavy scripts help INP. Width and height on images help CLS. So the checks in this test feed straight into the vitals.
Tips
Fixes that actually move the needle
The common causes of a low score, and what to do about each. Each fix maps to a check in your report.
Compress and resize images
Oversized, uncompressed images are the most common cause of a heavy page. Resize to the size you display, export as WebP or AVIF, and lazy-load images below the fold.
Cache your pages
A slow first byte usually means the page is built from scratch on every visit. A page cache or a CDN can turn seconds into milliseconds.
Add async or defer to scripts
Render-blocking JavaScript in your <head> delays everything below it. Defer scripts the first screen does not need.
Turn on gzip or Brotli
Usually one setting on your host, CDN or caching plugin, and it cuts text files by more than half. Often the fastest win on this list.
Set browser caching headers
So repeat visitors do not download your whole site again on every visit.
Cut third-party scripts you do not need
Every ad network, widget or tracking pixel adds its own DNS lookup and connection. Remove the ones nobody uses any more.
Set width and height on images
The browser can reserve the space, so the page stops jumping as images load. Visitors feel the difference.
FAQ
Frequently asked questions
Is this website speed test really free?
Yes, with no sign-up. You test one URL per check, and a fair-use limit of 10 checks a minute and 100 an hour keeps it fast for everyone.
Can I test any website, not just my own?
Yes. It only reads publicly available server responses, so you can test a competitor's site or any public URL the same way.
Does it measure Core Web Vitals like LCP or CLS?
No. Those need a real browser rendering the page. This test measures the server side: response time, weight, requests and the checks. Use it to catch server-level problems fast, then use Google PageSpeed Insights for Core Web Vitals.
Does it test mobile page speed?
No. It runs one request from our server, not from a phone or a throttled connection, and it does not compare mobile and desktop user-agents. A light page with a fast server is the base for good mobile speed, though, and PageSpeed Insights shows a mobile score.
Why is my page weight lower than in other tools?
We size the HTML and the first 20 CSS, JavaScript and image files it links to. Fonts and files loaded later by scripts are not counted, and we stop sizing after a few seconds to keep results fast.
Why did my score change between two tests?
Server response time varies a little from request to request, especially on shared hosting or behind a CDN. A few points either way is normal. Repeat tests within a few minutes show the same cached result; a big change after that usually means something changed, such as caching kicking in or a plugin update.
What is a good website speed score?
90 or more is excellent, 75 to 89 is good, 60 to 74 needs improvement, and below 60 means visitors are likely feeling real delay.
Do you store the URLs I test?
No. A result is kept for a few minutes so repeat checks are fast, then it is gone.
Keep going
More free SEO tools
- SSL Checker: confirm your certificate is valid and not about to expire.
- Robots.txt Tester: make sure search engines may crawl your pages.
- HTTP Status Checker: see status codes and every redirect hop.
- Meta Tag Analyzer: review titles, descriptions and social tags.
- Schema Markup Validator: check your structured data for errors.
- Canonical Tag Checker: make sure the right URL gets the credit.
Did this tool help you?
Tap a star. It takes a second, no sign-up.
–
0.0 0 ratingsNo ratings yet.
Test your page speed now
A faster site is not about bragging rights; it gets your content seen. Free, no sign-up, and it takes seconds.