Why your WordPress site is slow, and 7 fixes that work

When a WordPress site is slow, it costs more than patience. Visitors on a phone give a page about three seconds before they go back to Google and pick someone else, and Google notices that too. The good news: most slow sites have the same handful of problems, and you can find yours in ten minutes with a free test. This guide covers how to test, the seven fixes that make the biggest difference to WordPress speed, and what to do if your WordPress site is slow even after all of them.

PageSpeed score of 98 showing a WordPress site is slow no longer

Is your WordPress site slow? Test it first

Run your homepage through PageSpeed Insights on mobile. Ignore the overall score for now and look at the three Core Web Vitals:

  • LCP (Largest Contentful Paint): how long the biggest thing on screen, usually the hero image or heading, takes to appear. Aim for under 2.5 seconds.
  • INP (Interaction to Next Paint): how quickly the page reacts when someone taps a button or opens a menu. Aim for under 200 milliseconds.
  • CLS (Cumulative Layout Shift): how much the page jumps around while it loads. Aim for under 0.1.

Whichever Core Web Vitals score is red is where to start. Write the numbers down before you change anything, so you can prove each fix worked. If your WordPress site is slow only on mobile, that usually points at images and scripts. If it is slow everywhere, look at hosting and caching first.

Test the page your ads or Google results actually point to. It is often not the homepage.

1. Too many plugins doing the same job

Two SEO plugins, three slider plugins, a page builder you stopped using. Each one loads its own scripts on every page. Deactivate what you do not use, then check which plugins load files on pages that do not need them. The number of plugins matters less than what each one loads: twenty light plugins can be faster than five heavy ones.

// Only load the contact form scripts on the contact page
add_action( 'wp_enqueue_scripts', function () {
  if ( ! is_page( 'contact' ) ) {
    wp_dequeue_script( 'contact-form-7' );
  }
}, 100 );

Swap the handle for whichever plugin you are trimming. One rule: never remove a script without checking that the page still works afterwards, including forms and the mobile menu.

2. Huge images straight from the camera

A 5 MB photo shown at 600 pixels wide is the most common speed problem there is. Convert to WebP, resize to the size it is actually shown at, and lazy load anything below the first screen. Never lazy load the main hero image: it is usually your LCP element. WordPress lazy loads most images by default, so mark the hero with fetchpriority=”high” to make the browser fetch it first.

3. No page caching

Without caching, WordPress rebuilds every page from the database for every visitor. A caching plugin or server-level cache serves a ready-made copy instead, often cutting load time in half on its own. Pair it with browser caching for images, CSS and fonts, and object caching like Redis if your host offers it. On online stores, exclude the cart, checkout and account pages from the cache.

4. Cheap shared hosting

If your server takes more than 600 ms to answer (Time to First Byte in the test), no plugin will speed up WordPress enough to matter. Cheap plans put hundreds of sites on one server, so your speed depends on your neighbours. Look for recent PHP, server-level caching, HTTP/2 or HTTP/3 and a data centre near your customers. Moving can be done with zero downtime: here is the checklist for moving hosts.

5. A heavy page builder

Page builders add layers of wrappers, CSS and JavaScript to every page. If speed matters most, rebuild the key pages lean, or switch to a theme that does not depend on a builder. If a rebuild is not in the budget, trim what the builder loads: turn off unused widgets, disable its icon and font libraries, and avoid nesting sections inside sections. The trade-offs are compared in Elementor vs Gutenberg vs a custom theme.

6. Third-party scripts

Chat widgets, heatmaps, three analytics tags and a font from a different server. Each one is a request your visitor waits for. Keep the ones that earn their place and delay the rest until the visitor interacts. To find them, open your browser’s developer tools, go to the Network tab, reload and sort by domain. Anything that is not your own domain is worth questioning.

7. An old PHP version

PHP 8 runs WordPress noticeably faster than PHP 7. Most hosts let you switch in one click. Test on a staging copy first, because very old plugins can break. While you are there, check the memory limit: 256 MB is a sensible minimum for WordPress with WooCommerce or a page builder.

How to speed up WordPress and keep it fast

Speed is not a one-off job. Every new plugin, image and tracking script adds weight. Re-run the test once a month, compress images before you upload them and test updates on staging before they go live. A care plan with monthly speed checks catches problems before your visitors do.

Mistakes that make things worse

Installing three speed plugins at once is the classic one: they fight over the same files and can break the layout. Combining every script into one big file is another, because modern browsers load several small files faster. And chasing a perfect 100 score is rarely worth it. A page that loads in under two seconds on a phone and passes Core Web Vitals is fast enough to win the visitor.

When your WordPress site is slow after all seven fixes

If you have worked through the list and the page is still red, the cause is usually deeper: the theme, the database or the server. That is where an experienced developer saves you days. A fixed-price speed fix comes with a before and after report, so you can see exactly what changed. If you would rather hand it over, send a short brief with a link to the slow page.

Ahsan Salman

Full-stack web developer. Builds, fixes and looks after websites, web apps and online stores for businesses and agencies.

Start a project

Tell me a little about it. You'll get a reply within one working day.