Skip to main content

Blog

The case for static websites

Many business websites have a simple task. Explain the services, show the work, and help someone get in touch. A static site gives us fewer exposed components, and a foundation for performance.

The case for static sites

Many business websites have a simple task. Explain the services, show the work, and help someone get in touch.

The content might change a few times, but behind the scenes, there could be a whole application running, with a database, plugins, and software that needs regular attention.

That’s why more often than not I opt for a static website. It gives us a simpler setup, fewer exposed components, and a foundation for performance.

What is a static website?

A static website serves pages that are already built. When someone visits, the server sends the finished page.

Think about your services page. Most visitors need to see the same information. A static site will build that page when the content changes, then serve it until the next update.

“Static” describes how the page is delivered to a user. You can still have a modern design, animation, photo galleries, and interactive navigation. Forms and scheduling tools can connect to services that handle those functions. MDN explains the difference between static and dynamic websites.

How is that different from WordPress?

A WordPress website uses PHP to pull content from a database and assemble a page using its theme and plugins. That happens when a page is visited by a user. If you’re interested → How WordPress generates pages.

Caching can save a copy of the finished page so WordPress doesn’t have to repeat that work for every visitor. A well-built WordPress site can be fast. With static publishing, though, those finished pages are the starting point, and WordPress doesn’t need to run on the public server delivering them.

For a business whose website mostly presents information, that can remove quite a bit of unnecessary complexity.

Fewer things exposed to attack.

In November, PHP (the backend programming language used by WordPress) announced security fixes that included critical vulnerabilities, although the critical issues required unusual configurations. Keeping that software updated matters whenever your website depends on it.

A public website serving static files doesn’t need PHP, a WordPress login, or a content database to deliver its pages. When those components aren’t installed in that hosting environment, their vulnerabilities aren’t present there either.

That’s the practical meaning of a smaller attack surface. There are fewer exposed parts for someone to target.

Static sites still need care. Hosting accounts, connected forms, and any CMS behind the site need protection. Third-party scripts and development tools also deserve attention.

  • The Optimizely incident involved malicious JavaScript inserted into customer projects and delivered to visitors’ browsers. A static website loading an affected script could face that risk too. Optimizely’s incident report.
  • The malicious npm packages Microsoft investigated ran code when installed by developers. Tools used to build static websites can use npm, so the build process still needs protection. Microsoft’s investigation.

The benefit is reducing what the website depends on and being deliberate about what we add.

A starting point for speed.

Serving a finished page avoids the application processing and database queries that might otherwise happen before it can be sent.

That gives us less work to do when someone visits. It also lets us focus on what reaches their browser.

Large images, unnecessary JavaScript, and embedded widgets can still slow down a static site. We still need to build carefully. Static publishing gives us a useful foundation for that work.

I also like having direct control over the code. We can include the features a client needs and keep the rest of the implementation focused. That control helps with accessibility work, too, from clear headings to keyboard navigation and properly labeled forms.

Accessibility requires thoughtful implementation and testing regardless of the platform. Having control over the markup and behavior makes it easier to address problems directly.

You can still use a CMS.

“Will I need a developer every time I want to change something?”

You can have a CMS with a static website. WordPress, for example, can be the place where you write content and organize images. The publishing process then uses that content to build updated pages for the public site.

You keep an editing interface, and visitors receive the prepared pages. Changes appear once the updated files have been built and published.

The CMS still needs maintenance. Separating it from page delivery changes its role, but we still look after its software, accounts, and access.

How we handle updates for clients

The right arrangement depends on how involved you want to be. These three projects show a few ways we handle it:

Some clients want to publish themselves. Others would rather send us the changes and get back to their work. We can work around either preference.

When static makes sense

I’m especially interested in static websites for businesses whose content stays fairly consistent. Service pages, portfolios, and company information often work well this way.

If you only need occasional updates, going without a CMS can reduce long-term maintenance. There’s no CMS installation or set of CMS plugins to keep updated. When regular publishing makes a CMS useful, we can include one.

More complex needs, such as customer accounts, personalized dashboards, or transactions, may require additional systems. Those needs should guide the approach.

We look at what your website needs to do and who will manage it after launch. We can handle updates for you or connect a CMS your team can use.

If you’re wondering whether a static website would work for your business, let’s talk about it.