New series: what assistive tech really hears on your checkout page. Start with part one →
Shipwright
Home
JavaScript Jul 23, 2026 1 min read 273 views

What the Network Panel Taught Us About Our Bundle

June Park

June Park

@junepark

Share
Cover illustration for the article What the Network Panel Taught Us About Our Bundle

Screenshots of the waterfall that led us to a 40 percent smaller bundle. JavaScript gives you a dozen ways to solve the same problem, and the platform quietly added a better one while most of us were not looking. This post walks through that better way and the reasoning behind it.

What the screenshots show

The first version of our code worked on a fast laptop and failed on a slow phone. Nothing was wrong with the logic; the timing assumptions were simply never written down, so nobody noticed when they stopped being true.

We will revisit this in six months with fresh numbers. If the results change, we will update the post and note what changed at the end.

If you try this on your own project, start with one page or one service rather than the whole codebase. A small experiment gives you real numbers to argue with, and it is easy to roll back if the idea does not fit.

We have been running this approach for several months now. The initial setup took about a day, and the ongoing cost is close to zero once the team knows where to look.

What we would change next time

None of this is new, and that is the point. The techniques that last are usually the boring ones that are documented well and supported by the platform itself.

  • Measure on a throttled CPU, not your laptop.
  • Clean up listeners in the same place you add them.
  • Treat every network call as cancellable.
  • Log the slow path, not just the error path.
June Park

June Park

Author

Frontend engineer working across React and TypeScript. June writes the posts she wishes she had found while debugging.

Related Posts

Comments 0

Leave a comment

Your email will not be published. Sign in for a faster experience.

Supports **bold**, *italic*, and `code`.