How to Speed Up WordPress: 12 Fixes Ranked by Impact, Not by Plugin Count

In this guide

  • First, Measure Before You Fix Anything
  • How to Speed Up WordPress: The 12 Fixes, Ranked by Impact
  • What to Ignore: Popular Advice That Barely Moves the Needle
  • The Free Stack: How to Speed Up WordPress for $0
  • Frequently Asked Questions
  • Verdict: Your Next Three Steps

First, Measure Before You Fix Anything

If you want to know how to speed up WordPress the right way, start with a measurement, not a plugin. Open PageSpeed Insights, enter your homepage URL, and run the test for mobile first. Mobile is where most visitors arrive, so the mobile result is the one that matters. That is the first step in how to speed up WordPress: know the number before you chase it.

Google judges a page with three Core Web Vitals. Largest Contentful Paint (LCP) measures how fast the main content appears: “good” is 2.5 seconds or less. Interaction to Next Paint (INP) measures how quickly the page reacts to taps and clicks: “good” is 200 milliseconds or less. Cumulative Layout Shift (CLS) measures how much the layout jumps while loading: “good” is 0.1 or less.

A page passes only when all three metrics are good for 75% of real visits. PageSpeed Insights shows two kinds of data: lab data from one simulated visit, and field data from real Chrome users over the previous 28 days. The lab score is useful for diagnosis, but the field data is what Google actually uses. That distinction shapes every step of how to speed up WordPress, because a lab score can flatter a slow site. If you are building a new site, our guide to starting a WordPress website shows how to set it up cleanly from day one.

Write down your three numbers before changing anything. Then change one thing at a time and re-test. If you change five things at once, you will never know which one helped. Keep that baseline: it is the only honest way to judge how to speed up WordPress on your own site.

PageSpeed Insights style speed test report with a performance score dial on desktop and mobile

How to Speed Up WordPress: The 12 Fixes, Ranked by Impact

Most speed guides list tips in random order. This one does not. The fixes below are ranked by how much they usually move the Core Web Vitals above, starting with the biggest lever. Work from the top down, and stop when your numbers are good. That ranking is the backbone of how to speed up WordPress without wasting money on the wrong fixes.

Rank Fix Typical impact Effort / cost
1 Faster hosting Highest Medium / from a few dollars a month
2 One good page cache Very high Low / free to $59.95 a year
3 A CDN in front of the site High Low / free plan available
4 Compress and resize images High Low / free tiers available
5 Lightweight theme, fewer plugins High Medium / free
6 Optimise the LCP element High Low / free
7 Delay non-essential JavaScript Medium–high Low / free to $59.95 a year
8 Remove unused CSS Medium Low–medium / free to $59.95 a year
9 Update PHP, WordPress and plugins Medium Low / free
10 Clean the database Low–medium Low / free
11 Optimise fonts Low–medium Low / free
12 Browser caching and monitoring Low Low / free

Fix 1: Move to faster hosting

No plugin can rescue a slow server. Every visit starts with the server building the page, and that waiting time — Time to First Byte — sets the pace for everything downstream, including your LCP score. This is why hosting sits at the top.

If your site runs on the cheapest shared plan you could find, test it honestly. If your host cannot deliver a fast Time to First Byte, no guide on how to speed up WordPress can save the site. Move a copy to a better plan or host, measure both, and keep the faster one. Our comparison of the best WordPress hosting and our guide to the cheapest WordPress hosting explain the differences that matter. When you compare prices, read the renewal price, not the intro price. Our guide to WordPress hosting renewal prices shows how a $3 intro plan can become a $14 renewal. That is the first rule of how to speed up WordPress: fix the server before you buy the plugin.

Fix 2: Use one good page cache — and only one

A page cache saves the finished HTML of a page and hands that copy to the next visitor, so the server skips rebuilding it with PHP and database queries. For most blogs and business sites, this is the single biggest free win after hosting. Any serious plan for how to speed up WordPress starts here. Install exactly one page cache plugin. Two page caches will fight each other and can serve stale or broken pages.

WP Super Cache, maintained by Automattic, is free and does one job well: it writes static HTML files and serves them, and it almost never breaks anything. W3 Total Cache is also free and far more configurable, with a Pro version at $99 a year for one site (checked 19 November 2026). LiteSpeed Cache is free and the best choice on LiteSpeed servers, where its page cache runs at server level rather than inside PHP. On Apache or Nginx hosting, WP Rocket is the simplest paid choice at $59.95 a year for a single site, renewal at the same price (checked 19 November 2026).

One independent comparison on identical hardware measured LCP at 1.1 seconds with WP Rocket, 0.9 with LiteSpeed Cache, 1.3 with tuned W3 Total Cache and 1.6 with WP Super Cache, from 4.2 seconds with no cache — that tester’s numbers, not a promise for your site.

Fix 3: Put a CDN in front of the site

A content delivery network copies your static files — images, CSS, JavaScript — to servers around the world, so a visitor in another country downloads them from nearby instead of from your single origin server. That cuts loading time for distant visitors and takes load off your hosting plan.

Cloudflare offers a free plan that covers this for most small sites, and setup takes about fifteen minutes: point your domain’s nameservers at Cloudflare and turn on caching. A CDN is a standard step in how to speed up WordPress for an international audience.

Fix 4: Compress and resize images

Images are usually the heaviest part of a WordPress page. Upload images at the size they will be displayed, never larger, and compress them before or during upload. A 4,000-pixel photo from a camera has no business in a 800-pixel content column. If you ask how to speed up WordPress and the answer is images, start with size before format.

ShortPixel’s free plan gives 100 credits a month, and each image and thumbnail size costs a credit. Its Unlimited plan is $9.99 a month or $99.90 a year (checked 19 November 2026). Imagify’s free plan covers 20 MB a month, roughly 200 images, and its Growth plan is $4.99 a month billed yearly (checked 19 November 2026). Both convert images to WebP and AVIF, much smaller than JPEG and PNG. Whatever tool you pick, turn on lazy loading for images below the fold, and never lazy-load the hero image — that mistake is covered in fix six. That order — resize, compress, convert — is the practical core of how to speed up WordPress through images.

Fix 5: Switch to a lightweight theme and cut plugin weight

Every plugin and every theme feature adds code that the browser must download and the server must run. The fastest way to learn how to speed up WordPress on an existing site is often subtraction, not addition. List your plugins and ask each one what it earns. A slider showing one banner and three analytics plugins doing the same job are all dead weight.

A lightweight theme such as GeneratePress or Kadence renders far less code than a multipurpose theme packed with page builders and demo widgets. Deactivate plugins one at a time, re-test, and keep only the ones your site visibly needs. Aim for a plugin list you can explain in one sentence each. Every plugin you remove is a small lesson in how to speed up WordPress by subtraction.

Fix 6: Optimise the LCP element

LCP measures the largest visible element — usually the hero image or the main headline block. If that one element loads slowly, your whole LCP score is slow, no matter how good the rest of the page is. Find your LCP element in the PageSpeed Insights report, then give it special treatment. When you learn how to speed up WordPress, the LCP element is the first place to look.

Preload the hero image, serve it in WebP or AVIF, and never lazy-load it — lazy loading above the fold is one of the most common self-inflicted speed wounds in WordPress. This fix costs nothing and takes minutes, which is why it ranks above the JavaScript work below.

WordPress optimisation layers: server, CDN globe and compressed image icons with a rocket

Fix 7: Delay non-essential JavaScript

JavaScript is the usual suspect behind a bad INP score. Chat widgets, social embeds, analytics scripts and video players all compete for the browser’s attention before the visitor can click anything. Delaying scripts is one of the most effective ways to learn how to speed up WordPress for real visitors, not just for lab scores. Waiting until the visitor interacts with the page — often called “delay JavaScript execution” — keeps the page responsive during those first critical seconds.

WP Rocket includes this feature, part of what its $59.95 a year buys (checked 19 November 2026). Delaying the wrong script can break a menu, a form or a checkout.

Fix 8: Remove unused CSS

Most WordPress sites load CSS for features they never display: slider styles with no slider, form styles with no form, page-builder styles everywhere. Removing unused CSS shrinks the files the browser must download before it can paint the page, which helps both LCP and INP. Unused CSS removal is a quiet part of how to speed up WordPress that many guides skip.

WP Rocket and LiteSpeed Cache both offer unused-CSS removal, and W3 Total Cache Pro includes it in its $99-a-year plan (checked 19 November 2026). It can break layouts, so click through your homepage, a blog post and your contact page after turning it on.

Fix 9: Update PHP, WordPress and plugins

Old software is slow software. The current stable release is WordPress 7.1.5, released on 18 November 2026 as a security release, with WordPress 7.2 scheduled for 8 December 2026 (checked 19 November 2026). Running the latest WordPress on a current PHP version is free speed.

WordPress 7.1 needs PHP 7.4 at minimum, and a current PHP 8.x version is the sensible target. Update plugins and themes too, but back up first and use staging if your host offers it. Staying current is the cheapest part of how to speed up WordPress, because updates cost nothing.

Fix 10: Clean the database

WordPress stores every post revision, trashed item, spam comment and expired transient. On a site running for years, that clutter slows the queries behind every uncached page load.

With a good page cache, most visitors never touch the database, which is why this ranks tenth. Limit post revisions, set old spam to auto-delete, and schedule a cleanup once a month.

Fix 11: Optimise fonts

Web fonts are small files with an outsized effect. Each font weight is a separate download, so a page loading four weights of two families fetches eight files before the text can settle — a delay that shows up directly in LCP and CLS.

System fonts load instantly because they are already on the visitor’s device. Fonts are a small but permanent part of how to speed up WordPress. If you need a custom font, use one family and at most two weights, host the files on your own server, and add font-display: swap.

Fix 12: Set browser caching and keep monitoring

Browser caching tells a returning visitor’s browser to reuse files it already downloaded. Most caching plugins set these headers for you, and hosts and CDNs often set them too — check that they are present, as PageSpeed Insights flags missing cache headers.

Then keep measuring. Monitoring closes the loop on how to speed up WordPress: without it, speed quietly regresses. Every new plugin, image and embed can undo your work, so re-test once a month and after any big change.

What to Ignore: Popular Advice That Barely Moves the Needle

Not all speed advice deserves your time. Learning how to speed up WordPress also means learning what to skip. Installing three or four optimisation plugins at once is the classic mistake: they overlap and conflict. One page cache, one image tool, and one code optimiser is the limit.

Minifying HTML is another low-value ritual. It saves a few kilobytes and changes nothing a visitor can feel. The honest version of how to speed up WordPress is boring: measure, fix the biggest thing, measure again. The same goes for chasing a perfect 100 on PageSpeed Insights: a site can score 100 in the lab and still fail Core Web Vitals for real users. Aim for green Core Web Vitals, not a perfect number.

Finally, ignore any guide that promises a fixed percentage improvement from a single plugin: results depend on your hosting, theme and content, so trust your own before-and-after numbers over anyone’s marketing.

The Free Stack: How to Speed Up WordPress for $0

You do not need to spend anything to get most of the way there: ask your host for a current PHP version, install WP Super Cache, turn on Cloudflare’s free plan, and use WordPress’s built-in image tools plus a free image plugin.

That combination covers fixes one, two, three, four, nine and twelve for $0. This free stack is the most practical answer to how to speed up WordPress without spending a dollar. It will not do everything: delayed JavaScript and unused-CSS removal are easier in paid tools, and LiteSpeed Cache only shows its full power on LiteSpeed servers. But a free stack that passes Core Web Vitals beats a $59.95 plugin on a slow host. Spend money only after the free fixes stop moving your numbers.

Frequently Asked Questions

How fast should my WordPress site load?

Aim for the Core Web Vitals “good” thresholds: Largest Contentful Paint in 2.5 seconds or less, Interaction to Next Paint in 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured for 75% of real visits. A page passes only when all three are good. Those are Google’s published targets.

Will a caching plugin alone fix a slow site?

No. A caching plugin hides a slow server from logged-out visitors, but it cannot fix heavy images or a bloated theme. Fix the hosting first, then add the cache, and measure both steps separately so you know what helped. That is the first reality check in how to speed up WordPress: caching hides slowness, it does not cure it.

How many plugins is too many?

There is no magic number: ten well-built plugins can be faster than three badly built ones. Deactivate one, re-test with PageSpeed Insights, and keep only the plugins that earn their place. A plugin you cannot explain is a plugin you should remove. That test-and-remove loop is the everyday practice of how to speed up WordPress on a live site.

Is WP Rocket worth $59.95 a year?

WP Rocket costs $59.95 a year for a single site, and that is also the renewal price (checked 19 November 2026). It combines page caching, delayed JavaScript, unused-CSS removal and preloading with sensible defaults. If your host runs LiteSpeed, the free LiteSpeed Cache does the same job at server level; if your budget is $0, WP Super Cache plus free tools will get you most of the way there.

Do I need a CDN for a small blog?

If your visitors and your host are in the same country, a CDN is optional. If your audience is spread across continents, a CDN is one of the cheapest wins available, and Cloudflare’s free plan covers it.

Verdict: Your Next Three Steps

You now know how to speed up WordPress in the order that matters: hosting first, then one page cache, then a CDN and image compression, and only then the fine-tuning. Do not try all twelve fixes today. Run PageSpeed Insights now, apply fix one and fix two, and re-test. The method is simple, and it is the whole of how to speed up WordPress: measure, fix the biggest lever, measure again. If your Core Web Vitals turn green, stop and write something instead — a fast site with nothing to read is still an empty site.

If you are starting from scratch, our guide to starting a WordPress website walks through the setup that makes all twelve fixes easier: a light theme, a good host, and a clean plugin list from day one. Speed is a habit, not a project.

3 thoughts on “How to Speed Up WordPress: 12 Fixes Ranked by Impact, Not by Plugin Count”

Leave a Comment