The American flag loading icon is cute, but maybe it wouldn’t be necessary if http://code.gov was less than half a megabyte
-
-
Replying to @Pinboard
The problem is less the 0.5M of the entire site and more the ~280KB of blocking script required to show something /
@slightlylate2 replies 1 retweet 2 likes -
-
Replying to @Pinboard
The root of the problem is lack of testing on actual devices over actual networks. Results in slowness
2 replies 0 retweets 1 like -
Replying to @yoavweiss
with respect, the root of the problem is bloat. You don’t have to test vanilla HTML+CSS over a variety of networks
1 reply 0 retweets 6 likes -
Replying to @Pinboard
I think you're agreeing. You can have an 8mb html doc that renders once the first 20k lands. The type of bloat matters
@yoavweiss3 replies 0 retweets 2 likes -
web developers eagerly throw away progressive rendering and streaming
1 reply 0 retweets 2 likes
or you have people who do progressive loading correctly, but then others add tracking or ad scripts that break it
-
-
Replying to @Pinboard @yoavweiss
yeah, when people started async-loading scripts, it unleashed a world of content-shifting
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.