# How to Speed Up a WordPress Site: 10 Steps That Actually Work

> Speed up your WordPress site step by step: measure Core Web Vitals, turn on caching, fix images, audit plugins, cut third-party scripts and keep it fast.

URL: https://www.webdesigncolumn.com/how-to-speed-up-wordpress-site/  
Author: WebDesignColumn Editorial Team  
Published: 2026-11-19  
Updated: 2026-11-18  
Category: WordPress

---

A slow WordPress site usually isn’t slow for one big reason. It’s slow because of ten small ones: oversized images, a plugin that loads scripts on every page, fonts pulled from three places, no caching. The good news is that most of them take minutes to fix, and you don’t need to be a developer to do it.

This tutorial goes through the fixes in the order we’d do them: measure first, then the changes that make the biggest difference for the least effort.

## Key takeaways

- Measure with PageSpeed Insights before changing anything, and note your Core Web Vitals so you can compare later.
- The biggest wins are usually page caching, smaller images and fewer third-party scripts.
- Change one thing at a time and re-test, so you know what helped and what broke.

## Step 1: Measure where you are

Run your home page and your most visited page through [PageSpeed Insights](https://pagespeed.web.dev/). Look at the top section first: that’s real data from Chrome users, and it’s what Google uses. Google’s Core Web Vitals thresholds for a “good” result are:

- **Largest Contentful Paint (LCP):** 2.5 seconds or less. How quickly the main content appears.
- **Interaction to Next Paint (INP):** 200 milliseconds or less. How quickly the page reacts when someone taps or clicks.
- **Cumulative Layout Shift (CLS):** 0.1 or less. How much the page jumps around while loading.

Write the numbers down, or take a screenshot. The lab score below them (the 0 to 100 number) is useful for spotting problems, but don’t chase a perfect 100.

## Step 2: Check your hosting and PHP version

No plugin can fix a server that’s slow to respond. In PageSpeed Insights, look for “Reduce initial server response time”. If it shows up on every test, the problem is the hosting plan, not your site.

While you’re in your hosting panel, check the PHP version. Newer versions are faster and still get security fixes; WordPress shows a warning under **Tools → Site Health** if yours is out of date.

## Step 3: Turn on page caching

Without caching, WordPress builds every page from scratch for every visitor. A caching plugin saves the finished page and serves that copy instead, which is often the single biggest speed gain.

- If your host runs LiteSpeed (many shared hosts do), use the free **LiteSpeed Cache** plugin; it works with the server’s own cache.
- Many managed WordPress hosts already cache pages at the server level. Check their documentation before adding a plugin.
- Use **one** caching plugin. Two caching plugins fight each other and can break the site.

After turning caching on, submit every form on the site and, if you sell online, add something to the cart. Caching occasionally breaks things that need fresh data on each visit.

## Step 4: Fix your images

Images are the heaviest part of most pages, and if we had to pick one fix for a typical small business site, it would be this one.

Start with size. A photo straight from a phone can be 4,000 pixels wide, while your content area is probably under 1,200, so resize before you upload.

Then the format. WordPress accepts WebP and AVIF uploads, which are usually much smaller than JPEG or PNG at the same quality, and many image and caching plugins can convert the library you already have.

One exception to lazy loading: the big image at the top of the page. WordPress lazy-loads images further down by default, which is good, but the first large image should load right away or your LCP gets worse. If a plugin lazy-loads everything, exclude that one.

## Step 5: Audit your plugins

The number of plugins matters less than what each one does. A single badly built plugin can add a second to every page. To find it:

- Delete plugins you no longer use (deactivated plugins still need updates and can still be a security risk).
- Install the free **Query Monitor** plugin for a day. It shows which plugins run slow database queries or load scripts on pages that don’t need them.
- On a staging copy, deactivate suspects one by one and re-test. Then decide: replace it, or keep it and accept the cost.

## Step 6: Cut third-party scripts

Chat widgets, social feeds, video embeds, heatmaps and several analytics tools all load code from other servers, and they’re a common reason for a poor INP score. For each one, ask whether you still use the data or feature. Remove what you don’t, and for the rest, check the tool’s settings for an option to load later or only on the pages that need it. Each of these scripts was added for a reason someone once cared about, which is exactly why they so rarely get removed.

For YouTube videos, a “lite” embed that shows a thumbnail and loads the player only when someone clicks play saves a lot of weight on every page with a video.

## Step 7: Load fewer fonts

Each font weight is a separate file. Pick one or two families, load only the weights you actually use, and host them on your own site in WOFF2 format. Add `font-display: swap` so text shows straight away in a fallback font while the web font loads.

**From experience:** on WebDesignColumn we use two variable fonts, Source Serif 4 for headings and Inter for text, both self-hosted as WOFF2. A variable font holds every weight in one file, so the whole site loads three font files (the serif’s italic is its own file), each around 50 KB, with no calls to outside font services.

## Step 8: Add a CDN

A content delivery network keeps copies of your images, scripts and styles on servers around the world, so visitors download them from somewhere nearby. If your visitors are spread across countries, it helps. Many hosts include one; Cloudflare’s free plan is a common choice if yours doesn’t.

## Step 9: Clean up the database

Old post revisions, expired temporary data and spam comments build up over the years. A cleanup plugin such as WP-Optimize can remove them. Take a backup first. You can also limit how many revisions WordPress keeps by adding this line to `wp-config.php`:

```
define( 'WP_POST_REVISIONS', 10 );
```

## Step 10: Re-test, then keep it fast

Run PageSpeed Insights again after each change. The lab score updates immediately; the real-user data at the top is an average over the previous 28 days, so give it a few weeks to catch up.

Speed slips over time as plugins update and pages get added, so check it once a month. A good [WordPress maintenance plan](https://www.webdesigncolumn.com/wordpress-maintenance-services/) includes that check, and if you’re planning a bigger rebuild, our [website redesign checklist](https://www.webdesigncolumn.com/website-redesign-checklist/) covers how to keep a new site fast from launch.

### Quick checklist

- **Baseline** recorded in PageSpeed Insights.
- **Hosting** responds quickly; PHP is a current version.
- **One caching plugin** (or server caching), forms tested after.
- **Images** resized, WebP or AVIF, main image not lazy-loaded.
- **Plugins** audited; unused ones deleted.
- **Third-party scripts** removed or loaded later.
- **Fonts:** one or two families, self-hosted, `font-display: swap`.
- **CDN** on if visitors are spread out.
- **Database** cleaned, after a backup.

## Frequently asked questions

**Why is my WordPress site slow even with a caching plugin?**

Caching speeds up how fast the server delivers the page, but not what the browser does afterwards. Large images, heavy scripts and many fonts still have to download and run. If the server response is fine but LCP or INP is poor, look at steps 4 to 7.

**Does the number of plugins slow WordPress down?**

Not by itself. Twenty light plugins can be faster than one heavy one. What matters is what each plugin loads and when, which Query Monitor shows you.

**Is a page builder slower than a block theme?**

Often, yes, because page builders tend to add extra code to every page. That doesn’t mean you must switch: a well-configured page builder site can still pass Core Web Vitals. If you’re rebuilding anyway, test a block theme first.

**How long until Google sees the improvement?**

The real-user data in PageSpeed Insights and Search Console covers the last 28 days, so improvements show up gradually over about four weeks.

Still slow?

## Get a WordPress speed audit and fix from people who do it every week.

Our partner agency Plugig Solutions speeds up and maintains WordPress sites: hosting checks, caching, images, plugin audits and Core Web Vitals. Tell them about your site and get a quote.

[Get a free quote](https://www.webdesigncolumn.com/hire-an-expert/)
