1 min read
Fast by default: starting with less JavaScript
Why I start every project by shipping the minimum JavaScript to the browser and add interactivity only where it helps.
- #performance
- #architecture
- #astro
A site’s speed isn’t a luxury: it affects the experience, SEO, and the perception of quality. So I start from a simple idea: send the browser only the code the page actually needs.
The default-JavaScript problem
Many projects start with a framework that ships a large JavaScript bundle even when the page is almost static. The result: pages that take a while to become interactive, especially on phones and slow connections.
My approach
- HTML first. Most content is delivered already rendered.
- Targeted interactivity. I add JavaScript only to the components that need it, not to the whole page.
- Measure, don’t assume. I check real metrics (load, interactivity) before calling something done.
The result
Pages that load fast, work well on any device, and are easier to maintain. Interactivity is reserved for where it truly improves the experience.
Example note. Replace it with your own articles whenever you like.