How to Speed Up WordPress: The 2026 Checklist in the Order That Matters

Search “how to speed up WordPress” and you get the same checklist every time: install a caching plugin, compress your images, minify your CSS, add a CDN. The list isn’t wrong. It’s just out of order, and it skips the step that decides whether any of it works. We optimize WordPress sites for a living, and the single biggest mistake we see is people installing five performance plugins before they’ve measured what’s actually slow. They end up with a slower site and no idea why.

Caching is one piece of the puzzle, and which plugin you install depends entirely on your host. We break that decision down in our guide to the best WordPress caching plugin for 2026.

So this is the checklist in the order that matters, with the reasoning behind each step. Some of it you can do this afternoon. Some of it means an honest conversation about your hosting.

Step 1: measure before you touch anything

You can’t fix what you haven’t measured. Before installing a single plugin, run your site through Google PageSpeed Insights and GTmetrix. PageSpeed gives you the Core Web Vitals that Google actually uses for ranking. GTmetrix gives you a waterfall chart that shows exactly which files are slow to load and in what order.

The one number to find first is your TTFB, time to first byte. That’s how long your server takes to start sending the page, before a single image or stylesheet loads. If your TTFB is over 600ms, your problem is the server, not your front end, and no amount of image compression will fix it. If your TTFB is fine but the page still feels slow, the problem is what loads after: images, scripts, fonts. Knowing which half you’re in saves you from optimizing the wrong thing for a week.

One habit before you start changing things: take a backup. Performance work means editing config, swapping plugins, and clearing caches, and any of that can break a live site. Our guide on how to back up WordPress properly covers the two-minute version. A bad plugin swap can also blank the whole site, the WordPress white screen of death, which is quick to undo once you know where to look.

Step 2: hosting is the ceiling you can’t plugin your way past

Here’s the part most guides won’t say because they’re trying to sell you a plugin instead. If you’re on cheap shared hosting, that is your speed ceiling, and you will hit it no matter how many optimizations you stack. We’ve taken sites from a 1.2 second TTFB down to 200ms by doing nothing but moving them off oversold shared hosting onto a decent host. The plugins came after, and they worked because the foundation was finally solid.

For most small and mid-size sites we recommend Cloudways (on Vultr High Frequency) or a managed host like Kinsta or WP Engine. The difference between $5 shared hosting and $14 Cloudways is not subtle: faster CPUs, more memory, server-level caching, and a modern PHP version by default. Speaking of which, check your PHP version under Tools, Site Health. If you’re still on PHP 7.4 or earlier, upgrading to PHP 8.2 or 8.3 alone can cut your processing time by a third. It’s free and it’s usually one click at your host.

Step 3: caching, the single biggest win for most sites

Once the server is sound, caching is where you get the most speed for the least effort. Without caching, WordPress rebuilds every page from scratch on every visit: it queries the database, runs PHP, assembles the HTML, then sends it. A cache does that work once and serves the saved copy to everyone after, which can cut load time in half on its own.

Our default is WP Rocket. It costs money, and it’s worth it, because it turns on page caching, file optimization, and lazy loading with sane defaults out of the box, where free plugins make you configure all of that by hand. If you’re on a LiteSpeed server, use LiteSpeed Cache instead. It’s free and it’s faster than anything else because it caches at the server level rather than in PHP. We break down the setup in our WP Rocket configuration guide.

One warning that costs people whole afternoons: never run two caching plugins at once. We’ve been called in to fix “broken” sites that were just WP Rocket and W3 Total Cache fighting over the same files. Pick one, delete the other, and clear the cache before you test.

Step 4: images are almost always the heaviest thing on the page

On a typical site we audit, images are 60 to 70 percent of the page weight. A single uncompressed hero photo straight off a phone can be 4MB, and it’ll choke the page on mobile before anything else even loads. Three things fix this, and they compound.

• Compress and convert to WebP or AVIF. A plugin like ShortPixel or Imagify shrinks files by 60 to 80 percent and serves modern formats automatically. A 4MB JPEG becomes a 300KB WebP that looks identical.
• Lazy load below-the-fold images. Images further down the page only load as the visitor scrolls to them, so the first screen paints fast. WordPress does this natively now, and WP Rocket extends it.
• Set explicit width and height. This stops the page from jumping around as images load, which is the main cause of a bad layout shift score.

Do the images before you spend an hour shaving milliseconds off your CSS. The math is on the images.

Step 5: trim the plugins and scripts you forgot you installed

Every active plugin adds code that runs on page load, and some load their scripts and styles on every page even when they’re only used on one. A social-share plugin loading its assets on your checkout page is pure dead weight. When we audit a slow site, deactivating two or three abandoned plugins often does more than a caching tweak.

Go through your plugin list and ask of each one: do I still use this, and does it earn its load? Deactivate anything you don’t, and look hard at page builders and “all-in-one” suites, which are the usual heavyweight offenders. We dug into the real numbers on this in our breakdown of WordPress plugin bloat across 200 sites, and the pattern is consistent: it’s rarely the number of plugins, it’s the two or three badly built ones.

Step 6: clean the database nobody ever cleans

WordPress hoards data. Every time you save a draft it keeps a revision, so a single old post can carry 40 copies of itself. Add expired transients, spam comments, and tables left behind by plugins you deleted years ago, and the database that WordPress queries on every uncached load gets slow and bloated.

WP Rocket includes database cleanup, and WP-Optimize does it for free. Limit post revisions to the last 5 or 10 by adding a line to wp-config.php, clear out expired transients, and empty the spam. Take a backup first, because this deletes data and there’s no undo. Once a quarter is plenty for most sites.

Step 7: fonts and third-party scripts, the hidden tax

This is the layer almost every checklist forgets, and on otherwise-fast sites it’s often what’s left. Each Google Font you load is a separate request that blocks text from showing. Every analytics tag, chat widget, Facebook pixel, and embedded video pulls in scripts from someone else’s server, and you’re at the mercy of how fast that server responds.

Host your fonts locally instead of pulling from Google’s CDN, which removes a third-party connection and is better for privacy too. Limit yourself to two font families and only the weights you actually use. Audit your tags: that chat widget you added for a campaign two years ago might still be loading 200KB of JavaScript on every page. A YouTube embed can add half a megabyte before the visitor even clicks play; a lightweight “click to load” embed fixes that.

What “fast enough” means in 2026: Core Web Vitals

Google measures real-world speed with three Core Web Vitals, and these are the targets to aim for. Hitting them is what “fast” actually means now, not a vanity score in a testing tool.

• LCP (Largest Contentful Paint) under 2.5 seconds. How long until the biggest element, usually your hero image or heading, is visible. Caching, hosting, and image work move this.
• INP (Interaction to Next Paint) under 200ms. How quickly the page responds when someone taps or clicks. This replaced FID in 2024 and is mostly about heavy JavaScript, so trimming scripts helps here.
• CLS (Cumulative Layout Shift) under 0.1. How much the page jumps around while loading. Setting image dimensions and reserving space for ads fixes most of it.

Chase the field data in PageSpeed Insights, the numbers from real visitors, not the lab score. A site can score 100 in the lab and still fail Core Web Vitals for the people actually using it on a mid-range phone over cellular.

A realistic before and after

To show what the order does in practice: a recent client came to us with a WooCommerce store loading in 6.5 seconds, an LCP of 5.1 seconds, and a TTFB of 1.1 seconds on shared hosting. We moved them to Cloudways, set up WP Rocket, compressed 400 product images to WebP, removed two abandoned plugins, and hosted their fonts locally. The result was a 1.6 second load, an LCP of 1.9 seconds, and a TTFB of 210ms. No code rewrite, no redesign, just the steps above in the right order. The hosting move alone accounted for more than half the gain.

Want it done properly, with the numbers to prove it?

You can work through this checklist yourself, and for a lot of sites that’s enough. Where it gets tricky is diagnosing why a site is slow when the obvious fixes are already in place, or speeding up a heavy store without breaking the cart. That’s what our WordPress speed optimization service is for: we measure, fix in priority order, and hand back before-and-after Core Web Vitals so you can see exactly what changed. No guesswork, no plugin soup.

Frequently asked questions

Why is my WordPress site so slow?

Usually one of three things: cheap or oversold hosting with a slow server response, large uncompressed images, or a couple of heavy plugins. Run the site through GTmetrix and check your TTFB. Over 600ms points to hosting; a fast server but slow page points to images and scripts.

What is the single best way to speed up WordPress?

For most sites, page caching gives the biggest gain for the least effort, but only if your hosting is decent to begin with. If you’re on cheap shared hosting, moving to a better host is the bigger win and often the prerequisite for everything else working.

Do I need a caching plugin if my host has caching?

Often not. Managed hosts like Kinsta and WP Engine, and any LiteSpeed server, cache at the server level, which is faster than a PHP plugin. If your host already caches well, adding a second caching plugin can cause conflicts. Use the host’s caching and a plugin only for the extras like file optimization.

Will speeding up my site help SEO?

Yes, indirectly and directly. Core Web Vitals are a Google ranking factor, so passing them helps. The bigger effect is on people: faster pages keep visitors from bouncing and convert better, and those behavior signals matter more than the raw speed score.

How fast should a WordPress site load?

Aim for a largest contentful paint under 2.5 seconds and a full load under 3 seconds on mobile. In testing terms, a TTFB under 400ms and an LCP under 2.5 seconds is a healthy target. Below those, you’re in good shape for both users and Google.

Can too many plugins slow down WordPress?

It’s less about the count and more about the quality. Thirty well-built plugins can run fine while three bloated ones drag a site down. The problem plugins are usually page builders, social-share tools, and anything that loads scripts on every page. Audit what each one costs, not just how many you have.