How to Speed Up WordPress: 12 Fixes That Actually Work

A slow WordPress site costs you twice: visitors leave before the page loads, and Google uses page experience as one of its ranking signals. The good news is that most WordPress sites are slow for the same handful of reasons, and most of the fixes are free.

This guide covers how to measure your speed properly, then the fixes in the order that usually gives the biggest gain for the least effort.

Measure first#

Don't guess. Run your homepage and one or two key pages, such as a product or pricing page, through PageSpeed Insights and note three numbers, the Core Web Vitals:

If PageSpeed Insights shows real-user data ("Discover what your real users are experiencing"), trust that over the lab score. The lab score changes from run to run; real-user data is what Google uses.

1. Use page caching#

Without caching, WordPress builds every page from PHP and the database for every visitor. A page cache saves the finished HTML and serves it instantly. This is the single biggest speed win on most sites.

Many hosts include server-level caching. If yours does not, use one caching plugin, such as WP Rocket, LiteSpeed Cache (on LiteSpeed servers), WP Super Cache or W3 Total Cache. Never run two caching plugins at once.

2. Upgrade PHP#

Each PHP 8 release runs WordPress faster than PHP 7.4, and old versions no longer get security fixes. WordPress recommends PHP 8.3 or newer. Our guide to the WordPress PHP version shows how to check and upgrade safely.

3. Fix your images#

Images are usually the heaviest part of a page.

• Resize before uploading. A 4000-pixel photo shown at 800 pixels wastes most of its weight.
• Use modern formats. WordPress supports WebP and AVIF uploads; both are much smaller than JPEG at the same quality.
• Lazy load images below the fold. WordPress does this by default for most images.
• Don't lazy load the main image. The hero image is usually your LCP element and should load first.

4. Remove plugins you don't need#

Every active plugin can add PHP work on every request, and many add CSS and JavaScript to every page, even pages that don't use them. Go through Plugins > Installed Plugins and delete anything you don't use. For the ones you keep, check whether they load scripts site-wide.

5. Cut third-party scripts#

Chat widgets, heatmaps, ad pixels, social embeds and A/B testing tools are often the biggest cause of a slow INP score, because they run JavaScript on your visitors' devices. Keep only the ones you actually use, and load the rest after the page has loaded or on interaction where the tool allows it.

6. Use a lighter theme and builder setup#

Multipurpose themes and page builders can add a lot of markup and CSS. You don't need to rebuild your site, but you can:

• Turn off builder features and widgets you don't use.
• Build new pages with lighter elements. In Elementor 4, Atomic Elements render cleaner HTML than classic widgets; see our guide to Elementor 4 and the Atomic Editor.
• Avoid stacking sliders, animations and video backgrounds above the fold.

7. Load fonts carefully#

Every font weight and style is a separate file. Use one or two families, only the weights you need, and host them locally where possible. Make sure fonts use font-display: swap so text appears immediately.

8. Add a CDN#

A content delivery network serves your images, CSS and JavaScript from servers close to each visitor. Cloudflare's free plan is enough for most sites, and many hosts include a CDN.

9. Clean up the database#

Post revisions, spam comments, expired transients and leftover tables from deleted plugins slow down database queries over time. Limit revisions in wp-config.php and clean up regularly with a plugin such as WP-Optimize, after taking a backup.

10. Add object caching for dynamic sites#

Stores, membership sites and busy blogs run many database queries that page caching cannot help with, such as the cart and account pages. A persistent object cache (Redis or Memcached, usually offered by managed hosts) keeps the results of those queries in memory.

11. Check your hosting#

If your server takes more than about 600 ms to respond (PageSpeed Insights shows this as "server response time" or time to first byte) even with caching on, the hosting plan may be the bottleneck. Cheap shared hosting puts many sites on one server, and no plugin can fix that.

12. Watch for speed regressions#

Sites rarely become slow all at once. They get slower one update at a time: a plugin update adds a script, a new marketing tool adds another, an uncompressed image goes on the homepage. Re-test after major changes, and see our general guide to website speed for more background.

Know when an update makes your site slower#

MyKavo tracks the response time, page weight and number of requests of the pages you choose, and alerts you when one of them jumps compared with your approved baseline. With the free MyKavo WordPress plugin, it also shows which plugin, theme or core update happened right before the slowdown, so you know exactly what to roll back or fix.

Frequently asked questions#