Tim Kadlec’s Post

I'm incredibly excited about this! I've been a big fan of SpeedCurve since day one, and they've built an amazing team full of kind and supremely talented folks. I'm humbled to be able to be a part of it!

Plenty more work to do on this, but an 84% reduction isn't too shabby for a two line change. innerText forces reflow. It's aware of styling (it only returns content for non-hidden, human-readable elements. textContent isn't aware. It returns text regardless of if it's hidden or not. The trade-off matters in some situations, but in this, they were simply reading the content of an element and passing that value along elsewhere. It didn't matter if it was hidden or not. Each reflow by itself was fairly small, but it was death by a thousand cuts. #webperformance #javascript

Looks like we're down to the final 9 tickets for https://perfnow.nl/. I'm biased, naturally, but if you're interested in web performance, this is _the_ can't miss event of the year. Talks are great, yes, but those hallway conversations? That's what makes the event so special. You've got an incredible group of folks working on browsers, tooling, standards, optimizing performance at big companies, focused on performance at agencies....it's just an incredible mix of super talented folks and every year I walk away with a looooong list of new ideas to explore and follow-up on. Can't wait! #webperformance

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. We were able to establish a strong correlation between LCP and revenue for this company in the past, so this was clearly costing them money. Thankfully an easy and quick fix: remove the script. We talk a lot about the risk of single-points-of-failure like this for companies, but it's also risky for the providers! In this case, there's no reason why their script should be required to be loaded as a blocking resource, and now the client is looking at alternatives to purchase instead. Always build with resilience in mind. #webperformance #thirdparty #javascript

So yesterday I (finally) pulled back the covers on perfwork. I'm very happy to have this out, and hopeful it becomes a valuable resource for folks. I wrote a bit about why I built it and some ideas about the future: https://lnkd.in/gvNYEe8X

🎉 More on this coming very, very soon, but sooooo excited to have perfwork.com live now—job opportunities for web performance professionals and folks who want to work in the performance industry. I'm really hoping this becomes a great source for both employers and the web performance community. Much more coming (public roadmap: https://lnkd.in/drRdH-tp) soon. #webperformance #hiringdevelopers #performancetesting