engage.cloud.microsoft/main/feed speed test — 20 Oct 2026
Measured from the wfix.shop server on 20 October 2026 at 13:15 UTC. Grade A (93/100), with the screenshots, the timings and the fixes that matter.
Where the first byte went
- DNS lookup 88 ms 22%
- TCP connect 48 ms 12%
- Server wait 256 ms 65%
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 392 ms. That is workable, and the cheapest win left is caching or a warmer connection.
- The page transfers 279.1 KB over 6 request(s), which is lean. Javascript files are 89% 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 2.06 s, inside the 2.5 s Google calls good.
- Layout stayed still (CLS 0.026), so nothing jumps under the reader's cursor.
- The main thread was blocked for 40 ms in total, which is not enough to feel.
Fix first: Third-party weight - Self-host the libraries you can, drop the tags you cannot justify, and preconnect the ones you keep.
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. 6 request(s) in total, 279.1 KB across all of them.
Top issues
Third-party weight
medium impact1 third-party host(s) serve 278.5 KB 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 impact1 JavaScript file(s) over 200 KB: 3-render-renderer.js (204.6 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-1.cdn.office.net/yammer/20261016001.9840470/1-auth.js 3rd party | javascript | 200 | 396 ms | 38.8 KB |
| https://outlook-1.cdn.office.net/yammer/20261016001.9840470/manifest.webmanifest 3rd party | other | 200 | 395 ms | 474 B |
| https://outlook-1.cdn.office.net/yammer/20261016001.9840470/0-config.js 3rd party | javascript | 200 | 356 ms | 5.0 KB |
| https://outlook-1.cdn.office.net/yammer/20261016001.9840470/favicon.ico 3rd party | images | 200 | 323 ms | 29.7 KB |
| https://outlook-1.cdn.office.net/yammer/20261016001.9840470/3-render-renderer.js 3rd party | javascript | 200 | 319 ms | 204.6 KB |
Report this page
Run this test on your own site
The same engine, free, with the screenshots and the fixes. No account needed.