Why We Don’t Use React

Every agency we compete against builds on React. Or Next.js. Or Nuxt. Or Gatsby. Or Astro. The JavaScript framework ecosystem moves so fast that the stack you chose last year is already legacy. We don’t use any of them. And it’s the best technical decision we’ve made. The Framework Tax Here is what happens when you build a business website on React: 200-400KB of JavaScript before your first word of content loads. A vanilla HTML page loads in under 50KB. A build step that adds complexity, dependencies, and failure points. Our sites have no build step. The code you write is the code that ships. A dependency tree of hundreds of packages — each one a potential supply chain attack vector. The Axios attack proved this is not theoretical. Framework churn. React Server Components, the App Router, Suspense boundaries — the API surface changes constantly. Code written two years ago needs refactoring to follow current best practices. Vanilla JavaScript from 2016 still works perfectly. Hiring comp