Free tools

Website speed test

We load the page in a real browser with Google Lighthouse to score it, show how it renders and list what slows it down, and time the server's response step by step.

  • Free
  • No sign-up
  • Results in seconds

How the website speed test works

  1. 1Enter a page address
  2. 2We load it in a real browser with Google Lighthouse
  3. 3Get a score, the slow parts and what to fix first

What it checks

  • Performance score
  • Core Web Vitals
  • Filmstrip
  • Request waterfall
  • DNS, TLS and TTFB timings
  • Mobile and desktop
Example result, with sample data.

Frequently asked questions

What does the performance score mean?
It's Lighthouse's score out of 100, built from five lab measurements: First Contentful Paint, Largest Contentful Paint, Total Blocking Time, Cumulative Layout Shift and Speed Index. 90 and above is good, 50 to 89 needs improvement, below 50 is poor. Mobile scores are usually lower: the test simulates a mid-range phone on a slow 4G connection.
What are Core Web Vitals?
Google's three measures of real user experience: Largest Contentful Paint (loading, good under 2.5 s), Interaction to Next Paint (responsiveness, good under 200 ms) and Cumulative Layout Shift (visual stability, good under 0.1). The Real visitors section shows them from Chrome users over the last 28 days, when the site has enough traffic. Google uses these in search ranking.
Why does my score change between runs?
Network conditions, server load, ads and third-party scripts differ from one load to the next, so scores move by a few points. Results are kept for 10 minutes; test again later to compare, and look at the trend rather than one number.
Can I share the results or save them as a PDF?
Yes. Once both tests finish, Share link saves the mobile and desktop results and gives you a link anyone can open for a year, and Download PDF saves the same report as a file to send to a client or your developer.
What's a good time to first byte (TTFB)?
Under 200 ms is excellent and under 600 ms is fine. Above that, the server is slow to build the page: add caching, speed up database queries, or use a faster host or a CDN.
Why is DNS or TLS slow?
Slow DNS usually means a slow DNS provider or a long CNAME chain. TLS takes longer over long distances; a CDN close to your visitors cuts it down.
How do I keep an eye on speed over time?
Spot Downtime monitors record the response time of every check, chart it, and alert you when the site goes down. Start with the free plan.

Get told the moment it breaks

Checking by hand only tells you about right now. Spot Downtime checks your sites around the clock and alerts you by email, Slack, SMS or a phone call.

Start monitoring free