The "SSR is for performance" folks need to be posting traces from mid/low-end devices/networks to demonstrate that their experiences get consistently interactive fast enough to make the magic trick actually work.
-
-
And would you say for those big sites, doing a full CSR approach is more performant? Or is it maybe the case that the CSR sites you’re asked to analyze suffer from all the trappings of large teams that make any form of consistent perf hard at the org level?
-
You tell him Mike. Things aren't bad in the way he says. They're only bad in the way YOU say. High five bro.
- 2 more replies
New conversation -
-
-
I think it would be clearer to object not to “SSR” but to isomorphic JS. You can have an arbitrarily large code size budget on the server (write as much Node JS as you need!) but you shouldn’t just ship all of that to the client. The client bundle has to be teeny tiny.
-
I think it’s confusing to object to SSR b/c it makes it sound like you’re opposed to PE. Plus, you can get clear wins converting a giant CSR app with 10s+ FCP and ~0 FID into a SSR rehydration monster with ~2s FCP and ~6s FID. SSR is a Pareto improvement! But it’s not *enough*.
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.