How to Fix a Slow WordPress Site: 15 Fixes Ranked by Impact

Your WordPress site takes five seconds to load, visitors bounce before your content even renders, and every “speed up WordPress” guide throws forty tips at you in no particular order. That’s the real problem: not knowing what to fix, but knowing what to fix first.

This guide ranks 15 fixes by impact — the changes that typically move load times by whole seconds sit at the top, and the polish that shaves milliseconds sits at the bottom. It’s written for site owners who can use the WordPress dashboard and their hosting control panel, no developer required for most steps.

By the end, you’ll know how to measure your baseline, work through the fixes in order of payoff, and recognize when the honest answer is that your hosting — not your plugins — is the bottleneck.

Table of Contents

• Before You Start: Measure Your Baseline
• Tier 1: High-Impact Fixes (1–5)
• Tier 2: Medium-Impact Fixes (6–10)
• Tier 3: Fine-Tuning (11–15)
• Troubleshooting: When Fixes Don’t Stick
• FAQ
• Conclusion
• Sources

Before You Start: Measure Your Baseline

Never optimize blind. Do this first:

1. Run your homepage through GTmetrix or PageSpeed Insights and save the report. Note two numbers: TTFB (time to first byte — your server’s responsiveness) and LCP (largest contentful paint — when the main content appears).
2. Test one heavy interior page (a long blog post or a shop category page), not just the homepage.
3. Re-test after each tier below, not after every single fix — you want to see which tier actually moved the needle.

A rough rule of thumb: if TTFB is consistently high even on a cached, mostly-static page, your problem is server-side (hosting, PHP, caching). If TTFB is fine but LCP is slow, your problem is front-end (images, scripts, theme).

Tier 1: High-Impact Fixes (1–5)

1. Enable full-page caching

Without caching, WordPress rebuilds every page from PHP and database queries for every visitor. Kinsta’s own testing found that enabling caching reduced TTFB by roughly 90%, bringing it under 35 ms in their benchmarks [2]. This is consistently the single biggest win available.

• On managed hosting (Kinsta, Cloudways and similar): server-level caching is built in — verify it’s turned on in your hosting dashboard.
• On shared hosting: install a caching plugin such as WP-Optimize, which provides static page caching, Gzip compression, and browser caching in its free version [3].

2. Upgrade your PHP version

Each major PHP release is meaningfully faster for WordPress. Kinsta’s benchmarks measured WordPress running 47.10% faster on PHP 8.1 than on PHP 8.0 [1]. This is usually a two-minute change:

1. Check your current version under Tools → Site Health → Info → Server in wp-admin.
2. In your hosting control panel, switch to the newest PHP version your host offers.
3. Click through your site immediately after — a rare old plugin can break on newer PHP. If something errors, switch back and update or replace that plugin first.

3. Fix (or leave) your hosting

Cheap shared hosting stacks many sites on one server; when a neighbor gets a traffic spike, your site pays for it [4]. If you completed fixes 1–2 and TTFB is still slow, the server itself is the bottleneck — no plugin can fix that.

Managed WordPress hosts handle server-level caching, current PHP, and CDN integration out of the box [1][2]. This is the “one fix that replaces five plugins” option, and it’s where most stubborn slow sites actually get solved.

4. Compress and convert your images

On the median WordPress page, images account for roughly 46% of total page weight — about 1,117 KB [1]. Fixes:

1. Install an image-optimization plugin (WP-Optimize includes compression and WebP conversion [3]; Smush and ShortPixel are common alternatives).
2. Bulk-compress your existing media library.
3. Enable WebP serving — the plugin serves WebP to modern browsers and falls back to JPEG/PNG for older ones.
4. Stop uploading camera-original files; resize to the largest dimension your theme actually displays.

5. Audit and cut your plugins

One badly coded plugin can hurt more than ten lean ones [4]. Do a ruthless audit:

1. Deactivate anything you haven’t used in 90 days, test the site, then delete.
2. Watch for known heavy categories: broken-link checkers, “related posts” plugins that scan the database, and always-on live-traffic security dashboards [4].
3. Use Query Monitor (free plugin) to see which plugins generate slow database queries [1].

Tier 2: Medium-Impact Fixes (6–10)

6. Clean your database

Post revisions, spam comments, trashed posts, expired transients, and leftovers from deleted plugins accumulate for years [3][4]:

1. Back up first (non-negotiable).
2. Run WP-Optimize’s database cleanup: remove old revisions (keeping a handful is fine), spam/trashed comments, and expired transients, then optimize the tables [3].
3. Schedule it monthly.

7. Add a CDN

A CDN serves your static files from a location near each visitor instead of from one origin server [1]. Many managed hosts bundle one — Kinsta, for instance, reports that server-level caching alone cut TTFB by roughly 90% in its own tests, bringing it under 35 ms [2], and pairs that with edge caching / CDN delivery for static assets. On other hosts, Cloudflare’s free tier is the standard starting point.

8. Reduce external scripts and embeds

Ad networks, social feeds, tracking pixels, and chat widgets each add third-party requests you don’t control [4]. Remove the ones that aren’t earning their keep, and lazy-load video embeds so a YouTube iframe doesn’t load until someone scrolls to it.

9. Switch to a lightweight theme

Page-builder-heavy themes ship large CSS/JS bundles on every page. If your theme predates 2020 or loads sliders you don’t use, moving to a performance-focused theme (GeneratePress, Astra, Kadence are commonly cited examples) removes a whole layer of bloat [4].

10. Enable lazy loading everywhere

WordPress lazy-loads images natively since version 5.5, but verify your theme isn’t overriding it, and extend the behavior to iframes and videos via your optimization plugin [4].

Tier 3: Fine-Tuning (11–15)

11. Host fonts locally

Google Fonts calls add external DNS lookups and requests; hosting the font files on your own server removes them [4].

12. Minify and combine CSS/JS

Your caching plugin likely offers minification — enable it, then hard-refresh and check the layout, since aggressive combining occasionally breaks styling.

13. Defer non-critical JavaScript

Delay scripts that aren’t needed for first paint (analytics, marketing tags) so they load after the content renders [4].

14. Keep everything updated

Outdated themes and plugins carry both performance and security debt [4]. Update on a schedule, after a backup.

15. Prune what loads per page

Tools like Asset Cleanup let you stop a contact-form plugin’s scripts from loading on every page when only one page uses them [1].

Quick-reference: fix vs. effort vs. impact

#	Fix	Effort	Typical impact
1	Full-page caching	Low	Very high (TTFB)
2	PHP upgrade	Low	High
3	Better hosting	Medium	Very high
4	Image compression/WebP	Low	High (LCP)
5	Plugin audit	Medium	High
6	Database cleanup	Low	Medium
7	CDN	Low	Medium–high
8	Cut external scripts	Medium	Medium
9	Lightweight theme	High	Medium–high
10	Lazy loading	Low	Medium
11–15	Fine-tuning items	Low	Small each, real together

Troubleshooting: When Fixes Don’t Stick

These are user-reported patterns from forums and independent write-ups — label your own diagnosis accordingly:

• “I enabled caching and nothing changed.” Users report testing while logged in as admin — most caching setups bypass the cache for logged-in users. Test in a private/incognito window.
• “My site broke after the PHP upgrade.” Users report a single abandoned plugin as the usual culprit. Roll back the PHP version, find the incompatible plugin by deactivating in batches, replace it, then upgrade again.
• “Minification broke my layout.” A known trade-off: users report that combining CSS/JS can break page-builder themes. Turn off the combine option but keep minify, or exclude the offending file.
• “Scores improved but the site still feels slow.” Users report chasing lab scores while real-world TTFB stays high — usually a hosting bottleneck (see fix 3) that front-end tweaks can’t paper over.
• “Two caching plugins made things worse.” Stacked caching layers can serve stale or conflicting pages. Run exactly one page-cache layer; if your host caches at server level, don’t add a page-caching plugin on top.

FAQ

How fast should a WordPress site load? Aim for LCP under 2.5 seconds on mobile — that’s the threshold Google’s Core Web Vitals treats as “good.” Uncached TTFB varies by host, but on a cached page it should be a few hundred milliseconds or less.

Do I need a developer to fix a slow WordPress site? For fixes 1–2, 4–8, and 10–14: no, they’re dashboard-level changes. A theme rebuild (fix 9) or custom-code diagnosis is where a developer earns their fee.

Will deleting plugins break my site? Deactivating is reversible — deactivate, test, and only then delete. Always keep a fresh backup before bulk changes.

Is a caching plugin necessary on managed hosting? Usually not for page caching — hosts like Kinsta cache at server level [2]. You’d still use a plugin for image optimization or database cleanup.

Why is my WordPress admin slow, not just the front end? The front-end fixes (caching, CDN) don’t apply to wp-admin. A slow dashboard points to heavy plugins running background tasks, an overloaded database, or underpowered hosting — fixes 3, 5, and 6.

Conclusion

Work the list top-down: caching, PHP, images, and a plugin audit will resolve the majority of slow WordPress sites in an afternoon. But if you finish Tier 1 and your TTFB is still poor, stop stacking plugins — the server is the problem. That’s the point where moving to managed WordPress hosting with built-in server-level caching, current PHP, and edge caching pays for itself in both speed and the hours you stop spending on this.

👉 Check out managed WordPress hosting here and compare plans against what you’re paying now — then re-run that GTmetrix test and enjoy the difference.