Option 1: Do it yourself
Follow the steps in this guide. Free, and typically 30 minutes to a few hours of careful work.
Option 2: Just contact us
Skip every step below. $49/mo and it is sorted, or WhatsApp us right now.
Last updated: August 2026
How slow is "too slow"?
If your main content takes longer than 2.5 seconds to appear (Google's LCP threshold), you're losing visitors and ranking potential. Test it free at PageSpeed Insights, but test the pages customers actually land on, not just your homepage.
One thing to know before you diagnose: your site is faster for you than for anyone else. Your browser has it cached and you're often close to the server. Always test in an incognito window, on mobile data, or with a testing tool, not from your office chair.
The 12 causes, ranked
1. Uncompressed, oversized images. The #1 cause we find. A 4MB photo scaled down by the browser still downloads all 4MB. Fix: compress everything, serve WebP, lazy-load below the fold.
2. Cheap shared hosting past its limits. At $3-8/mo, you share a server with hundreds of sites. When a neighbor gets busy, you get slow. If your time-to-first-byte (TTFB) is regularly above 600ms, hosting is your bottleneck.
3. No caching. Without page caching, your server rebuilds every page from scratch for every visitor. A cache plugin plus server-level caching is the single biggest cheap win on WordPress.
4. Plugin bloat. Every active plugin can add code to every page load. It's not the count that kills you, it's the two or three heavy ones (page builders, bloated sliders, "all-in-one" suites doing twelve jobs).
5. Third-party scripts. Chat widgets, tracking pixels, heatmaps, embedded fonts, video embeds. Each is "just one script" until you have nine and they add two full seconds. Audit quarterly; delete what nobody checks.
6. A bloated database. Post revisions, expired sessions, spam comments, and orphaned tables from deleted plugins accumulate for years. Sites we clean routinely shed 30-60% of database size safely.
7. No CDN for a distributed audience. If your server is in Dallas and your customers are in Vancouver, physics adds delay. A CDN puts copies close to everyone. If your audience is one metro area, this matters far less.
8. Old PHP version. PHP 8.x is dramatically faster than 7.x. Many hosts leave old sites on old versions forever unless someone asks. Check yours, it's a one-click change (test on staging first).
9. Render-blocking CSS/JS. Code that must load before anything displays. The fix (defer, async, critical CSS) is technical but standard.
10. Unoptimized fonts. Loading six font weights from two families delays every headline on the page. Two weights, preloaded, is almost always enough.
11. Redirect chains. http → https → www → final page: three round trips before anything loads. Common after migrations that nobody cleaned up.
12. Actual malware. Crypto-mining scripts and spam injections consume server resources. If your site got slow suddenly with no changes on your end, scan before you optimize.
What order should I fix things in?
Images → caching → PHP version → plugin audit → database cleanup. That sequence delivers most of the gain for the least risk. Hosting upgrades and CDN come next only if TTFB is still poor. Fine-tuning render-blocking resources is the last 10%, not the first move.
When it's worth handing off
Speed work has a trap: half the "optimizations" on the internet break sites (aggressive minification and page builders are a famously bad combination). If you'd rather not gamble the live site, this whole list is standard work inside our Growth plan, with before/after numbers in your monthly report so you can see the change, not take our word for it.
FAQ
Will a speed plugin alone fix my slow site? It helps with caching (cause #3) but does nothing for oversized images, bad hosting, or database bloat. Plugins are one tool, not the fix.
Does website speed really affect Google rankings? Yes, Core Web Vitals are a confirmed ranking signal, and speed also affects rankings indirectly: slow pages get more back-button abandonment, which suppresses performance across channels, including your paid ads' quality scores.
How fast should my site load in 2026? Aim for LCP under 2.5s on mobile, and under 2.0s if you're in e-commerce. Sub-1-second is achievable on well-maintained WordPress and worth pursuing for stores.
My site was fast last year and slowed gradually, why? That's speed decay: images accumulate, plugins pile up, the database grows, and nobody was assigned to watch it. It's the default fate of unmaintained sites, and the reason speed is a monthly job, not a one-time project.
You do not have to do any of this yourself
Skip the steps above. Our engineers handle security, updates, speed, backups and fixes for you, with a 12-minute average response and a 99.99% uptime target.