Robin Marx
programmingart.bsky.social
Robin Marx
@programmingart.bsky.social
Network protocols (HTTP/2, HTTP/3, QUIC) and Web performance
at Akamai. PhD. Dad. Longsword fencer. He/Him.

http://linkedin.com/in/rmarx
@[email protected]
Slides?? Wardrobe!!
September 30, 2025 at 10:14 PM
Reposted by Robin Marx
Featured posts this week:
⚡ Fast and furious: @catchpointsystems.bsky.social
⚡ How browsers REALLY load Web pages: @programmingart.bsky.social
⚡ Client-Side Rendering: @adevnadia.bsky.social
⚡ More Edge features get a perf boost: Mohamed Mansour
Special thanks to the authors.🙏
February 23, 2025 at 3:32 PM
The "contributing" options on the web.dev bottom for example don't seem quite as inviting as say github.com/mdn/content, which imo helps reinforce the impression this is a google/chromium-first thing.

(just trying to provide some feedback on why I had my initial impressions on web.dev)
GitHub - mdn/content: The content behind MDN Web Docs
The content behind MDN Web Docs. Contribute to mdn/content development by creating an account on GitHub.
github.com
February 18, 2025 at 10:18 AM
Arguably, you can't expect Chrome engineers to add non-chromium behaviours in there, but it's also unclear (at least to me on the outside looking in) if you would accept contributions from say Firefox/Safari/outsiders to extend that type of article with cross-browser content (it's already extensive)
February 18, 2025 at 10:15 AM
Good to know this is the intent (as @paul.kinlan.me also echoed), but from my perspective, web.dev articles that talk about the type of topics I research, are usually still exceptionally chromium-focused, even for features in baseline (prime example being web.dev/articles/fet...).
Optimize resource loading with the Fetch Priority API  |  Articles  |  web.dev
The Fetch Priority API indicates the relative priority of resources to the browser. It can enable optimal loading and improve Core Web Vitals.
web.dev
February 18, 2025 at 10:13 AM
Thanks Patrick. I would definitely be interested in contributing docs, I'm just not sure where they would fit best. Web.dev is traditionally google/chromium-focused and not sure if they'd want to change. MDN doesn't seem to do much of this more "fuzzy" content in my experience, but maybe I'm wrong?
web.dev
Guidance to build modern web experiences that work in every browser.
Web.dev
February 18, 2025 at 9:37 AM
Sadly yes... Dinner date with the wife I'm afraid
February 1, 2025 at 5:19 PM
It was just bit.ly/loadline :)
config/benchmark/loadline - crossbench - Git at Google
bit.ly
February 1, 2025 at 4:57 PM
Let's hope we can re-invigorate that then :) Thanks for sharing!
December 18, 2024 at 4:18 PM
Hmz that's indeed much lower than I would have expected... Maybe @tunetheweb.com can have a look once he's less busy? 😇
December 11, 2024 at 3:00 PM
But as a percentage of all sites that use preload (the ~2.5 million):

235,535 / 2,506,138 = 0.09 = 9%
228,895 / 2,506,138 = 0.09 = 9%
so about 18% combined (round up to say 20% for the leftovers that uselessly preload more than 2 resources).

Hope that helps :)
December 11, 2024 at 10:31 AM
Hm, I think it's more like 20% :) Looking at the raw results (docs.google.com/spreadsheets...).

2,506,138 used preload (~20 of all desktop homepages)
235,535 has 1 unused preload (~1.9% of all desktop homepages)
228,895 has 2 unused preloads (~1.85% of all)

Combined <4% of total (as reported)
December 11, 2024 at 10:30 AM
MASSIVE thank you to @tunetheweb.com, without whom there would have been no data to write about in the first place!

Barry is consistently one of the kindest and most hardworking people in #webperf (and beyond) and deserves our gratitude!
December 10, 2024 at 12:40 PM