Free website speed test and health check: numbers, not guesses
Run a free website speed test on any address. In under a minute you’ll see how long your server takes to respond, how heavy the page is, which CDN you’re behind and which hosting company’s IP address you sit on, what state your SSL certificate is in and, most importantly, exactly what will make your site faster.
What we measure
One test, forty checks
This tool really loads your site over the network from our server and measures the actual responses it sends back. No simulation, and no estimates read from your code.
Server response time (TTFB)
Every stage from the DNS lookup to the first byte is timed separately: DNS, TCP connect, TLS handshake, server processing and document download. Each stage gets its own number, so you can see exactly where the slowdown is. The measurement is repeated several times and the median reported, so a single cold connection can’t skew the result.
CDN and origin IP detection
By combining four independent signals (response headers, the IP owner’s name, nameservers and the CNAME record), we work out which CDN you’re behind, from Cloudflare and Akamai to ArvanCloud and Derak Cloud. If a CDN is active, we also check whether your origin server’s IP can be discovered from your own domain’s public records.
IP address and hosting provider lookup
The site’s IP address, its network number (ASN), the company that holds that address range, the server’s country and its reverse DNS name (PTR). The data comes from Team Cymru’s public service and the official RDAP registries, not from free databases that guess.
Page weight and structure
The page’s CSS, JavaScript, image and font files are actually downloaded and measured: how many there are, how big they are, which ones aren’t compressed, which images are needlessly heavy and which files block the page from rendering.
Security and SSL certificate
The certificate’s issuer and days remaining, the automatic http-to-https redirect, the HSTS header, insecure content on a secure page and the browser security headers. Anything missing comes with exact instructions for adding it.
Technical SEO checks
Title, meta description, main heading, mobile viewport, document language, canonical, robots.txt and sitemap, image alt text, and whether the site answers on one address with or without www: the things that quietly cost you rankings when they’re missing.
Scoring
How the score is calculated
No number in this report is a matter of taste. Every check has a fixed weight, each category’s score is the weighted average of its checks, and the overall score combines the four categories in the proportions below.
Speed — 40%
Server response time, document download time, connection handshake, DNS response, total page weight and number of files.
Optimization — 25%
Compression, browser caching, HTTP version, image format and size, render-blocking files and whether a CDN is in place.
Security — 20%
HTTPS and its automatic redirect, certificate validity, HSTS, insecure content, security headers and whether the origin IP stays hidden.
Quality & SEO — 15%
Title and description, main heading, mobile viewport, language, canonical, robots and sitemap, image alt text and a single address for the site.
Anything that can’t be measured (for example, when a site doesn’t send our server a full response) is marked “Not measured” and left out of the score entirely. Penalizing a site for something we never saw would make the report worthless.
FAQ
Free website speed test FAQ
Is this tool free? How many times can I use it?
It’s completely free, and no sign-up is needed. To keep the tool usable for everyone, each domain can be tested 3 times a day as a guest. Sign in to a Mehran Host account and the per-domain limit is lifted; only an overall daily cap for your account remains. Creating an account is free and doesn’t commit you to buying anything.
Where is the test run from?
From our server in Europe, over the public internet. Keep that in mind if your audience is in Iran: a site that opens quickly from Europe can still be slow for a visitor inside Iran, and the other way round. Numbers measured from another network can differ, and if your server rate-limits datacenter traffic, the response we get may not match what a browser gets. When that happens, the report says so plainly.
What does “Origin IP is exposed” mean, and how do I fix it?
With a CDN in front of your site, your DNS record points at the CDN’s nodes and your real server’s IP stays hidden. But the same domain usually publishes other things too: an MX record for email, an SPF record, and subdomains like cpanel or webmail that control panels create automatically. If any of them points at your origin server, its IP has leaked. We only read your own domain’s public records (anyone can do the same with a single dig command) and then check whether that address really serves your site. The fix: on your firewall, allow direct access to the server only from the CDN’s nodes, and send outgoing email from a different IP.
I got a low score. Where do I start?
At the top of the “What to fix” list. It’s ordered by real impact on the score, not by topic. The first two or three items usually make more difference than all the rest combined, and on most sites they are compression, image formats and browser caching, none of which require touching your site’s code.
Why are my results different from Google PageSpeed?
Because they measure different things. PageSpeed runs a real browser and reports user-experience metrics (LCP, CLS and so on); this tool measures the infrastructure: server, network, protocol, compression, caching, certificate and CDN. The two complement each other. Much of a poor PageSpeed score is rooted in exactly what we measure here, while browser-side rendering problems don’t show up here at all.
Is my site’s data stored?
The result is stored so the report link can be shared, and that link is the only way to reach it: reports aren’t listed anywhere public and aren’t indexed by search engines. What’s stored is exactly what you see in the report. Cookies and Set-Cookie headers received during the test are deliberately stripped and never kept in the saved report.
Can I test other people’s websites?
Yes. Everything this tool reads is public: the same page any browser gets and the same records any resolver sees. There’s no port scanning, no mass subdomain guessing and no attempt at unauthorized access. It’s well suited to benchmarking competitors or checking a client’s site.
🤖
MehranHost.cloud AI assistant
Instant answers to your questions
Answers are automated and may be incomplete. For anything about your account, please open a ticket.