Just because you can get SSR wrong doesn’t mean you should bet on a technology that won’t ever let you get it right. H2 and SW have similar footguns; I wouldn’t use a framework that prevented me from using them.
@chadhietala posted traces in the comments: https://infrequently.org/2018/09/the-developer-experience-bait-and-switch/#comment-256438 …
Here are the preact-only sets of runs:
CSR: http://www.webpagetest.org/result/180202_67_ae21f1a34a7f570599edae125e1c292a/ …
SSR+CSR: http://www.webpagetest.org/result/180202_VF_84ae556dc7c51e405d5fccccccb383ae/ …
-
-
As noted in the comments of the post,there's a lot of noise between runs. The user-timeline data seems to vary in access cost, which I presume affects both equally? Hard to know.
-
It looks like the SSR version gets ~complete 500ms sooner. This is interesting given the waterfall for the CSR version: http://www.webpagetest.org/result/180202_67_ae21f1a34a7f570599edae125e1c292a/3/details/ … Request for data is delayed by ~300ms because it's blocked by script eval? Why?
- 22 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.