There is a dentist somewhere paying forty dollars a month for managed WordPress hosting, two hundred a year for a premium theme, and five hundred every couple of years to a developer who “updates the site.” The site has not actually changed since 2022. It is two pages and a contact form. The developer updates the plugins, makes sure nothing is broken, and sends an invoice.
That dentist is running a static website in a CMS costume. And they are not alone. Nearly half of all WordPress sites go six months or longer without a content update. For a lot of small businesses, “having WordPress” means having a database, a PHP runtime, and 50,000 lines of code they do not need, sitting behind a login page they never visit.
This is not a knock on WordPress. WordPress is great at what it does. But when the question is “does my plumber’s three-page website need a content management system,” the honest answer, most of the time, is no.
What a static site actually is
A static site is an HTML file. Maybe two or three HTML files. CSS for styling, maybe a small JavaScript file for a mobile menu or contact form. No database. No server-side processing. No PHP, no plugins, no admin panel. You open the file in a browser and it works. Upload it to a web server and it is live.
That is not primitive — that is the entire architecture of the fastest websites on the internet. When there is no database to query, no PHP to execute, no plugin chain to resolve, the page loads before the visitor’s thumb lifts off the screen. A WordPress site on standard hosting averages three to five seconds on mobile. A static HTML file on Cloudflare Pages or Netlify routinely loads in under one second. That is not a minor difference. A one-second improvement in mobile speed increases conversions by up to 27 percent.
The cost difference is not small
WordPress has a running tab. Hosting: 10 to 100 dollars a month depending on whether you are on shared, managed, or something in between. A premium theme: 50 to 200 a year. Essential plugins — a form builder, a caching plugin, an SEO tool, maybe a security scanner — another 200 to 1,000 a year. Annual maintenance if you hire someone: 500 to 5,000 depending on how much hand-holding is involved. Add it up and a simple WordPress brochure site costs somewhere between 500 and 3,000 dollars a year to keep alive. For a site that nobody is updating.
A static site on Netlify’s free tier costs zero. Cloudflare Pages, also zero. Both include SSL, CDN, and more bandwidth than any small business will ever use. The hosting bill for a dentist’s static site is literally nothing. The annual maintenance bill is also nothing, because there are no plugins to update, no database to back up, no PHP version to patch.
For a business owner watching every dollar — and most small business owners are — the difference between $1,500 a year and zero is real money. That is a quarter’s worth of Google Ads budget. That is a new sign for the storefront. That is money doing something instead of keeping a database alive for no reason.
The security argument is not theoretical
In 2025, researchers logged over 11,000 new WordPress vulnerabilities — a 42 percent increase from the year before. Ninety-one percent of those vulnerabilities were in plugins. Nearly half had no developer patch available when they were disclosed. The median time between a vulnerability being made public and mass exploitation beginning was five hours.
Roughly 13,000 WordPress sites get compromised every day. Not targeted attacks by sophisticated hackers — automated bots scanning the internet for unpatched plugins and known exploits. A small business owner is not checking their WordPress dashboard for security updates. They probably forgot the login URL. Their site is sitting there with a contact form plugin from 2023 and a prayer.
A static HTML file has no database to inject, no admin panel to brute-force, no plugin to exploit. The attack surface is effectively zero. You cannot hack a file that does not execute code. This is not security through cleverness. It is security through having nothing to attack.
When to go static
If the business checks most of these boxes, static is almost certainly the right call:
- The content changes once or twice a year at most
- There is no blog and there is never going to be one
- The owner is never logging in to edit anything
- The site is under ten pages
- Speed and uptime are more important than flexibility
- The budget is tight and every recurring cost matters
That covers the majority of local businesses. Restaurants, dentists, small law firms, coffee shops, plumbers, electricians, yoga studios, barbershops, veterinarians. Their website is a digital business card. It needs to load fast, show up in local search, display the phone number, and look like a real place, not a template. A single HTML file does all of that better than WordPress for less money.
When WordPress actually makes sense
WordPress earns its complexity when the site needs to do things a flat file cannot:
- Regular content publishing. A real blog with a weekly cadence. Not “we should probably blog someday” — an actual publishing calendar. If the business is going to post once, get distracted, and never post again, that is not a blog. That is a dead page hurting your SEO.
- E-commerce. Selling products with a catalog, cart, checkout, and inventory management. WooCommerce exists for a reason, and it is good at this.
- User accounts. Memberships, student portals, client dashboards, gated content. If people need to log in and see personalized content, you need a CMS.
- The owner edits things themselves. And they actually will. Not “they want to be able to” — they actually sit down and change the hours when the hours change, update the menu when the menu changes, add photos when they take new photos. If this describes the client, WordPress is the right tool.
- Complex content types. A site with services, team members, case studies, events, and testimonials that all need to be managed independently. When the content model has more than two or three types, a CMS starts earning its keep.
The honest question is not “could this business benefit from a CMS.” Every business could theoretically benefit from a CMS. The question is “will this business actually use the CMS features that justify its cost and complexity.” For most local businesses, the answer is no.
The middle ground: static sites with a lightweight CMS
For the businesses that fall in between — they do not need WordPress, but they want to update the menu or change the hours without calling someone — there are options that did not exist a few years ago.
Decap CMS is a free, open-source, Git-based editor that sits on top of a static site. It gives the owner a clean editing interface for the content that actually changes — hours, prices, team bios — while the site itself stays static. No database, no server, no plugins to maintain. The content lives in the same repository as the code. Hosting is still free on Netlify or Cloudflare Pages.
Another approach: use WordPress locally as an authoring tool and export the site as static HTML with a plugin like Simply Static. The client gets the familiar WordPress editor. The live site is flat HTML. Best of both worlds, though it adds a step to the publishing workflow.
These are niche solutions and they are not for everyone. But they exist, and for the right business, they solve the “I want to edit one thing twice a year” problem without dragging in the entire WordPress ecosystem.
The Core Web Vitals argument
Google uses Core Web Vitals as ranking signals. Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift. Static HTML sites score 95 to 100 on these metrics out of the box, with LCP routinely under one second. WordPress on mobile? About 44 percent of sites pass all three metrics. Getting a WordPress site to compete on speed requires a caching plugin, a CDN, image optimization, deferred JavaScript, and sometimes a more expensive host. All of that is achievable, but it takes effort and money. A static file achieves it by default.
For local businesses competing on “plumber near me” or “dentist in [city],” page speed is a direct ranking factor. The fastest site in the local pack wins more clicks. A static site starts that race 50 meters ahead.
The library has both
There are 20 static HTML prompts for the businesses that should ship one file, and 20 WordPress prompts for the ones that genuinely need a CMS. The static prompts produce a single HTML file with inline CSS and JavaScript — drag it onto a host and go live. The WordPress prompts produce a full architecture: theme.json, custom post types, plugin stack, Gutenberg block markup, and a launch checklist.
Pick the right tool for the actual business, not the one that sounds more impressive. A static site that loads in 800 milliseconds and costs nothing to host is not a lesser choice. For most small businesses, it is the better one.
Still weighing it? The static vs WordPress breakdown goes deeper on the trade-offs, and the Claude walkthrough shows the static route end to end.
The questions people actually type
Do I need WordPress to build a website?
No. You need WordPress to publish often or to hand editing to non-technical people. A site whose content changes twice a year is better off as static files: faster, safer, and nothing to update on a Tuesday night.
Do I need WordPress hosting?
Only if you run WordPress. Static sites host free on Vercel or Netlify. If you do go the CMS route, managed WordPress hosting at $15 to $30 a month earns its keep in backups and PHP updates you never have to think about.
Why do I need WordPress at all, then?
Sometimes you genuinely do: a weekly blog, structured content like listings or locations, multiple editors, a store. That is WordPress earning its keep. The trap is paying CMS costs — hosting, updates, security surface — for a brochure site that never changes.