That'd make the TTFB hit you usually pay for "SSR" more reasonable and prevent invisible breakage.
-
-
Replying to @slightlylate @jlongster and
What's the problem with background loading JS? Why does it affect TTFB?
1 reply 0 retweets 1 like -
Replying to @wycats @slightlylate and
Honestly, nobody should use SSR if it makes TTFI worse. TTFB also shouldn't be worse but if worse TTFB improves TTFI, seems ok?
1 reply 1 retweet 0 likes -
Replying to @wycats @jlongster and
Most SSR solutions I've traced do not flush() early, delaying delivery of markup to request critical resources; critical path pushed out.
2 replies 0 retweets 1 like -
Replying to @slightlylate @wycats and
This seems particularly framework-centric. Excited to see streaming pulled into this discussion to avoid the TTFB delays.
2 replies 0 retweets 1 like -
Replying to @slightlylate @wycats and
The approach that I've seen that works around this isn't much better: statically SSRing an "entrypoint", rehydrating full app for content
1 reply 0 retweets 0 likes -
Replying to @slightlylate @jlongster and
Hm that doesn't seem like a useful SSR solution. The point of user facing SSR is to get them Googlable content fast.
1 reply 0 retweets 1 like -
Replying to @wycats @jlongster and
Googlebot runs JS; so that works fine. Anyway, we agree that SSR should not delay TTFB = )
3 replies 0 retweets 1 like -
Replying to @slightlylate @jlongster and
Fine bingable. Also Googlebot runs some godawful old version of chrome that nobody wants to target (yay evergreen!)
1 reply 0 retweets 2 likes -
Godawful old version. Where's the @slightlylate that bet his career on evergreen ;)
-
-
Replying to @wycats @slightlylate and
We recently had to revert a polyfill clean up and delay release b/c of it. I don't want to make it a broader argument than that it matters.
1 reply 0 retweets 3 likes -
Replying to @sebmarkbage @slightlylate and
I'm hopeful Google will get on a more evergreen path for Googlebot.
0 replies 0 retweets 2 likes
End of conversation
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.