Speed test · mit.edu

How fast is mit.edu?

1 GET to https://web.mit.edu/ from our edge · Mon, 27 Jul 2026 20:09:16 GMT · not your device
B
Good. Nothing here is hurting users.
HTTP 200 over HTTP/1.1 · 11 KB transferred · 1 redirect · no HTTP/2

Where the time went

dns 2msconnect 7mstls 16msttfb 23msdownload 1ms
DNS
2 ms
Connect
7 ms
TLS
16 ms
First byte
48 ms
Download
1 ms
Doc rate
92.5 Mbps

"Doc rate" is the transfer rate of this one document from our vantage, it reflects the server and path, not your bandwidth.

Report card

CheckMeasuredGrade
Time to first byte48 msA
Document transfer size11 KB (gzip)A
Compressiongzip · text/htmlB
Redirects302 → 200B
HTTP/2not supported
Cache-Controlpublic, max-age=2201, s-maxage=3600

Your connection to us

This panel runs in your browser and measures the path between your device and our edge, latency, jitter, and a rough download estimate. It cannot measure your path to any other site, browsers don't allow that, so use it as the "is it me" half of the diagnosis: if the site's server tests fast here but everything feels slow, your connection is the suspect.

Latency (median)
-
Jitter
-
Download
-

The download number is an estimate from a single 4 MB burst, enough to tell "broadband fine" from "something is wrong", not a substitute for a full bandwidth test. Nothing about your connection is stored.

How we grade

GradeTime to first byteDocument transfer sizeRedirect hopsCompression
A≤ 200 ms≤ 100 KB0brotli (or non-text)
B≤ 400 ms≤ 300 KB1gzip / deflate
C≤ 800 ms≤ 1 MB2-
D≤ 1500 ms≤ 3 MB3+-
Fworseworse-uncompressed text

Overall letter = weighted average (first byte counts double), nudged up a third of a grade when the host speaks HTTP/2 and down when it doesn't.

Slow today can be down tomorrow. A free monitor probes mit.edu every 5 minutes with 4 probe methods and emails you when it stops answering, and the live check page has current status and history.