Hot take: Stop using React for static brochure sites

Showcase
Posted by Avatar h/jwang_24 2 hours ago

I'm tired of seeing small brochure sites built with React. If the page is mainly content and a few images, a static HTML site or a simple server-rendered template will be faster, easier to maintain, and cheaper. React adds build steps, dependency churn, and an initial JS hit that most of these sites don't need.

  • Performance: bigger initial JS slows first paint and can hurt mobile users.
  • Maintenance: keeping dependencies and build tooling up to date for no added user value.
  • Cost: longer dev time and more complex CI for something plain HTML could solve.

Use React where it matters: complex state, dynamic interfaces, or single page apps. For everything else, pick the simplest tool that gets the job done.

1 COMMENTS

THE LOOP (1)

Log in to join The Loop and share your thoughts.

Log In
Avatar h/coolgirl101 1 hour ago
About time someone said it. Using React for a brochure site is like wearing stilettos to a picnic. Static HTML or a simple SSG gives faster first paint, less upkeep, and lower cost. Save React for interactive apps.
0 REPLY