We maintain WordPress sites with hundreds of posts and static sites with hundreds of pages, sometimes for the same kind of business. So when an owner asks which one they should have, we do not have a favorite to sell. We have a short list of questions, and the answers usually settle it in five minutes.
What the two words mean
A WordPress site is a program. Every time someone visits, a server runs code, asks a database for the page, assembles it, and sends it back. You log in to a dashboard to change things.
A static site is a folder of finished pages. They are built once, ahead of time, and a server hands them over exactly as they are. There is no database and no dashboard on the server, because there is nothing running there.
That difference sounds technical. It decides almost everything else.
Pick WordPress when someone on staff publishes every week
WordPress earns its keep when a non-technical person needs to write, edit, and publish without calling anyone. A law firm with an active blog is the classic case. One of the firms we work with has more than 550 posts, a daily publishing schedule, and staff who need to fix a typo at four in the afternoon. That site belongs on WordPress, and we have never tried to talk them out of it.
It is also the right call when you depend on a plugin that does something specific: a booking system, a membership area, a reviews feed your industry expects.
The honest costs:
- It needs maintenance forever. Core, theme, and every plugin ship updates. Skipping them is how sites get compromised.
- Speed takes work. Out of the box, a plugin-heavy WordPress site is slow on phones. Getting it fast means caching, image handling, and regular attention.
- Page builders lock you in. Content built in a visual builder is stored in that builder's own format. We once had to write a custom plugin just to publish pages into one programmatically.
Pick static when the site changes monthly, not daily
Most small business sites are not publications. A contractor, a bail bondsman, a solo attorney: the phone number, the services, and the service area change a few times a year. For those, a static site is better on nearly every axis.
- It is fast without trying. There is no code to run, so pages arrive almost instantly. A 305 page site we built for a Kansas defense attorney loads as quickly as a single page would.
- There is nothing to hack. No login page, no database, no plugins. The most common ways a small business site gets taken over simply do not exist.
- Hosting costs close to nothing. Static files are cheap to serve and do not fall over when a post goes viral.
- Scale is free. If you serve fourteen cities and offer eleven services, a build script can produce a correct page for every combination from one data file.
The honest cost is that changes go through a developer, or through a simple editing screen someone has to build for you. If you want to rewrite your homepage every Tuesday, that friction will annoy you.
The questions we actually ask
- Who will publish, and how often? Weekly or more, by staff: WordPress. Monthly or less: static.
- Has the site ever been hacked or gone down? If yes, static removes the cause instead of treating the symptoms.
- How many pages do you need that are the same shape? Many pages of one shape, like services by city, are a job for a generator.
- Is there a plugin you cannot live without? If the business runs on it, that decides the platform.
You can change your mind later
The choice is not permanent. We moved a realtor's site from WordPress to a static build and kept every page and article at its exact original address, so search engines never noticed the move. We wrote up how that migration works for anyone considering it.
Going the other way is possible too. What matters is choosing for how the business really operates today, not for a future where someone on staff suddenly starts blogging.
If you are not sure which side of the line you are on, tell us about the site and we will give you a straight answer, including when the answer is to leave it alone.