request chains can def get long; as we move further off polymer to lit-element / vanilla they reduce each time. HTTP2 w/ our preference toward hitting multiple properties I believe will see us be more efficient over the long run (students take multiple courses as example)
-
-
The less aggressive version is some bundling variant, ala
@dam'shttps://dev.to/begin/progressive-bundling-1gj2 … -
A few other things from this trace jump out: 1.) I'm seeing multiple H/2 connection setups to https://cdn.webcomponents.psu.edu/ . Seems like it could collapse to 1? 2.) https://oer.hax.psu.edu/bto108/sites/ist402/files/IMG_20190823_102434%202.jpg … is very big! On a slow link, starving other fetches.
- 3 more replies
New conversation -
-
-
def didn't grok that from looking through PRPL w/ the polymer app build tooling that our team was reverse engineering / picking through 3 years ago when we went down the WC route. We'll have to revisit this now that our app's a bit more well defined
Thanks. 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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.