This is why I encourage teams to focus on "Time to Interactive"; it lies to you less about the real-world experience.https://twitter.com/justinfagnani/status/893134662767226880 …
-
-
Replying to @slightlylate
In the small tests that I've run, SSR improved time to interactive, have you not been finding that? I'd love to compare notes
4 replies 0 retweets 15 likes -
Replying to @sarah_edo
Have not been seeing that. Many sites are using "SSR" to get content rendered, but it then becomes unusable due to long script eval...
2 replies 0 retweets 6 likes -
Replying to @slightlylate @sarah_edo
...which would be bad enough, except that "SSR" techniques (done naively) also frequently delay time-to-first-byte too.
3 replies 0 retweets 5 likes -
Replying to @slightlylate @sarah_edo
Is this for heavy interaction sites? Seems like primarily consumption sites would have big benefits from SSR
1 reply 0 retweets 0 likes -
Replying to @jbaxleyiii @sarah_edo
Riddle me this: how am I meant to know _which_ 50% of interactions won't work on a site like that?
2 replies 0 retweets 1 like -
If you dropped the JS payload entirely, it'd all be interactive as soon as it renders (the goal, IMO).
1 reply 0 retweets 0 likes -
If you didn't paint anything until it was interactive, you get the same benefit. The "middle ground" is actually a chasm.
1 reply 0 retweets 0 likes
That we've done magic in the browser to make some content scrollable while pages camp out on the main thread doesn't make them usable.
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.