Friendly reminder that when a third-party provider requires you to load their script in a render-blocking manner, their problems become your problems.

Got an email about a massive performance regression from a past client yesterday. Turns out a third-party provider was (still is) having server issues causing an absolutely massive regression in LCP. Thankfully an easy and quick fix: remove the script.

Always build with resilience in mind.

Me, a professional, who gets paid to help companies for with performance, looking at a popular indoor hydroponics garden company's site, knowing darn well I could just buy the thing:

I wonder if they would give me a free stand if I helped them fix their performance?

Today in "our tools need to get better".....

Next.js driven document is 2.6MB, 1.5MB of which is all of Next's generated inline JSON stuff.

🚀 perfwork is now live! https://www.perfwork.com

I wrote a little bit about why I built it, and a little bit about what I've got in mind going forward.

https://timkadlec.com/remembers/2023-07-26-introducing-perfwork/

Started reaching out to companies who expressed early interest in https://www.perfwork.com/ to get their initial job listings up for the public launch

Message me if you're keen to post. I've got a hefty pre-launch discount to share for the first few listings.

Started working with these folks in mid-May and not gonna lie, pretty pleased with the progress they've made on INP in such a short span of time.

From a p75 of 4.25s in April (90% of sessions having a poor experience) to a p75 of 225ms in June (9% of sessions have a poor experience).

In a thread talking about why perf doesn't matter and it's a waste of time to focus on it: "users on 3G don't buy anything"

🤔 I wonder why that is?

We interrupt my usual performance posts for, I guess, a potential 🌶️ spicy take: design by democracy is less likely to ruin your product than the single visionary fairytale.

https://timkadlec.com/remembers/2023-06-30-single-visionary-fairytale/