Back to writing
Nelson Lopez
Nelson Lopez

Draft - LoveVisuals: Part 3 - Why Astro Was the Perfect Choice

Draft - LoveVisuals: Part 3 - Why Astro Was the Perfect Choice

When I started working on LoveVisuals, I knew I needed a framework that could handle both performance and flexibility. Astro turned out to be the perfect choice, and this post explains why.

Why Astro?

Astro wasn’t just a technical choice for this project; it was a revelation. Coming from a background of mostly internal applications, I was used to frameworks that prioritized functionality over performance. Astro flipped that script. Its static site generation, component islands, and focus on shipping less JavaScript made me rethink how I approach web development.

Component Islands: A Game Changer

The concept of component islands was particularly powerful for LoveVisuals. Instead of shipping a full JavaScript framework for the entire site, I could use Svelte just where I needed it—for the video embeds and a few interactive elements. The rest of the site could be static HTML, CSS, and minimal JavaScript.

---
// Example of mixing Astro and Svelte
import VideoPlayer from '../components/VideoPlayer.svelte';
---

<main>
  <h1>Static content rendered at build time</h1>
  <VideoPlayer client:load />
</main>

Performance by Default

Astro’s focus on performance was evident from the start:

  • Lighthouse scores were consistently in the high 90s
  • The site loaded quickly, even with dozens of videos
  • The build process was fast and efficient
  • The development experience was smooth and intuitive

The Right Tool for the Job

What made Astro perfect for LoveVisuals wasn’t just its technical capabilities—it was how well it matched the project’s needs:

  • Static site generation for fast loading
  • Component islands for interactive elements
  • Built-in image optimization
  • Easy integration with other frameworks
  • Great developer experience

Lessons Learned

This project taught me several valuable lessons:

  1. Performance Matters More Than Ever
    Users expect sites to load quickly, and search engines reward fast performance. Astro’s focus on shipping less JavaScript was a game-changer.

  2. Choose the Right Tool for Each Job
    Instead of using one framework for everything, Astro let me use the best tool for each part of the site.

  3. Documentation is Part of the Process
    Writing about the technical decisions helped me understand them better and might help others facing similar challenges.

What’s Next?

This project has rekindled my interest in writing about development. I’m planning to:

  • Write more about technical decisions and lessons learned
  • Share tips and tricks that might help other developers
  • Document the process of building other interesting projects

What I learned:
Sometimes the right framework isn’t just about features—it’s about how well it matches your project’s needs and your development style. Astro was the perfect choice for LoveVisuals, and it’s made me excited about web development in a way I haven’t been in a while.


This is the final post in the LoveVisuals series. You can read the previous posts here: