Every website I've built for Webspansion is a static site, plain HTML, CSS, and a little JavaScript. No WordPress. No CMS. No database. No monthly server bill. No plugin updates. No security patches because someone shipped a vulnerable version of a plugin you've never heard of.
I get asked about this a lot. "Why not WordPress? Why not Squarespace? Why not Webflow?" The honest answer: for most of the clients I work with, a static site does everything they need better than any of those options, faster, cheaper, simpler, and with far fewer ways for things to go wrong after launch.
What a static site actually is
A static site is a collection of HTML files that a server sends directly to the browser. There's no database query, no server-side rendering, no PHP or Python running on a backend. When someone visits the site, the server just sends the files.
This sounds limited. In practice, it rarely is. The question most small business clients actually need answered is: can people find us, understand what we do, and get in touch? A static site can do all of that extremely well.
The real argument: complexity has a cost
WordPress is great. I'm not trying to trash it. But for a local nail salon, a youth nonprofit, or a first-generation immigrant-owned shop, the hidden costs of a CMS are real:
- Hosting that costs $10–30/month instead of $0 on GitHub Pages or Netlify
- Plugin updates that break things when you don't do them, and break different things when you do
- A backend admin panel that needs a login, a password, and someone to actually maintain it
- Security vulnerabilities from plugins that haven't been updated in two years
- A site that slows down over time as things accumulate
None of these things are dealbreakers for someone with a dedicated web team. But for a small organization with no technical person on staff, they're a genuine burden.
The best website for most small businesses is the one that stays up, loads fast, and doesn't break when nobody's looking at it.
Static sites aren't as limited as they used to be
Contact forms: handled by Web3Forms or Formspree, no backend needed. Analytics: Clarity or Plausible, dropped in with one script tag. Hosting: GitHub Pages, Netlify, or Vercel, free for static sites. Custom domain: $10–15/year from any registrar.
The thing static sites genuinely can't do: user accounts, dynamic content that changes per visitor, e-commerce with a server-side cart, blog posts that someone non-technical needs to write from an admin panel. For those use cases, you do need something more.
When I'd recommend something else
If someone needs to update their blog every week and they're not comfortable editing HTML, a static site is a bad fit. A CMS like WordPress, Ghost, or even a hosted solution like Squarespace makes more sense. If someone needs an online store with inventory management, Shopify or WooCommerce is the right answer.
I'm upfront about this when clients apply. Webspansion builds static sites. If that's not the right tool for what you need, I'll say so, it's more useful to point you in the right direction than to build the wrong thing.
But for most of the clients I work with? A fast, well-built static site hosted for free is exactly what they need. And it'll still be working perfectly five years from now, without anyone having to maintain it.
Common questions about static websites
What is a static website?+
A static site is a collection of HTML files that a server sends directly to the browser. There's no database query, no server-side rendering, and no PHP or Python running on a backend. When someone visits, the server just sends the files. That keeps things fast and simple.
Why does Webspansion only build static websites?+
For most of the clients I work with, a static site does everything they need better than WordPress, Squarespace, or Webflow, faster, cheaper, simpler, and with far fewer ways for things to go wrong after launch. There's no CMS, no database, no monthly server bill, and no plugin updates to maintain. For a small organization with no technical person on staff, that matters.
Can a static website have a contact form?+
Yes. Contact forms are handled by tools like Web3Forms or Formspree, so no backend is needed. Analytics can be added with a single script tag from Clarity or Plausible. Static sites aren't as limited as they used to be.
What can't a static website do?+
Static sites genuinely can't do user accounts, content that changes per visitor, e-commerce with a server-side cart, or blog posts that someone non-technical needs to write from an admin panel. For those use cases, you do need something more, and I'll say so when you apply rather than build the wrong thing.
How much does it cost to host a static website?+
Hosting a static site is free on GitHub Pages, Netlify, or Vercel, instead of the $10–30/month a CMS host can cost. The one optional cost is a custom domain, which runs about $10–15/year from any registrar.