outlook.live.com/mail speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 12:34 UTC. Grade C (78/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 65 ms 14%
- TCP connect 67 ms 14%
- Server wait 336 ms 72%
Measured on the connection that fetched the HTML. Every other request on the page waits for the end of this bar before it can start.
How this page compares
Every report published here is in this comparison, so it is a reference population of pages tested from one server - not a benchmark of the whole web.
What these numbers mean
- The first byte arrived in 468 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 2.06 MB over 17 request(s). Javascript files are 81% of it, so defer what is not needed for the first screen, and drop tags nobody uses.
- The HTML itself arrives gzip-compressed.
- It runs over HTTP/3, so the assets share a connection instead of opening one each.
- 100% of the weight comes from other hosts (analytics, fonts, embeds), which also means their slow day becomes your slow day.
- The largest element painted at 476 ms, inside the 2.5 s Google calls good.
Fix first: Server response time (TTFB) - Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.
Read on one shared server, not a visitor's phone: use it to compare pages against each other, not as a promise about every connection. We fix what these tests find.
Screenshot
What the page looks like
Loaded in headless Chromium on this server. Click an image to open it full size.
Browser render
The same URL loaded in a real browser, so these are the readings curl cannot produce. The grade above is still built from the server measurements.
Page weight by type
What the page is made of
Transfer size, compressed as sent. 17 request(s) in total, 2.06 MB across all of them.
Top issues
Server response time (TTFB)
high impactThe first byte arrived after 468 ms. Of that, 336 ms was the server thinking and 132 ms was connection setup. A first byte under 400 ms is what a visitor feels as instant.
Fix: Cut server think time: page cache, query indexes, fewer synchronous calls to third parties inside the request. Connection setup is distance, so a nearer region or a CDN edge helps instead.
Total page weight
high impactThe page transfers 2.06 MB across 17 request(s), with the document itself at 5.9 KB.
Fix: Work through the heaviest assets first: images, then fonts, then third-party scripts.
Third-party weight
medium impact1 third-party host(s) serve 2.05 MB of this page. Each one is another DNS lookup, TLS handshake and point of failure you do not control.
Fix: Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.
JavaScript weight
medium impact2 JavaScript file(s) over 200 KB: owa.23217.m.4b07d7bf.js (702.9 KB), owa.AppBoot.m.c6fa89a2.js (662.5 KB)
Fix: Split routes, remove unused dependencies, and prefer a two-file build (one pinned library, one application bundle) over many small ones.
Avoid extra redirects
medium impact2 redirect hop(s) before the page load started, each one a full round trip before the first byte.
Fix: Link to the canonical URL (and make sure http, the apex domain and www all point at it) so no visitor pays a redirect first.
Waterfall
Slowest requests
Each bar is one request's own response time, scaled to the slowest. Assets were fetched in parallel, so the bars overlap in real time rather than stacking. first party third party
| Request | Type | Status | Time | Size |
|---|---|---|---|---|
| https://outlook.live.com/mail/mail/favicon.ico | images | 405 | 860 ms | 0 B |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.71719.m.df8464ca.js 3rd party | javascript | 200 | 685 ms | 2.2 KB |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.23217.m.4b07d7bf.js 3rd party | javascript | 200 | 677 ms | 702.9 KB |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.AppBoot.m.c6fa89a2.js 3rd party | javascript | 200 | 664 ms | 662.5 KB |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mail.m.7fec7e25.css 3rd party | css | 200 | 663 ms | 41.3 KB |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.46744.m.24b2dac1.js 3rd party | javascript | 200 | 660 ms | 16.2 KB |
| https://res.public.onecdn.static.microsoft/assets/mail/pwa/v4/pngs/apple-touch-icon.png 3rd party | images | 200 | 659 ms | 15.1 KB |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.styles.m.70df255b.css 3rd party | css | 200 | 654 ms | 21.2 KB |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mailindex.f5cd8347.js 3rd party | javascript | 200 | 646 ms | 133.7 KB |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.mail.runtime.c5aacd1a.js 3rd party | javascript | 200 | 646 ms | 123.2 KB |
| https://res.public.onecdn.static.microsoft/assets/framework/microsoft.svg 3rd party | images | 200 | 646 ms | 1.4 KB |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.shared.m.7033c40f.css 3rd party | css | 200 | 645 ms | 191.5 KB |
| https://res.public.onecdn.static.microsoft/owamail/20261008079.11/resources/fonts/o365icons-mdl2.woff 3rd party | fonts | 200 | 645 ms | 108.8 KB |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.98434.m.220db147.js 3rd party | javascript | 200 | 645 ms | 58.7 KB |
| https://res.public.onecdn.static.microsoft/owamail/20261008079.11/resources/fonts/office365icons.woff 3rd party | fonts | 200 | 645 ms | 11.4 KB |
| https://res.public.onecdn.static.microsoft/owamail/hashed-v1/scripts/owa.MsalAuth.m.027ef2c0.js 3rd party | javascript | 200 | 645 ms | 9.9 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.