🟦 RUM INP attribution & subparts, including dimension filters (e.g. browser, connection type)
🟦 RUM update: lux.js v314
🟦 New synthetic test scripts
🟦 Upgraded test browsers for Industry Benchmarks
2 years ago—before I joined Google—some work I did was highlighted at I/O 2022. Then I was lucky enough to get my dream job at Google and prerecorded a talk for I/O 2023. And now I've got to talk live. I guess the only place to go from here is doing Sundar's keynote next year 😜
My pals in BBC World Service have been doing some awesome work on "lite" versions of their news articles (other page types to follow).
They essentially skip the Server-Side React hydration which means you end up with a simpler HTML+CSS page, no JS.
Page sizes drop significantly:
> In addition to advanced settings, navigation types, and page attributes, we've just released more diagnostic detail for the latest flavor in Core Web Vitals: Interaction to Next Paint (INP).
This looks great, will use it ASAP for client sites!
> In addition to advanced settings, navigation types, and page attributes, we've just released more diagnostic detail for the latest flavor in Core Web Vitals: Interaction to Next Paint (INP).
This looks great, will use it ASAP for client sites!
If you're building animated dialogs/menus, you should be building them with this and transition-behavior: allow-discreet, workarounds/hacks should only be used where absolutely necessary as they will rapidly become deadweight.
Accept where we are today, but build with the near future in mind.
PERFORMANCE HERO • per-FAWR-muhns HEER-oh • noun • A person who has made a huge contribution to the #webperf and #ux community, without whom the web would be a sadder, slower place.
I'm brainstorming topics for a brand-new #webperf / #ux conference talk. Tell me, folks... what burning questions/problems would you love to get answers for?
Bonus points for suggestions that are not about INP. 😉
I wonder if there's a better way to show page weight on leaderboards.
One thing could be to sync their Y-axis so that they're lines on the same base chart (instead of relative to own history only).
Another might be to then invert that axis with bottom the current largest and top the current-smallest. Or... maybe a singlestat number with current size of each and some kind of shared color range (no line/history until click).