01The differences
New here? Start at the pillar page for the full picture.
Security. WordPress has a patch cycle, a plugin ecosystem of varying discipline and an admin login pointed at the internet. A static site has none of those things to attack, which is why repeated compromises stop being a topic.
Speed. A WordPress page is generated, then cached, then hopefully served from cache. A static page is read off disk in Australia and arrives in milliseconds. Caching WordPress is real work that needs doing forever.
Cost. Static hosting is a small flat fee like ours. WordPress is hosting, plus a care plan, plus the occasional cleanup you did not budget for.
Editing. WordPress edits in a browser. Static edits by commit, which a coding agent now does from a plain-language request. This is the one place the comparison has genuinely shifted in the last two years.
Features. WordPress runs shops, memberships and ten thousand plugins. Static serves pages and a form endpoint. WordPress wins this column outright and it is not close.
02Side by side
| Static (managed) | WordPress | |
|---|---|---|
| Runs on | Files on our disk | PHP and a database on the hosting |
| Security surface | Your repository and host account | Core, plugins, themes, admin login |
| Page speed | Milliseconds, served from Australia | Depends on caching being maintained |
| Editing | Commits, by you or an agent | Visual editor in the browser |
| Shops, logins, plugins | Not supported | Supported, with the maintenance that carries |
| Annual bill | Flat hosting price | Hosting plus care plan plus surprises |
03The recommendation, stated plainly
04The recommendation, stated plainly
Choose WordPress when the site is an application: commerce, logins, daily browser editing by staff who will never touch a commit, or a workflow a plugin carries. Accept the maintenance as its operating cost, pay a good care plan, stop reading comparison posts.
Choose static when the site is pages people read. Brochure, portfolio, local business, blog. The maintenance stops existing, the speed stops being a project, and the cost stops surprising you.
05Frequently Asked Questions
Do forms work on a static host?
Yes. The form posts to an endpoint and lands in your inbox. LoomWeb ships one. What does not work is anything needing a server-side program to run per visitor.
Which scales better?
Serving files scales almost embarrassingly well. But a small business site was never the scale problem, so pick static for the removed maintenance rather than for scale.
Can I run a blog on static hosting?
Yes. Posts are files, published by push. You lose browser drafting and the SEO plugin; you keep everything readers see.
What about staging sites?
LoomWeb keeps deployment history, and restoring a previous deployment takes seconds. Most people who wanted staging wanted exactly that.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.