Skip to main content
AstroSpark
Back to Engineering Articles
BenchmarksAug 5, 2026•1 min read

Why We Rebuilt Our Developer Portal and Docs on Tailwind CSS v4 and Astro 7

How moving away from heavyweight client-side frameworks delivered 100/100 Core Web Vitals, sub-second HMR, and zero runtime JavaScript overhead.

K
Kaelen Chen
Staff Design Systems Engineer

Speed is a competitive moat for developer-facing companies. When an engineer visits a documentation portal or pricing calculator, every 100ms of latency erodes conversion and trust.

When rebuilding our web properties in mid-2026, we established three non-negotiable architectural mandates:

  1. Zero Client Runtime JavaScript by Default: Every page must render pure, accessible HTML and CSS unless explicitly hydrated.
  2. Instant Developer Feedback: Vite-powered HMR compile times under 50 milliseconds.
  3. Flawless Type-Safety: Direct schema validation from content markdown through to layout props.

The Results

Switching our stack to Astro 7 paired with Tailwind CSS v4’s CSS-first @theme engine allowed us to delete 420kB of bundle overhead, achieving a perfect 100/100 Lighthouse performance audit on all desktop and mobile viewports.