Totally agree about this. Some bad stuff you can get into, and we should make JS-powered sites more bulletproof by default.
-
-
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.
3 replies 0 retweets 5 likes -
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 -
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 -
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 -
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 -
Googlebot runs JS; so that works fine. Anyway, we agree that SSR should not delay TTFB = )
3 replies 0 retweets 1 like
The broader point about delay loading JS is that it really has to be small chunks to avoid locking up the main thread.
-
-
Replying to @slightlylate @wycats and
So I can imagine many ways to make it work (chunked <script> blocks, e.g.), but haven't seen good solutions in the wild yet.
2 replies 0 retweets 1 like -
Replying to @slightlylate @wycats and
The best architectures I'm seeing right now in traces just run a LOT LESS JS; exotic strategies not required when you do less work = )
1 reply 0 retweets 3 likes - 18 more replies
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.