> Silly example is gmail, which loaded in 1s on my 2011 MacBook Pro when new, if it load it again today (I just tried) it takes 35 seconds before I can click anything.
Gmail currently does easily over 50 HTTP requests when loading, and browsers limit the number of connections:
https://docs.pushtechnology.com/cloud/latest/manual/html/des...
The net effect is that you wait at least 8x (but probably much more) your ping to the server for the page to load.
It's sort of a plague in enterprise web apps and stems from the fact that nowadays you have small teams working on independent modules, which do their own requests. Banking apps are the worst offender here.
Also some people are simply unaware of/ignore the issue. The other day I inspected an e-store my friend paid decent money to set up and the first thing that I noticed was that it was firing 200+ requests, because the devs neither bundled nor minified their code.
I thought this was because it was still in development - nope - another store by the same company had the same issues, causing the site to load 12s+ on a good connection, and 30s+ on a 4G simulator.