Free · live registry data · no login

Website Speed Test

Load time and Core Web Vitals snapshot.

How it works

Website speed test: server response time and page weight

Enter a domain and our server fetches the homepage, timing the redirect chain and the final response separately so you can see time-to-first-byte, total download time and HTML size. We then read the HTML and headers for the things that most often make a page slow: missing compression, redirect hops, render-blocking scripts and stylesheets, no caching, too many third-party hosts. This is one server-side request, not a full browser render, so treat it as a fast diagnostic rather than a Lighthouse replacement.

Results appear here after you click Test speed.

How this works

1
Time the request
Our server requests the homepage, timing each redirect hop and the final response to separate TTFB from redirect waste.
2
Inspect the response
Headers reveal compression, caching and protocol; the HTML head reveals render-blocking scripts, stylesheets, fonts and third-party hosts.
3
Score the basics
Points are deducted for slow TTFB, redirect chains, missing compression, blocking scripts and missing hints, with a fix for each.

Frequently asked questions

What is a good server response time (TTFB)?: Google treats under 800 ms as good and over 1,800 ms as poor. Well-cached static sites and CDN-fronted pages typically answer in 100–300 ms. Uncached WordPress on shared hosting often lands at 1–3 seconds, and page caching alone usually fixes it.
Is this the same as Google PageSpeed Insights?: No. PageSpeed renders the page in a real browser and reports Core Web Vitals from Chrome users. This tool makes one server-side request and inspects the HTML and headers, so it is faster and good at spotting server and delivery problems, but it cannot measure layout shift or interaction delay.
How do I make my website load faster?: In order of impact for most sites: enable page caching or a CDN to cut TTFB, turn on brotli or gzip compression, add defer to scripts, lazy-load below-the-fold images and compress them to WebP or AVIF, remove unused plugins and third-party scripts, and collapse redirect chains.
Why is my site slow even though the host says the server is fast?: Server speed is only TTFB. Most load time is spent in the browser downloading and running JavaScript, fonts and images. A fast server with 3 MB of scripts still feels slow. Check the composition table for blocking scripts and third-party hosts.
Does a CDN really help a small site?: Yes if your visitors are not near your server. A CDN caches your pages and assets in dozens of cities so the first byte arrives from a nearby node, and most CDNs add brotli compression and HTTP/3 automatically. Cloudflare's free plan is enough for most small sites.

Every MailShrine domain includes WHOIS privacy, transfer lock, Anycast DNS with DNSSEC and two business mailboxes.