We’ve taken over dozens of slow WordPress sites. Almost every time, the owner had already installed a caching plugin, an image optimizer, and something promising “one-click speed.” The site was still slow.

That’s because caching is the last step, not the first. Caching hides a slow site behind a saved copy — it doesn’t make the site fast. When the cache misses, or a logged-in user visits, or WooCommerce bypasses it on the cart page, you’re back to the real speed underneath.

Here’s what we actually check, in the order we check it.

First: measure properly

Before changing anything, get a baseline you can trust. Run your site through PageSpeed Insights and — more importantly — WebPageTest with a real device profile and a location near your actual audience.

Pay attention to these three numbers, not the overall score:

• TTFB (Time To First Byte) — how long the server takes to start responding. Above 600ms means a server or PHP problem.
• LCP (Largest Contentful Paint) — when the main content appears. Google wants this under 2.5 seconds.
• CLS (Cumulative Layout Shift) — how much the page jumps while loading. Should be under 0.1.

Each of those points at a different category of problem. A bad TTFB with a good LCP is a hosting issue. A good TTFB with a bad LCP is a front-end issue. Knowing which one you have saves you from fixing the wrong thing.

Fix 1: Your hosting is probably the problem

This is the uncomfortable one, because it costs money. But if your TTFB is over 800ms on a cached page, no plugin will save you.

Cheap shared hosting puts hundreds of sites on one server. When your neighbour gets traffic, you get slow. You’re also usually capped on PHP workers — meaning only two or three requests can be processed simultaneously, and everything else queues.

What to check:

• PHP version. PHP 8.3 is roughly three times faster than PHP 7.4 on typical WordPress workloads. If you’re below 8.1, upgrade — but test on staging first, since old plugins can break.
• OPcache enabled. This caches compiled PHP so it isn’t recompiled on every request. Most decent hosts have it on; some budget hosts don’t.
• Server location. If your clients are in the US and your server is in Asia, you’re paying 200ms in latency before anything else happens.

Moving from budget shared hosting to a decent managed host or a small VPS is frequently the single biggest speed improvement available, and it takes an afternoon.

Fix 2: Audit your plugins ruthlessly

Plugin count matters less than plugin quality. Ten well-built plugins can be faster than three bloated ones. But most slow sites we inherit have the same problems:

• A page builder loading its entire CSS and JS framework on every page, including pages that don’t use it
• A slider plugin loading jQuery UI, a carousel library, and three stylesheets — for a slider that appears on the homepage only
• Two plugins doing the same job, both active
• Social sharing plugins loading scripts from four different third-party domains
• A “related posts” plugin running an unindexed database query on every single page load

The diagnostic: install Query Monitor temporarily. It shows you exactly which plugin is running slow queries, how many queries each page fires, and how long PHP spent on each hook. It turns guesswork into a list.

Our rule of thumb: if a plugin adds more than 100ms to page generation and isn’t essential to revenue, it goes.

Fix 3: Images are usually the largest problem you can fix yourself

On most sites we audit, images account for 60–80% of total page weight. Three things to fix:

Serve modern formats. WebP files are typically 25–35% smaller than JPEG at the same visual quality. AVIF is smaller still. Any decent image optimization plugin will generate these and serve them with a fallback.

Stop serving oversized images. A 4000px-wide photo displayed in a 600px container wastes enormous bandwidth. WordPress generates multiple sizes automatically — make sure your theme is actually using srcset so the browser picks the right one.

Lazy-load below the fold, but never above it. WordPress lazy-loads images by default now. That’s good for images further down the page and actively harmful for your hero image, because it delays your LCP. Add loading="eager" and fetchpriority="high" to the main above-the-fold image.

Fix 4: Clean up your database

WordPress databases accumulate junk. On a site that’s been running a few years, it’s normal to find:

• Thousands of post revisions — every draft save creates one, forever
• Expired transients that were never cleaned up
• Orphaned postmeta rows from plugins you deleted years ago
• Spam comments sitting in the queue

The wp_options table deserves special attention. WordPress loads every row marked autoload on every single request. Some plugins dump megabytes of cached data in there with autoload enabled. We’ve seen sites where a single autoloaded option was adding 300ms to every page load.

Check it with this query:

SELECT option_name, LENGTH(option_value) AS size
FROM wp_options
WHERE autoload = 'yes'
ORDER BY size DESC
LIMIT 20;

Anything over 100KB in that list is worth investigating. Back up before you touch anything.

Also limit revisions going forward by adding this to wp-config.php:

define('WP_POST_REVISIONS', 5);

Fix 5: Eliminate render-blocking resources

When a browser hits a CSS file or a synchronous script in the <head>, it stops rendering until that file downloads and parses. Stack up eight of those and you’ve added seconds of blank screen.

What helps:

• Defer non-critical JavaScript. Almost nothing needs to run before the page paints.
• Inline critical CSS — the styles needed for above-the-fold content — and load the rest asynchronously.
• Dequeue assets where they aren’t used. If Contact Form 7 only appears on your contact page, don’t load its CSS on all forty other pages.
• Self-host your fonts. Google Fonts adds a DNS lookup, a TLS handshake, and a round trip to a third-party domain. Self-hosted WOFF2 with font-display: swap is faster and better for privacy compliance.

Fix 6: Now add caching

With the foundation fixed, caching multiplies your gains instead of masking problems.

You want three layers:

• Page caching — serves a pre-built HTML file instead of running PHP and MySQL. This is the big one.
• Object caching via Redis or Memcached — caches database query results between requests. Matters most on WooCommerce and membership sites where page caching gets bypassed.
• Browser caching — correct Cache-Control headers so returning visitors don’t re-download your CSS, JS, and images.

If your host runs LiteSpeed, use LiteSpeed Cache — it hooks into the server itself rather than doing everything in PHP. Otherwise WP Rocket (paid) or FlyingPress are solid. Whatever you choose, run only one caching plugin. Two will fight each other and cause bizarre bugs.

Fix 7: Put a CDN in front of it

A CDN copies your static files to servers around the world so a visitor in London downloads from London, not from your server in Karachi.

Cloudflare’s free tier covers this for most small business sites and adds DDoS protection and free SSL. Set it up, but be deliberate about the optimization toggles — Rocket Loader and Auto Minify occasionally break themes. Enable them one at a time and test after each.

A realistic order of operations

If you do nothing else, do these in this order:

1. Measure your baseline — TTFB, LCP, CLS
2. Upgrade PHP to 8.1 or higher
3. Install Query Monitor and identify your worst plugins
4. Remove or replace them
5. Fix your images — WebP, correct sizes, eager-load the hero
6. Clean the database and check autoloaded options
7. Defer JavaScript and self-host fonts
8. Add one caching plugin
9. Add a CDN
10. Measure again and compare

Steps 2 through 6 are where the real wins are. Most people start at step 8, which is why their sites are still slow.

When it’s worth calling someone

If your site is a hobby blog, work through this list yourself over a weekend. It’s genuinely doable.

If your site takes orders, books appointments, or generates leads, the calculation is different. A one-second improvement in load time measurably increases conversion rates. If your site does $10,000 a month, a 10% conversion lift pays for a professional audit many times over in the first month.

Either way, don’t buy the plugin that promises to fix everything with one click. That plugin doesn’t exist, and the sites that install it are the ones we get called to rescue six months later.