This feels like the right place to invoke @tomskitomski:
https://twitter.com/tomskitomski/status/1241009376653012993 …
If I had to guess, this probably wasn't ever tested on anything w/o a "Designed in Cupertino" badge.
-
-
Show this thread
-
It's *more than 900K of JS* to see the headline data. A screen shot is significantly smaller. Nothing about this is OK.
Show this thread -
Once -- just once -- I'd like to see prominent React peeps pitching in to fix these sorts of disasters instead of just excusing them.
Show this thread
New conversation -
-
-
I don't usually do this, but it's about public health and this site is getting a lot of press and HOLY !*#$ WHAT IS WRONG WITH THE GOOGLE COMMUNITY!? https://news.google.com/covid19/map literally has a lighthouse score of 2 and hits document complete at 13s https://www.webpagetest.org/result/200419_J0_0c275c3e7a6ecb3b7f99a02bc943121c/ …pic.twitter.com/2JduXMrFrU
-
Wasn't aware of this page. Will dig in.
- 7 more replies
New conversation -
-
-
"I don't usually do this..."

-
It's hard for me to explain the incredible volume of terrible experiences I see. What leaks out to twitter is the faintest echo of the collapse of usability web-wide driven by JS.
- 9 more replies
New conversation -
-
-
I agree with the sentiment that things like this should be incredibly accessible ...but how do you blame a whole ass community for this? As if someone who uses React is responsible for this website being unperformant?
-
This is a microcosm of the culture of performance failure that follows React everywhere it goes. A perfect, distilled instance of a trend that's so vast it's nearly impossible to get one's head around.
- 7 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.