
Jeremy Wagner
Jeremy Wagner is a Senior Technical Writer for Google Chrome. When he’s not writing and editing content about Core Web Vitals and web performance, you can find him nudging and death saving on pinball machines that have done him wrong.
Talks
-
Interaction to Next Paint: 2024 Edition
Now that Google has officially landed Interaction to Next Paint (INP) as a Core Web Vital metric earlier this year, it's now more of a priority than before to build user experiences that focus on responding quickly to user interactions. Even so, INP can be a tough metric to grasp. How is it defined? What are the nuances around it? How does one improve it? In this session, a quick overview on how INP works will be offered, and more importantly, observations from the community that have caused us to think differently about how the metric is perceived, and how that relates to the inner workings of the browser. Finally, some recommendations from the Web Performance Developer Relations team at Google will be provided, and other interesting optimization tips to put you on the path towards improving INP for your website.
-
Understand and plan for web feature adoption with Baseline
Historically, understanding the compatibility of web platform features hasn't been an easy task—various sites such as MDN and Can I Use have come a long way in helping developers to understand compatibility, but the adoption of new web features is still relatively conservative and slow. Baseline is an initiative originated by the Google Chrome team—now owned by the WebDX Community Group—that provides clear information on which web platform features are ready to use in your projects today. In this talk, an explanation of Baseline will be given, as well as ways that you can use Baseline in your project tooling to help you decide what features are ready for adoption, and how many of your website's users can benefit from them.