I'm still trying... https://www.webpagetest.org/result/180811_JS_2ab921531530addb85a7ff2cdace3661/ …
-
-
Replying to @slightlylate @michaelbenin1 reply 0 retweets 0 likes
-
Replying to @slightlylate @michaelbenin1 reply 0 retweets 0 likes
-
Replying to @slightlylate @michaelbenin
Here's video of the difference: https://www.webpagetest.org/video/view.php?id=180811_7aef36019aeadf3cd2fa8e86850537958bebf842 … And the timelines: https://www.webpagetest.org/video/compare.php?tests=180811_W9_9225fd126256bd1721ce5b4d8d8834d4-r:1-c:0,180811_7P_df566597ec85868e288a2867ca0dac4c-r:1-c:0# …
1 reply 0 retweets 0 likes -
Replying to @slightlylate @michaelbenin
Without getting into the first-party content, we can pretty definitively say at this point that the third-parties are sinking this experience. It's gonna be a bad time without an ad blocker *no matter what*.
1 reply 0 retweets 1 like -
Replying to @slightlylate @michaelbenin
Lets dive into the 1p-only trace (4G, Moto G4): https://www.webpagetest.org/result/180811_7P_df566597ec85868e288a2867ca0dac4c/ …
1 reply 0 retweets 0 likes -
Replying to @slightlylate @michaelbenin
I'm guessing this looks a lot like what the developer sees with devtools emulation turned on: https://www.webpagetest.org/video/compare.php?tests=180811_7P_df566597ec85868e288a2867ca0dac4c-r:1-c:0 …
1 reply 0 retweets 0 likes -
Replying to @slightlylate @michaelbenin
A few things jump out: 1.) SSR is indeed getting some content on screen relatively quickly, but at the cost of a pretty bloated initial payload; HTML is ~90K/575K (wire/uncompressed). 2.) The JS bundles are huge; more than 200K/1MB for two main 1p packages.
3 replies 0 retweets 0 likes -
Replying to @slightlylate @michaelbenin
All of that adds up to the redness at the bottom of the timeline in "Browser Main Thread": https://www.webpagetest.org/waterfall.php?test=180811_7P_df566597ec85868e288a2867ca0dac4c&run=1&cached=0&step=1&max=6&mime=1&state=1&cpu=1&bw=1 …
1 reply 0 retweets 0 likes -
Replying to @slightlylate @michaelbenin
There's something funky going on with the second script getting a new H/2 connection; not sure what that's about; see something similar for the fonts.
2 replies 0 retweets 0 likes
While that's concerning, the big issue is the raw amount of code being run on the main thread. SSR is helping you get content "up" at ~2s mark, but the content still feels "broken" for multiple seconds thereafter thanks to the heavy JS hit; not interactive here until ~6s.
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.