You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building a super-performant front-end is far harder and more intensive than making onLoad or onDomReady happen quicker — After you've removed "blocking scripts", what do you do?
In this talk I'll show you how to put best practice tools to work for you & your team.
We'll explore how to keep your pages scrolling buttery-smooth, the depths of undocumented Chrome devtool APIs, how to create your very own clean-room environment to test and measure while coordinating collection of performance metrics over many geographical borders — then how you can make it all happen within a continuous integration server.
I've been working on tooling to address all of the issues around front-end performance for a year or so now.
The text was updated successfully, but these errors were encountered:
Building a super-performant front-end is far harder and more intensive than making
onLoad
oronDomReady
happen quicker — After you've removed "blocking scripts", what do you do?In this talk I'll show you how to put best practice tools to work for you & your team.
We'll explore how to keep your pages scrolling buttery-smooth, the depths of undocumented Chrome devtool APIs, how to create your very own clean-room environment to test and measure while coordinating collection of performance metrics over many geographical borders — then how you can make it all happen within a continuous integration server.
I've been working on tooling to address all of the issues around front-end performance for a year or so now.
The text was updated successfully, but these errors were encountered: