How to speed up a slow WordPress site (without a single plugin)
WordPress out of the box is slow for boring, fixable reasons. Here is how to make it genuinely fast — by moving the work to the edge instead of stacking yet more plugins on top.
WordPress rebuilds each page from PHP and the database on every visit, which is the slowness. The fix isn't another caching plugin fighting your other plugins — it's full-page caching at the edge, so most visitors get a static, instant copy while logged-in users and carts still work normally.
WordPress runs a huge share of the web, and a huge share of slow websites — which isn't a coincidence. It's not that WordPress is bad; it's that, by default, it does a surprising amount of work to show someone a page that hasn't changed in three weeks.
Why it's slow in the first place
For every visit, WordPress wakes up PHP, runs your theme and plugins, makes a pile of database queries, assembles the HTML, and only then sends it. Do that for one visitor and it's fine. Do it for everyone, all at once, on shared hosting, and you get the spinning tab of doom.
The fix: cache the whole page at the edge
If a page looks the same for every logged-out visitor, there's no reason to rebuild it each time. Full-page caching saves the finished HTML at the edge and serves that copy directly. PHP and the database get a day off, and your visitors get a page in milliseconds.
The classic objection is "but my site has dynamic bits". It does — and that's handled by bypassing the cache only where it's actually needed.
Cache these (same for everyone)
- Posts and pages
- The homepage and archives
- Category and tag listings
Bypass these (personal)
- wp-admin and logged-in sessions
- Carts and checkout
- Anything behind a login
The other two wins
Optimize images at the edge
Convert to WebP or AVIF and resize to the displayed size on the fly. Most WordPress media libraries are full of oversized photos.
Minify and compress
Strip whitespace from CSS and JS and compress everything with Brotli. Small, automatic, free speed.
Serve from nearby
With a CDN, your visitor in another country loads from a local edge instead of your single host.
More caching plugins is not the answer when caching plugins are already the problem. Stacking three of them tends to produce conflicts, not speed. Moving the cache off the server and onto the edge sidesteps the whole mess.
WordPress is slow because it rebuilds unchanged pages on every visit. Cache the whole page at the edge, bypass the cache for logins and carts, optimize images and compress assets — and a sluggish site turns fast without you installing a single new plugin.
Mads has worked in IT — mostly hosting — since he was 16. He took an early stake in a SaaS company and helped grow it through to its acquisition by Visma, has built and run data-center networks, and served as CTO of a Danish data center. He started NordicCDN to make fast, secure infrastructure simple to use.
