Astro just became my default choice for new websites
1/2/2026
I regularly see obese client-side web applications, and it’s been years since I started asking myself: why? Why are we building those fat apps that take forever to develop, then to debug, then to optimize because they’re too heavy to load… when plain HTML and CSS would have done the job just fine?
There are obviously a few legitimate answers to this. But if you want to build something lighter, more efficient, and easier to maintain, hop in — you might love what follows!
Content first, interactivity then
Like other static site generators, Astro relies on files as the source of truth. Most of the content you create is just Markdown files and images. No build step gymnastics, no mystery state living in a browser tab: the page you ship is the page the user sees.
And this is exactly where Astro shines: zero JavaScript by default. You write your pages, Astro renders them to static HTML at build time, and the browser downloads a featherweight document that loads instantly. Only when a component genuinely needs to run code in the browser does Astro send JavaScript — what they call the “islands” architecture. A mobile menu, a theme toggle, a small form: each island hydrates on its own, without dragging the rest of the page along.
Why it clicked for me
I’ve used Astro for this very website, and honestly it was the smoothest experience I’ve had building a personal site:
- Content collections give your Markdown real structure — titles, dates, covers and descriptions validated at build time, not at runtime
- Image optimization built in: drop a JPG in, get responsive WebP out, automatically
- Integrations are one-liners: sitemap, RSS, and more just plug into the config
- It stays out of your way: no client-side router to babysit, no hydration bugs at 2am. The output is just… files. Which also means deployment is trivial — upload to any static host and you’re done
The honest caveats
Astro is not a silver bullet. If you’re building a highly interactive application — a dashboard, a collaborative editor, a real-time anything — you’ll want a full client-side framework instead. Astro happily hosts those islands too, but the sweet spot is clearly content-driven websites: blogs, portfolios, documentation, marketing pages. Which, let’s be honest, is most of the web.
The bottom line
Next time you start a website, ask yourself the real question: does this page need to be an app? If the answer is “mostly no, but this little widget needs JS”, Astro is probably your best default. Fast by default, boring in the best way, and it lets you focus on the content instead of the plumbing.