Website Speed Test

Find out how fast a website responds and what slows it down: DNS, connection, TLS and server time, page weight, compression, HTTP/2 and render-blocking resources, with prioritised recommendations.

Try: wikipedia.org, github.com, example.com
A
Website speed report

https://www.wikipedia.org/

Score 94/100 · Scanned 13 Oct 2026, 21:05 UTC · by ToolsForAnyone
Server response110 ms
Total load (HTML)377 ms
HTML size119.3 KB
Compressiongzip

Timing breakdown

Measured from our server (eastern US)
Redirects
244 ms
DNS lookup
1 ms
TCP connect
2 ms
TLS handshake
20 ms
Server (TTFB)
110 ms
Download HTML
0 ms

Opportunities

2 found
Redirects cost 244 msLOW IMPACT
1 redirect(s) before the page loaded.
Link to the final URL directly.
No modern image formats detectedLOW IMPACT
WebP and AVIF are typically 25–50% smaller than JPEG/PNG.
Serve WebP or AVIF images.

Page resources

External scripts
2 (+2 inline)
Stylesheets
0
Images
7
Iframes
0
Preload / preconnect hints
1
Third-party domains
0

Server

IP address
208.80.154.224
Server software
ATS/9.2.15
HTTP/2
Yes
HTTP/3
No
Cache-Control (HTML)
s-maxage=86400, must-revalidate, max-age=3600

Want Core Web Vitals from real Chrome users? Run Google PageSpeed Insights for this URL.

What this website speed test measures

We load the page from our server and break the time down into each step a browser goes through before it can start rendering: resolving the domain name (DNS), opening a TCP connection, negotiating TLS encryption, waiting for the server to generate the page (time to first byte) and downloading the HTML. Then we analyse the HTML for the things that most often slow pages down in the browser.

Core Web Vitals in brief

MetricMeasuresGood
LCP (Largest Contentful Paint)When the main content appears≤ 2.5 s
INP (Interaction to Next Paint)How quickly the page reacts to clicks and taps≤ 200 ms
CLS (Cumulative Layout Shift)How much the layout jumps while loading≤ 0.1
TTFB (Time to First Byte)Server and network responsiveness≤ 0.8 s

A slow server response delays everything else, which is why TTFB is the first number to optimise. Render-blocking scripts and stylesheets delay LCP, images without dimensions cause CLS, and heavy JavaScript hurts INP.

The most effective speed fixes

  1. Cache pages and use a CDN so most visitors get a ready-made page from a nearby server.
  2. Enable brotli or gzip compression for HTML, CSS and JavaScript.
  3. Defer non-critical JavaScript with defer or async, and remove unused tags and plugins.
  4. Optimise images: serve WebP/AVIF at the displayed size, set width and height, and lazy-load below-the-fold images.
  5. Enable HTTP/2 and HTTP/3 and preconnect to essential third-party origins.
  6. Avoid redirect chains; check them with the redirect checker.

Looking for your own connection speed instead? Use our internet speed test. For search visibility, run the SEO checker.

Frequently asked questions

Why are my results different from PageSpeed Insights or GTmetrix?

Each tool tests from different locations, devices and network speeds. Lab tools simulate a mid-range phone on a slow network; this test measures server-side timings from our data centre. Track changes over time with the same tool.

Does this test load images and scripts?

No. It downloads and analyses the HTML document. Resource counts and recommendations come from the HTML, which keeps the test fast and gentle on the site.

Copied to clipboard