I've written some thoughts about what the key #webperf technologies of 2020 could be. Spoiler alert: not 5G or HTTP/3.https://simonhearne.com/2019/2020-predictions/ …
-
-
Replying to @simonhearne
Wow, your list and mine could not be more different.
1 reply 0 retweets 2 likes -
-
Replying to @simonhearne
1.) `font-display: optional` 2.) Perf Budgets (e.g., via Lighthouse CI) 3.) Workers (e.g., via Comlink) 4.) CSS Custom Paint (off-thread in '20) & Animation Worklet (w/ Scroll Timeline) 5.) SW-based MPA architecture (content stitching w/ streams) 6.) 4G penetration (yes, 4G!) ...
3 replies 2 retweets 8 likes -
Replying to @slightlylate @simonhearne
7.) Feature Policies for control (e.g., via Never-Slow Mode) 8.) Observability & feedback (on your list) 9.) Anaheim (Chromium-based Edge) killing polyfill bloat 10.) CSS features replacing JS libraries (no JS for, e.g., carousels) 11.) Bonus! Sequestering JS to the server-side.
1 reply 1 retweet 1 like -
Replying to @slightlylate @simonhearne
Others will have impact on fewer (but more heavily used) sites, e.g., better understanding and use of Service Worker code caching optimisations. Some have played out in '19 w/ too little fanfare; notably layout for non-latin text and JS parse speed improvements.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
All good points! In terms of crystal ball big shifts in web perf - SW.js, Lighthouse CI, removing polyfills, updating carousels etc. all require effort for _every_ site to improve. I wonder what % of sites changed 0 LOC in 2019.
2 replies 0 retweets 0 likes
Most. And for them, the wins in JS parsing and non-latin layout we saw this year were huge (particularly as 3P JS continued to grow): https://v8.dev/blog/preparser Off-thread comp & cache had similar effect last year: https://v8.dev/blog/background-compilation … https://v8.dev/blog/improved-code-caching …
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.