Boy was I wrong!!!
- 500/565 requests
- 7.0 MB transferred
- 9.86 second to load
Holy crap!!! - 400 requests (adds about 1 per second after that)
- 6.8 MB transferred
- 6.1 seconds
Then I ran it AGAIN, and got this: - 307 requests
- 4.6 MB
- 9.03 seconds
You're right - it is WEIRD!On mobile, but last I checked was around 700 HTTP requests on a desktop without adblock.
I always find it difficult to imagine what kind of process leads to that result. The developers can't be happy about it, surely. It has to be a case where management and everyone else throws things they want into the project, a big concensus party, and you end up with a bloated monster at the end.
As helpful as decreasing image size was, switching to HTTP/2 was even better. Highly recommend giving HTTP/2 a try if your dealing with a lot of file requests & latency. A small test of 150 images went from 6 seconds down to 1 second in our tests.
Turns out the intranet team had decided to add a panel for Yammer updates. It doesn't help that the Yammer implementation has errors. For example, the X-XSS-Protection header returns 1; mode=block twice in the same header.
If there is anyone here from the Yammer team, let me know and I'll show you.
From my perspective, it seems that everything has gotten way more bloated there is an assumption that everyone has unlimited data and bandwidth. I used to have a 1GB data cap on my phone that I would blow out in a couple of weeks from just reading news websites. For example, bloomberg.com shouldn't need to make nearly ~300 requests and download 18mb of data just to load the front page.