So I said I'm going to start discussing how "modern" frontend practice impacts experiences using public sector sites. Lets get into it. You know who deserves the very best experience? Our Veterans. ...meanwhile at http://vets.gov ...: https://www.webpagetest.org/result/180912_6Q_5fd08e0ef64071de6f3cd266c36a3cac/ …
-
-
Because this is in the now-traditional style of cultural-React-inspired DIY-bloat (everything's pluggable, which means an exercise to the reader), the app bundle includes Proptypes, what *looks* like a full copy of Lodash, and oh so very much more.
Show this thread -
The net result is to push TTI in this trace back nearly 4 full seconds: https://www.webpagetest.org/video/compare.php?tests=180912_6Q_5fd08e0ef64071de6f3cd266c36a3cac-r:1-c:0 …
Show this thread -
There's a lot going on deeper in this app, it seems: https://github.com/department-of-veterans-affairs/vets-website/tree/master/content/pages … But why is the front-page paying for that? Why are our vets and their loved ones being slowed down in accessing essential services this way?
Show this thread -
If there's something that *doesn't* need React, it's a drop-down menu. The sport of pure-CSS drop-downs was won more than a decade ago. There's no excuse.
Show this thread
End of conversation
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.