Honestly, I'd love to see "SSR"d sites simply not ship JS on first load and only pull in JS when served from SW.
-
-
Replying to @slightlylate @jlongster and
That'd make the TTFB hit you usually pay for "SSR" more reasonable and prevent invisible breakage.
1 reply 0 retweets 0 likes -
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 @wycats and
To be fair, it's Chrome 41 and Googlebot is hardly the only bot one should target. Each one has different capabilities. Many don't run JS.
1 reply 0 retweets 2 likes
If bots are gonna run JS, they should be evergreen.
-
-
Replying to @wycats @slightlylate and
Agree, that'd be nice, but I was just stating the current reality :)
0 replies 0 retweets 1 likeThanks. 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.