If you've ever asked a web designer "is my site static or dynamic?" and walked away more confused than when you started, this guide is for you. The distinction matters — it affects how much your site costs to build, how easy it is to update, how fast it loads, and how well it holds up over time. But it gets explained in jargon when it really shouldn't.
Let me walk you through it the way I'd explain it over a coffee.
The basic difference
A static website is one where every page exists as a finished HTML file sitting on a server. When someone visits your site, the server hands them that file. Done. The file doesn't change unless someone edits it.
A dynamic website assembles each page on the fly when it's requested. Behind the scenes, a database holds your content. When a visitor lands on a page, the server pulls the content from the database, drops it into a template, and sends back the result. Same URL can show different content to different visitors, or change over time as the data changes.
WordPress is dynamic. So is your e-commerce store. So is Facebook. Anything where logged-in users see different things, where content updates regularly, where there are comments or filters or search — that's dynamic.
A landing page for a tradie? A brochure site for a dental practice? A handful of pages that rarely change? That can be static, and it'll be faster, cheaper, and more secure.
The three flavours of dynamic
When developers talk about dynamic websites, they usually mean one of three approaches.
1. Server-side rendering
This is the classic CMS approach — WordPress, Joomla, Drupal. When you load a page, your server runs PHP (or another language), pulls content from a database, builds the HTML, and sends it down. Every visit triggers this process.
Server-side is great for content-heavy sites with frequent updates. It's also where most of the security headaches live, because every page request is doing real work — running code, querying databases, loading plugins. That's surface area for things to go wrong.
2. Client-side rendering
Modern single-page apps work this way. The server sends a mostly-empty HTML shell plus a big chunk of JavaScript. The JavaScript runs in the visitor's browser, fetches data from an API, and builds the page in front of them. Think Gmail, Trello, most web apps you log into.
Fast once it's loaded, terrible for SEO if done poorly, overkill for a brochure site. Not what your dentist needs.
3. Hybrid / static site generators
This is the modern middle ground, and it's where I do a lot of my work these days. Tools like Astro, Eleventy, or Next.js build all your pages ahead of time (so they're as fast as static), but you can still write content in a CMS or markdown files. When you publish a change, the site rebuilds and re-deploys. The visitor gets a static file — fast, secure, no database — but you still get an easy way to update content.
Server-side dynamic (WordPress) is the default for most small business sites, and that's fine. But if your site rarely changes, going static can cut your hosting costs, eliminate plugin updates, and make your pages load in under a second.
When dynamic makes sense
Dynamic websites earn their complexity in specific situations:
- You publish regularly — blogs, news sites, anything with a content schedule benefits from a proper CMS
- You have a lot of pages — say you're a directory or have hundreds of products; building each page individually doesn't scale
- Users log in — member areas, dashboards, anything personalised needs to be dynamic
- You're selling online — e-commerce needs to handle inventory, payments, accounts
- Multiple staff need to update content — a CMS gives you user roles, version control, and a friendly editing interface
When static is the smarter call
Static sites quietly beat dynamic ones for a lot of small businesses:
- Local service businesses — tradies, professional services, anyone whose website is essentially a digital brochure
- Landing pages and campaign sites — speed matters more than anything for conversions
- Sites that rarely change — if you update once a quarter, you don't need a CMS
- Sites where security is critical — no database, no admin login, no plugins = nothing to hack
- Sites where you want low ongoing costs — static hosting is often free or under $10/month
The trade-off: making content changes requires either editing files directly (fine if you know HTML) or using a static site generator with a CMS layered on top.
What this means for your business
If someone's quoting you a dynamic WordPress build for a five-page brochure site, ask them why. There might be a good reason — maybe you'll be adding products, or you genuinely need member logins. But a lot of agencies default to WordPress because that's what they always build, not because it's right for the job.
A static site for a small service business often costs less to build, less to host, less to maintain, and loads faster. The "downside" — that you can't log in and edit it whenever you want — turns out to be irrelevant for businesses that update their site twice a year.
If your site needs to be updated by you regularly, WordPress is probably the right call, and there are ways to keep it lean (fewer plugins, lighter themes, proper hosting). If your site is essentially a working brochure that you set and forget, static is worth a conversation.
Still not sure which is right for your business? Get in touch — I'll give you an honest answer based on what you actually need, not what's easiest to sell.