WordPress has a reputation for being slow. It isn’t — but the way most WordPress sites are built is. Every week I audit sites that take 6+ seconds to load, and the causes are almost always the same five things. Here they are, with the fixes, in the order I apply them.
The five usual suspects
- 1. A bloated multipurpose theme. Themes that can “do anything” load the code for everything — 2 MB of CSS/JS for a page that uses 5% of it. Fix: a lean custom theme that ships only what the design needs.
- 2. Unoptimized images. 4000-pixel photos squeezed into 400-pixel slots. Fix: WebP format, correct dimensions, lazy loading below the fold.
- 3. Plugin stacking. Thirty plugins, each adding scripts to every page. Fix: audit ruthlessly; most sites need fewer than ten.
- 4. No caching. Every visit rebuilds the page from scratch. Fix: page caching turns dynamic pages into instant static files.
- 5. Bottom-tier hosting. A US$2/month server answers in 1.5 seconds before your site even starts. Fix: decent hosting is US$10–30/month and worth every cent.
Why speed is money, not vanity
Google uses Core Web Vitals in ranking, and paid traffic punishes slowness even harder: if your ad click takes 5 seconds to show a page, you paid for a bounce. Every second of load time measurably cuts conversions — this is the most expensive invisible problem a business site can have.
How my builds stay fast
Speed isn’t a plugin you add at the end; it’s a build standard. My sites use hand-built block themes (no multipurpose bloat), self-hosted optimized fonts, WebP images and caching — which is how the sites in my portfolio, including this one, score 90+ on Google PageSpeed mobile. Speed optimization of existing sites is also a service I offer on its own.
FAQ
What is a good PageSpeed score?
90+ (green) on mobile is the standard I deliver. 50–89 means real work to do; under 50 means the site is actively losing visitors.
Can an existing slow site be fixed without a rebuild?
Often yes — images, caching and plugin cleanup can double a score. If the theme itself is the bottleneck, a rebuild pays for itself.
Do caching plugins alone solve slowness?
No. Caching hides server slowness but can’t fix 2 MB of render-blocking theme code or oversized images. It’s one layer of five.