Why we moved our own site to Astro
Static-first HTML, zero unnecessary client JavaScript, and clean content collections. The reasoning behind our rebuild and the measured speed gains.
We spend our weeks making client websites faster, so when our own agency site started carrying an unnecessary client-side JavaScript bundle, it was time to rebuild it using the same standards.
The problem
Our previous site shipped a full single-page application runtime to render what were essentially static service pages, case studies, and a contact form. Visitors on mid-range mobile devices were downloading and parsing framework code just to read text.
The decision
We migrated to Astro with Tailwind CSS and typed Markdown Content Collections:
- Static HTML and CSS generated at build time, hosted on Cloudflare Pages
- Zero JavaScript shipped to marketing pages except the lightweight contact form submission handler and live CET clock
- Typed Zod schemas validating every bilingual case study and engineering article during build
The result
- First Contentful Paint dropped below 0.8 seconds on throttled mobile connections
- Near-zero runtime JavaScript payload across service and white-label landing pages
- Clean bilingual routing (
/for English,/slfor Slovenian) with straightforward Git-based content updates
For marketing sites, service pages, documentation, and content hubs, Astro’s default model (HTML first, JavaScript only where interactivity actually earns its weight) remains the fastest option on the web.