As you probably know, inline CSS isn't cached, so it has to be downloaded every time, which is a waste of bandwidth. Obviously 2 lines probably isn't worth making an external CSS file for; but thousands of lines are.
You can prefetch and pre-connect to mitigate some on the latency issues [1].
The roundtrips from the TLS negotiation and TCP handshake are a waste of time by introducing latency.
It’s 2025. There is X/Twitter, Facebook, TikTok, BlueSky, Mastodon , Instagram, YouTube, Starlink, glass fibre cables on the sea floor and to (a select few) homes, etc.
Latency is a far worse bottleneck than bandwidth. And more difficult to physically improve. And worse on mobile where almost everybody is.
What are good numbers on gzipping 20,000 lines of CSS from React apps or Tailwind or Bootstrap or all the other CSS parties?
alwillis•6mo ago
You can prefetch and pre-connect to mitigate some on the latency issues [1].
[1]: "Speculative loading" -- https://developer.mozilla.org/en-US/docs/Web/Performance/Gui...
dapperdrake•6mo ago
It’s 2025. There is X/Twitter, Facebook, TikTok, BlueSky, Mastodon , Instagram, YouTube, Starlink, glass fibre cables on the sea floor and to (a select few) homes, etc.
Latency is a far worse bottleneck than bandwidth. And more difficult to physically improve. And worse on mobile where almost everybody is.
What are good numbers on gzipping 20,000 lines of CSS from React apps or Tailwind or Bootstrap or all the other CSS parties?