Until a year or so ago you could read Twitter with Javascript disabled in your browser. So we know zero lines of Javascript are actually required to read tweets.

I just stopped clicking in Twitter links once they intentionally disabled browsing without Javascript, and use Nitter.net if there's a tweet I really want to read.

One can also embed tweet with nitter by adding /embed in the end and with iframe tag. Eg: https://nitter.fly.dev/mhevery/status/1606438382561026049/em...

Pagespeed score: https://pagespeed.web.dev/report?url=https://nitter.fly.dev/...

reference: https://github.com/zedeus/nitter/pull/515

> What hope does an average site have if a simple tweet requires MegaBytes of JS and seconds to interactivity?

Their hope is that their orgs probably aren't as bloated as twitter's

Watching the browser choke two load points to make it appear is truly disgusting.

Honestly pathetic considering the size the engineering team used to be and points to an extremely broken culture.

There is also this alternative solution if you are using react/next

https://static-tweet.vercel.app/

> What hope does an average site have if a simple tweet requires MegaBytes of JS and seconds to interactivity?

But dev deploying that abomination spent whole days less by just including random shit instead of understand the problems they solve! That's investor value!

JS: 1.5MB PageSpeed score: 61/100 Time to Interactive: 9 sec TBT: 1.7 sec