Let's say you do need JS (or a drop-down, which you probably don't). That only leaves ~390K to explain.
-
-
-
Replying to @ryanflorence @slightlylate
You have a good point in this thread but you rope in all sorts of irrelevant things to try to make it. You regularly conflate "frameworks!" with "just too much JS for this page". React is 35kb. You point your finger at frameworks but that isn't the problem here at all.
1 reply 1 retweet 19 likes -
Replying to @ryanflorence @slightlylate
For instance, lets talk about that hero image, it's 242 kilobytes which is about seven Reacts! Or fonts. They've got 216 KB of fonts. That's another six Reacts! Their initial bundle should be smaller, but frameworks are the least of this site's problems.
1 reply 0 retweets 9 likes -
Replying to @ryanflorence
Fonts are a problem, but images aren't critical path. And font download is in competition with the JS in this trace.
1 reply 0 retweets 1 like -
Replying to @slightlylate @ryanflorence
I mean, if your point is that this site wasn't built well, ok. But nothing hurts as much as script, and there's waaaaaay too much of it here.
2 replies 0 retweets 0 likes -
Replying to @slightlylate
Right. Site wasn't built great, so why do you continually go straight for frameworks as the problem when they represent < 40kb of it?
1 reply 0 retweets 5 likes -
Replying to @ryanflorence
Why is it that the sites I see that avoid adopting framework-of-the-minute tend to do so much better? If you read my post you'll hopefully understand that I'm discussing a management and culture issue. Frameworks we can't afford being overused are a symptom.
2 replies 0 retweets 2 likes -
Replying to @slightlylate
You don't talk about any other symptoms though. Can you link me to two sites that don't use "framework-of-the-minute"? I'd love to see what they are.
1 reply 0 retweets 0 likes -
Replying to @ryanflorence
ICYMI, I linked a trace of such a site in the post itself: https://www.webpagetest.org/result/180827_FR_7ca373cd8e9e200d531c63fa03a14809/ …
3 replies 0 retweets 0 likes
And let's get straight on something: I'm focusing on 1p JS because it's the thing that's blocking interactivity of new sites more than anything else. Yes, fonts are often an issue. As are 3p scripts. But they don't matter until 1p JS is under control. Classic bottleneck.
-
-
Replying to @slightlylate @ryanflorence
To be fair the nice thing about building government services is that you get to see people build very similar things with widely different technical stacks and approaches. React could benefit from layered rendering rather than the typical client first approaches I see.
1 reply 0 retweets 0 likes -
I really like React, it's fun to develop with and in many ways expresses UI for me in ways that other frameworks never have. But I couldn't be honest and say that of the many audits I have done for services in GOV that the output is good for users.
1 reply 0 retweets 0 likes - 11 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.