Oops! You’ve chunked too hard!

Wouldn’t it be really nice if we could get a warning message from the browser that tells us when we’ve gone overboard with our enthusiastic code splitting?

From the years we’ve spent optimising performance at 1mg, we quickly learned that chasing objective improvements in the web vital scores not only start giving diminishing return post a threshold, but instead starts creating artefacts that can be very jarring for the user. Yes, your app is now really fast but is it pleasant for the user?

Talk contains: Understanding user psychology, perceived performance hacks, how important INP is, code splitting approaches, react server components, leveraging web APIs to tie it all in together.