it's poetic and illustrates why the original chart is a poor analysis of the situation ;)
JS off the critical path is super-common, and most likely target for pruning.
-
-
sure.
@samccone tweets *a lot* about code *on* the critical path. in that case, parse time is real, yeah?@tbreisacher@tdreyno -
yes, but the conclusion *literally everyone* draws from the chart is to go measure bytes over wire
-
and I think we're agreeing that bytes-over-wire is much less important than bytes-in-critical-path
-
you may, for example, want to include some extra bytes so subsequent interactions don't trigger 1/
-
network fetches. those bytes will have a net positive impact on the early user experience 2/
-
but the "bytes-over-wire" metric will tell you to force another XHR. 3/3
-
in my experience, this is a second optimization. cutting critical path bytes makes a bigger diff.
@samccone@tbreisacher@tdreyno -
I have seen even critical-path bytes (which nobody really measures) really mislead people.
- 8 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.