React vs Plain HTML:
Does Your Business Site Need a Framework?

Introduction

If you're commissioning a website for your business, you'll hear conflicting advice. Some developers insist you need React or Next.js. Others say plain HTML is perfectly fine. And a growing number recommend middle-ground solutions like Astro that feel like frameworks but output static HTML.

There's a real industry discussion happening right now. In July 2026, Frontend Focus #750 asked the question directly: "Do We Still Need Build Tools for Frontend Dev?" Ollie Williams' feature-by-feature audit concluded that vendor prefixing and ES5 transpilation are becoming obsolete, and Sass features are largely absorbed into native CSS — but bundling and minification remain relevant. Meanwhile, React Status #483 featured Kent C. Dodds declaring that "the framework wars are over" — React won, but most business sites don't need React.

This article cuts through the noise. I've been building websites since 2005 — long before React existed — and I work with all the major frameworks today. Here's what I tell business owners who ask me whether their site needs a JavaScript framework or plain HTML.

The Core Question: What Does Your Site Actually Do?

The answer depends on one thing: what kind of site are you building? Not every website is a web application. Most business websites — even professional, high-performing ones — are fundamentally content delivery systems. They present information to visitors. That's it.

The distinction between a content site and a web application is the most important decision factor:

When Plain HTML/CSS/JS Is the Right Choice

For the majority of business websites, plain HTML with modern CSS is not just adequate — it's better. Here's why:

1. Performance Is Free

A plain HTML page loads immediately. There's no JavaScript bundle to download, parse, and execute before the user sees content. No framework runtime. No virtual DOM. The browser gets HTML and renders it. This is the fastest possible experience.

Core Web Vitals — Google's ranking signals for page experience — are trivially easy to pass with a well-built HTML site. No hydration issues, no layout shifts from JavaScript injecting content, no blocking scripts. My own corporate sites built with plain HTML consistently achieve LCP under 1.5 seconds and Cumulative Layout Shift of 0.

2. Modern CSS Is Remarkably Capable

CSS has evolved enormously. What used to require a framework or JavaScript can now be done in pure CSS:

• CSS Grid and Flexbox — complex layouts without any framework
• CSS Container Queries — responsive components that adapt to their container, not the viewport
• CSS View Transitions — smooth page transitions with a single meta tag
• Relative Color Syntax — manipulate colors in CSS (darken, lighten, adjust hue)
• CSS Anchor Positioning — tooltips, popovers, and dropdowns without JavaScript
• CSS Mixins — reusable style patterns (Chromium implementation in progress)

For a deep dive on these capabilities, see my CSS Container Queries guide and Relative Color Syntax guide. The point is: modern CSS handles what once required a framework.

3. Lower Cost and Faster Delivery

A plain HTML site takes less time to build and has no dependency maintenance costs. My rates: a landing page from 300 BYN (~$100), a corporate site from 4,500 BYN (~$1,500). A React/Next.js web application starts from 6,000 BYN (~$2,000) and can go up to 25,000 BYN for complex applications.

The cost difference isn't about the framework itself — it's about the additional complexity: build tooling, routing, state management, API integration, testing infrastructure, and ongoing dependency updates. If you don't need those, why pay for them?

4. Security and Maintenance Simplicity

A plain HTML site has zero JavaScript dependencies. That means zero npm packages to audit, zero supply chain risks, zero breaking updates. The npm ecosystem has seen increasingly sophisticated supply chain attacks — see my analysis of the 2026 npm Mini Shai-Hulud attack — and every framework dependency you add is another potential entry point.

A well-architected plain HTML site can run for years with minimal changes. A React site that's not actively maintained will accumulate security vulnerabilities in its dependency tree within months.

When a JavaScript Framework Makes Sense

Frameworks exist for a reason. For certain types of projects, they're not just beneficial — they're necessary. Here's when React, Next.js, or Vue are the right choice:

1. You're Building a Web Application, Not a Website

If your project involves complex state management, real-time data, user accounts, multi-step forms, or a dashboard — you need a framework. A SaaS platform, booking portal, admin panel, or interactive tool benefits enormously from React's component model, state management, and ecosystem.

For these projects, I typically recommend React with Next.js (for SSR/SEO) or Vue with Nuxt (for faster development). The additional complexity is justified because you're building something that genuinely needs it.

2. You Plan to Build a Mobile App

If you know from the start that you'll need an iOS and Android app alongside your website, React is the strategic choice. React Native shares the same component model and ecosystem as React for web. You can share business logic, state management, and even significant portions of your UI code between web and mobile.

This is one of the few scenarios where React's ecosystem advantage is decisive. For a deeper comparison of React vs its alternatives, see my React vs Vue vs Angular comparison and my React vs Next.js guide.

3. Your Site Requires Complex Client-Side Interactivity

Think drag-and-drop interfaces, real-time collaborative editing, interactive data visualizations, or complex form wizards. These benefit from React's declarative approach to UI — you describe what the UI should look like for a given state, and React handles the updates.

That said, many interactions that used to require React can now be done with native Web APIs. The bar for "complex enough to need React" has risen as the platform has matured.

4. You're Building a Large-Scale Application with a Team

For enterprise applications developed by multiple developers over years, framework conventions enforce consistency. Angular excels here with its opinionated structure. React with Next.js also scales well — especially with the React 19 Server Components architecture. For a detailed look at what React 19 brings, see my React Compiler guide and Next.js 16.3 preview.

The Middle Ground: Astro, Static Sites, and Island Architecture

Not everything is binary. A growing category of tools bridges the gap between plain HTML and full JavaScript frameworks. The most notable is Astro.

Astro lets you use components from React, Vue, or Svelte but renders them to static HTML at build time — sending zero JavaScript to the browser by default. Interactive components become "islands" that load their JavaScript only when they become visible on the page.

This is an excellent middle ground: you get the developer experience of component-based development with the performance of static HTML. For content-driven business sites, Astro delivers fast pages, excellent SEO, and the flexibility to add interactivity where needed. Read my Astro 6.4 guide for the full details, including its new Rust-powered Markdown processor.

Decision Framework

Here's a simple way to decide, based on your situation:

FAQ

Need Help Deciding?

Choosing between plain HTML and a JavaScript framework shouldn't be stressful. The right answer depends on your specific business goals, timeline, and budget. I've built projects with both approaches — from simple landing pages to complex SaaS platforms — and I can help you make the right call without upselling you into technology you don't need.

I'm a full-stack web developer with 20+ years of experience working in both plain HTML/CSS/JS and modern frameworks (React, Next.js, Vue, Angular). Based in Minsk and working with clients worldwide, let's discuss your project.