I smell 355kb of not framework!
-
-
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 -
Replying to @slightlylate
if your point is "static sites don't need a bunch of JavaScript" I agree. However, had they used gatsby you'd get super fast server renders AND sw precaching for bad networks when you might need access to that info on the go. Maybe were in the "gets worse before better" phase.
1 reply 0 retweets 3 likes
Got a good Gatsby trace handy? But the background here is that font issues (the second-most frequent issue) are much easier to remediate. A bit of <link rel="preconnect"> here, some `display: optional` there. Mostly done and dusted.
-
-
Replying to @slightlylate @ryanflorence
How about this gatsby site https://marvelapp.com/ ?
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Replying to @slightlylate @ryanflorence
this is all very enlightening and educational, please do continue your discussion :-)
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.