Spent a lot of the last 6 months helping partners analyse the performance of their PWAs. Biggest lesson: RUN LESS JS. Second: DELAY LOAD.
-
-
Replying to @slightlylate
Our take on it is: How do we make adding more overall JS not slowdown start up? Scalability. Takes you down a different route.
1 reply 1 retweet 5 likes -
Replying to @sebmarkbage
: two related things: running less code is always better. Let the browser do what it can. Second, timing matters
1 reply 0 retweets 1 like -
Replying to @slightlylate
: I see lots of React apps screw themselves by loading everything up front; webpack and script-centricness defeat browser help
1 reply 0 retweets 1 like -
Replying to @slightlylate
: if you could break up the work and load modularly, when needed, that can work... but that's not where React apps are at today
2 replies 1 retweet 1 like -
Replying to @slightlylate
: I traced an app yesterday that had 7s of eval + mountComponent() work (on an android one device)
2 replies 0 retweets 2 likes -
Replying to @slightlylate
Did you measure how much of that was actually parse time misattributed to mountComponent? Seen that.
1 reply 0 retweets 2 likes
: great question; not sure. Will dig deeper after I/O.
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.