A renovation contractor came to us with a WordPress backup that ran 98 megabytes. The static site we built to replace it, same pages, same photos, same quote form, came in at 3.2 megabytes. That's not a rounding error and it's not a one-off. It's what happens once you strip out everything WordPress carries that a five page business site never actually uses.
We rebuild WordPress sites as static sites often enough that people ask us why, usually right after their site got hacked or their host bill jumped for no obvious reason. Here's the honest version, no scare tactics, including the cases where WordPress is still the right call.
What "static" actually means
WordPress is software. It runs on your server every time someone loads a page: it queries a database, loads a theme, runs however many plugins you've installed, and assembles the page on the fly. That's what makes the built-in editor possible, and it's also what makes WordPress slow, hackable, and expensive to keep patched.
A static site skips all of that. We build the pages once as plain HTML, CSS, and a little JavaScript, and the server just hands those files to a visitor's browser with nothing to compute. There's no database to lose, no login page for someone to try to break into, no plugin that can go rogue on an update. It's the same reason a photocopy of a finished document opens faster than a live spreadsheet still doing math in the background.
The two side by side
| Factor | WordPress | Static site |
|---|---|---|
| Typical page load | 2 to 5 seconds with a plugin-heavy theme | Under 1 second, often a few hundred milliseconds |
| Security updates needed | Core, theme, and every plugin, monthly at minimum | None. There's no software running to patch |
| Hosting cost | Managed WordPress hosting, database backups, often $20 to $50+/month | Basic static hosting, often $5 to $10/month |
| Who can edit content | Anyone, through the WordPress admin, no code needed | Requires a developer for most changes (some setups add a light content layer) |
| Plugin risk | A single abandoned plugin can open the whole site to attack | Not applicable, there's nothing to install |
| Best fit | Stores with constantly changing inventory, blogs with many non-technical authors | Brochure sites, service businesses, most five to twenty page sites |
Where we actually see WordPress break
Three patterns show up over and over on the sites we take over. Plugin conflicts top the list: someone installs a new booking plugin, it fights with the SEO plugin, and half the site's forms stop submitting until somebody notices. Nobody notices for two weeks, usually.
Second is the slow, quiet hack. WordPress runs a huge share of the web, which makes it a huge target, and an unpatched plugin from eighteen months ago is an open door. We've picked up sites redirecting visitors to pharmacy spam or loaded with hidden links, and the owner had no idea until Google flagged the site or a customer called to ask why the page looked wrong.
Third is the hosting bill that creeps up. Managed WordPress hosting exists because WordPress needs babysitting: automated backups, malware scanning, a staging environment so updates don't break production. All of that is real infrastructure, and real infrastructure costs money every month whether or not anyone touches the site that week.
Real migrations, real numbers
We don't publish client counts, but we can show our own work. Farhat-McGee Removals came off a 136 megabyte WordPress backup onto a 7.3 megabyte static site, about a 95 percent size drop, with the same funeral transfer service pages and price list intact. Southdale Barbershop's live disk usage dropped to around 28 megabytes after its rebuild, down from a full WordPress install eating most of its hosting quota. Low Price Auto Glass went further: we replaced their WordPress site with a 35-page static Astro build across three branch cities, and their DataForSEO domain rank climbed from 25 to 84 within about a month of the ranking cluster loading properly for the first time.
None of that is magic. Search engines and browsers both reward pages that load fast and don't choke on a database query, so a lighter site tends to rank and convert better once the technical debt is gone. We'd be lying if we said file size alone did that, content and links still matter, but a fast static rebuild removes a real handicap.
Check your own site today, no developer needed
Go to Google's PageSpeed Insights, paste in your homepage URL, and hit "Analyze." If your mobile score is under 50, that's usually a WordPress plugin problem, not a content problem. While you're at it, log into your WordPress admin, go to Plugins > Installed Plugins, and count how many say "not tested with your version of WordPress." Anything past a handful of tested-recently plugins is a site quietly building risk.
If your PageSpeed score is fine and your plugin list is short and current, you probably don't need to move anywhere. This isn't a pitch to rebuild everything; it's a pitch to actually look.
When WordPress is still the right choice
We keep some clients on WordPress on purpose. RK Forever Jewellery and Furniio both run WooCommerce stores with catalogues that change weekly: new products, new prices, new stock levels, managed by staff with no coding background. Static doesn't do that well. If your business needs several non-technical people updating inventory or content constantly, WordPress (kept patched and properly hosted) is still the better tool, and we'll tell a client that even when a rebuild would be more billable work for us.
The line is simple: if your site is mostly "here's who we are and how to reach us" with occasional updates, static wins on speed, security, and cost. If your site is a living catalogue that non-developers touch every day, keep WordPress and pay for proper hosting and maintenance instead.
If you're not sure which camp you're in, that's a five-minute conversation, not a sales pitch. We can look at your current site and tell you honestly whether a WordPress to static migration would help or whether you'd just be paying to move sideways. Our case studies show what the finished migrations look like, disk size, load time, and rankings included.
Frequently asked questions
Will I lose my Google rankings if I move off WordPress?
No, not if the migration is done right. We carry over every URL, every meta title, every redirect, and the schema markup. Rankings usually hold steady or improve within a few weeks, because the new site loads faster.
How long does a WordPress to static migration take?
For a typical five to fifteen page business site, one to three weeks. Bigger sites with fifty-plus pages, like a multi-location business, take longer because every page needs a manual pass, not a bulk export.
Can I still update my own content on a static site?
Small text and price changes, yes, usually through us or a lightweight content file we set up for you. Frequent self-serve editing across a large site is the one job static genuinely does worse than WordPress.
Is WooCommerce different from regular WordPress?
Same core software, extra plugin. WooCommerce adds a product catalogue and checkout on top of WordPress, which means it inherits every WordPress maintenance headache plus payment security on top. It's a legitimate choice for stores with real inventory turnover, not a shortcut.
What happens to my WordPress site if I just leave it alone?
It gets slower and riskier over time, even with zero changes, because the software underneath it keeps aging and new vulnerabilities keep getting found in old plugin versions. Doing nothing is a decision too, it just isn't a neutral one.