The slowest client site we've taken over this year took 14 seconds to load on a phone. Fourteen. The average visitor gives you about three before they hit back and try the next result — which means that business was paying for a website most mobile visitors never actually saw.
Here's the thing: that site wasn't broken in some exotic way. It had the same four problems almost every slow WordPress site has, because WordPress sites accumulate them the same way garages accumulate boxes.
The four things actually slowing you down
1. Plugin pile-up
Every plugin was installed to solve one problem, and each one loads its own scripts and styles on every page — whether that page needs them or not. Twenty plugins deep, your homepage is hauling code for a contact form, a slider you deleted in 2023, and three SEO tools that argue with each other. The site doesn't feel broken. It feels heavy. That's the pile.
2. A theme built for the demo, not for you
Commercial themes ship with every feature switched on so they look impressive in the marketplace preview. You use maybe a tenth of it; your visitors download all of it, on every page, forever.
3. Hosting that was cheap for a reason
Budget shared hosting means your site waits in line behind hundreds of strangers' sites on the same server. The first second of your load time is often gone before a single pixel of *your* site is involved.
4. Images nobody ever optimized
A 4MB photo straight off a phone, displayed at 400 pixels wide, is a few hundred kilobytes of picture wrapped in several megabytes of waste. Multiply by every image on the page.
Diagnose yours in five minutes
Run your site through Google's free PageSpeed Insights tool and look at exactly one number first: LCP (Largest Contentful Paint) on mobile — how long until the main content is visible.
- Under 2.5 seconds: you're fine. Go build your business.
- 2.5–5 seconds: fixable problems, worth fixing — this range usually responds well to image optimization, plugin cleanup, and better hosting.
- Over 5 seconds: the platform is probably the ceiling, not the settings.
Sites we take over typically start between 8 and 14 seconds. That's not a tune-up situation.
The honest fix-or-rebuild rule
Fix WordPress when the problem is isolated — one bad plugin, slow hosting, unoptimized images, a hacked file. That's real, bounded work with a real payoff, and it's often all a site needs.
Stop patching when the platform is the ceiling. If your mobile load time is over 5 seconds, updates keep breaking things, and you're paying monthly for a stack of plugins that fight each other, another year of patching usually costs more than a rebuild — you just pay it in installments, plus the invisible tax of every visitor who left.
We build replacements on Next.js — the same framework our [web builds →](/services/web-development) use to score 90+ on all four of Google's Lighthouse metrics. But the framework isn't the scary part for most owners. This is:
"Won't I lose my Google rankings if I rebuild?"
Only if it's done carelessly — and this is where most rebuilds go wrong, because the rankings live on URLs, and a rebuild that changes URLs without a map orphans years of earned search equity.
Done right, nothing is lost. On our most recent migration we inventoried all 270 URLs Google knew about from Search Console before cutover — rebuilt the pages that earn traffic, permanently redirected everything else, and verified every single one resolved before DNS moved. Zero rankings lost, and the 14-second load time I opened with became a thing of the past. That site now earns more search visibility than the old one ever did — the full method lives on our [WordPress repair & migration page →](/services/wordpress).
Where to start
If your WordPress site feels slow, don't guess. Run PageSpeed Insights, read your mobile LCP, and you'll know which situation you're in within five minutes.
And if you want a second opinion, our [free WordPress assessment →](/services/wordpress) covers speed, security, and SEO health, and ends with an honest read: fix it, or stop patching — including the case where the answer is "your site's fine, spend the money elsewhere." We'd rather tell you that than sell you a rebuild you don't need. [Get in touch →](/contact) and we'll take a look.
