Noam Rosenthal

248 Followers
226 Following
31 Posts

Webperfing for Google Chrome

Views are my own, at a given moment (if that)

He/him

Well, @noam wrote up his plans for revamping LongTasks into Long Animation Frames, and they look great!! https://github.com/w3c/longtasks/blob/loaf-explainer/loaf-explainer.md
longtasks/loaf-explainer.md at loaf-explainer · w3c/longtasks

Long Task API. Contribute to w3c/longtasks development by creating an account on GitHub.

GitHub
Just because you can measure something, doesn't mean it's the most important thing. Vice versa.

RT @nomsternom
Gonna speak in this upcoming meetup in Herzliya (Israel) about how I broke performance.timeOrigin right before my paternity leave 😬, left a messy regression for @yoavweiss, and why different clocks ⏰🕰️ in @ChromiumDev are more than meets the eye 👁️...

https://www.meetup.com/hodash-dev/events/290589223

Hodash Dev Meetup @ Varonis - Saving the Time ⏰: UI Libraries & Chrome Clocks, Tue, Jan 24, 2023, 6:30 PM | Meetup

We are excited to announce the January 2023 meetup 🤩 The meetup will be at **Varonis**, Herzliya. **Agenda**: * 18:30 - Mingling & 🍕🍺 * 19:30 - Constructing a Modern U

Meetup

I wrote a blog post about doing things in vanilla JavaScript. I'm really not a fan of frameworks, and since I'm currently working on a website redesign, I thought I'd write my thoughts here.

https://francisrubio.antaresph.dev/writing/building-websites-with-vanilla/

Building Websites with Vanilla

No, vanilla is not a framework.

Bad performance is bad accessibility. https://brucelawson.co.uk/2022/bad-performance-is-bad-accessibility/ - my riff on @slightlyoff's post.
Bruce Lawson's personal site

» Bad performance is bad accessibility

2022 is turning into a big year for Team Finding Out, and there's still a couple of weeks left, so join me in deciding that frontend's lost decade can also come to a close.

We can decide that the JS thinkfluencers actually *didn't* know what they were talking about and go HTML-first. And it can be better.

h/t, @noam:

https://calendar.perfplanet.com/2022/an-html-first-mental-model/

An HTML-first Mental Model

... while building a fast movies app Overview The Movies App The TasteJS movies app is a showcase for different frameworks. I was excited about it because it gave me an opportunity to test some hypothesis, and see if it holds in the context of an app that's a bit less trivial than TodoMVC.

Web Performance Calendar

A #webperf thought after profiling some sites in the wild:

Look at the different parts of the DOM tree & JS that your users get. Do they look like...

1. Your mental model as a dev
2. Your org-chart, how your teams are set up
3. How users experience your site

If it's not (3), perhaps your tools are wasteful?

My Perf Calendar article is out!

"An HTML first mental model",
Writing a fast movies app with vanilla, how to make it fast while maintaining a nice-ish developer experience?

https://calendar.perfplanet.com/2022/an-html-first-mental-model/

An HTML-first Mental Model

... while building a fast movies app Overview The Movies App The TasteJS movies app is a showcase for different frameworks. I was excited about it because it gave me an opportunity to test some hypothesis, and see if it holds in the context of an app that's a bit less trivial than TodoMVC.

Web Performance Calendar

I think a lot of people on here follow me because of Core Web Vitals, so I wanted to let people know we're working on clarifying the intent of the Largest Contentful Paint metric (LCP) in https://github.com/w3c/largest-contentful-paint/issues/86

Specifically, we want to clarify that placeholder images are NOT intended to be candidates for LCP, as they're not contentful.

Improve unimportant image heuristic · Issue #86 · w3c/largest-contentful-paint

Currently we use a heuristic to exclude certain images from being considered LCP candidates. For instance, we exclude images that take the full viewport. This heuristic is imperfect as it could exc...

GitHub
I'm wondering if any of that is possible at all :( all of this info is some derivative of tracing JS. Right now we don't trace JS at all (except for devtools)