Web Development

How to Speed Up WordPress: 12 Proven Fixes for a Faster Site

How to speed up WordPress: test your site, then fix hosting, PHP, caching, images, plugins, the database and CDN, using WordPress.org's own guidance.

Safikul Islam· 7 min read
Fast-loading website on a laptop with speed lines, a server, compressed images and a stopwatch
On this page

WordPress powers a huge share of the web, but it doesn’t have a great speed reputation. In HTTP Archive’s November 2025 Core Web Vitals technology report, only about 46% of WordPress sites passed Core Web Vitals, the lowest of the six platforms Search Engine Journal compared. The good news: WordPress itself is rarely the problem. Slow hosting, heavy themes, too many plugins and unoptimised images usually are.

In this guide I’ll show you how to measure your site’s speed, then work through 12 fixes in the order I’d tackle them, from the biggest wins to the fine-tuning. I’ve based the steps on WordPress.org’s own optimisation documentation and Google’s performance guidance.

First: measure before you change anything

Test two or three important pages (your homepage, a popular post and a key landing page), not just the homepage.

  • PageSpeed Insights: shows real-user Core Web Vitals data (if your site has enough traffic) plus a lab test with suggestions.
  • Google Search Console › Core Web Vitals: shows which groups of pages are slow across your whole site. My Google Search Console tutorial explains where to find it.
  • Your browser’s DevTools › Network tab: shows how many files load and how big they are.

Write down your scores. After each fix, test again, so you know what actually helped. For a full explanation of LCP, INP and CLS, read my guide on how to improve Core Web Vitals.

Important: take a full backup before changing caching, database or performance settings.

1. Use good hosting

Hosting sets the ceiling for how fast your site can be. WordPress.org’s optimisation guide notes that better CPU, more RAM and SSD or NVMe storage make a big difference.

  • Cheap shared hosting is fine for a small blog, but busy sites outgrow it.
  • Look for hosts with server-level caching, HTTP/2 or HTTP/3, PHP 8.3+ and a data centre near your visitors.
  • Managed WordPress or cloud hosting (VPS) usually gives better and more consistent speed. See my explainer on virtual private servers.

If your server response time (TTFB) is slow even on a simple page, hosting is likely your bottleneck.

2. Run a current PHP version

Newer PHP versions are faster and more secure. WordPress.org currently recommends PHP 8.3 or newer and MySQL 8.0+ or MariaDB 10.11+. Older versions still run WordPress, but they’re end-of-life.

You can usually change PHP version in your hosting control panel. Check Tools › Site Health first to make sure your theme and plugins are compatible, and test on a staging site if you can.

3. Turn on page caching

Without caching, WordPress builds every page from scratch on every visit: running PHP, querying the database and assembling the HTML. A page cache saves a ready-made copy and serves that instead. WordPress.org’s documentation says this can help “several hundred times over” for fairly static pages.

  • Many hosts include page caching (for example Cloudways with Breeze and Varnish, or LiteSpeed servers with LiteSpeed Cache). Use what your host recommends.
  • Otherwise, use a caching plugin such as WP Super Cache, W3 Total Cache or WP Rocket.
  • Use only one caching plugin. Two often conflict.

4. Add an object cache and opcode cache

Two server-side caches make WordPress itself faster:

  • Opcode cache (OPcache): stores compiled PHP so it doesn’t need recompiling on every request. Most good hosts enable it by default.
  • Persistent object cache (Redis or Memcached): stores the results of database queries so WordPress doesn’t repeat them. This especially helps WooCommerce, membership sites and logged-in users, where page caching can’t help much.

Tools › Site Health will tell you if a persistent object cache is recommended for your site. Ask your host whether Redis is available.

5. Optimise your images

Images are often the heaviest part of a page.

  • Resize images to the size they’re displayed at. Don’t upload a 4000-pixel photo for an 800-pixel space.
  • Use WebP or AVIF. WordPress has supported AVIF uploads since version 6.5.
  • Compress images with an image optimisation plugin or your host’s tools.
  • WordPress lazy-loads images below the fold automatically (since 5.5) and, since 6.3, adds fetchpriority="high" to the image it thinks is the main (LCP) image. Check that your theme or page builder isn’t lazy-loading your hero image anyway.

My guide to responsive images in WordPress explains how WordPress serves different sizes to different screens.

6. Remove plugins you don’t need

Each plugin can add PHP work, database queries, CSS and JavaScript. WordPress.org’s advice is simple: remove plugins you don’t need, and if you suspect one is slowing you down, deactivate them one at a time and re-test.

Common heavy hitters:

  • sliders and carousels
  • page builders used for one or two pages
  • social feed widgets
  • “all-in-one” plugins where you use one feature
  • multiple plugins doing the same job (two SEO plugins, two security plugins)

A free plugin such as Query Monitor shows which plugins run the most database queries and slow PHP.

7. Use a lightweight theme

A theme packed with animations, sliders and bundled features loads lots of code on every page, whether you use it or not. A lightweight theme (or a block theme built for the Site Editor) gives you a faster starting point. When you compare themes, test their demo pages in PageSpeed Insights.

8. Reduce CSS, JavaScript and fonts

  • Minify CSS and JavaScript (most caching plugins do this).
  • Defer non-critical JavaScript so it doesn’t block the page from appearing.
  • Remove unused CSS where your optimisation plugin supports it, and test carefully, since aggressive settings can break layouts.
  • Limit web fonts to one or two families and a few weights, and host them locally if you can.
  • Load scripts such as chat widgets and heavy embeds only on pages that need them.

Heavy JavaScript is also the main cause of poor INP (slow response to clicks and taps).

9. Clean up the database

Over time, the database fills with post revisions, spam comments, trashed posts, expired transients and leftover data from deleted plugins.

  • Empty spam and trash regularly.
  • Limit post revisions by adding define( 'WP_POST_REVISIONS', 10 ); to wp-config.php.
  • Keep autoloaded options small. WordPress.org’s guide suggests staying under about 800 KB. Site Health flags this if it’s a problem.
  • Use a database clean-up plugin (such as WP-Optimize) or your host’s tools, after taking a backup.

10. Use a CDN

A content delivery network stores copies of your images, CSS and JavaScript on servers around the world, so visitors download them from somewhere nearby. WordPress.org recommends a CDN to reduce server load and improve speed for distant visitors. Cloudflare has a free plan, and many hosts include a CDN add-on.

11. Make use of speculative loading

Since WordPress 6.8, core includes speculative loading: when a visitor starts clicking a link, the browser begins fetching that page early, so it appears faster. By default it uses a conservative prefetch and is turned off for logged-in users. The free Speculative Loading plugin from the WordPress Performance Team lets you change the settings (for example, to prerender pages when visitors hover over links).

12. Keep everything updated and monitored

  • Update WordPress core, your theme and plugins. Updates often include performance improvements.
  • Block abusive traffic such as brute-force login attempts, which waste server resources. See my WordPress security tips.
  • Re-test your key pages every month, and after installing any new plugin.

If speed changes break your site

  • Clear all caches (plugin, server and CDN) and check again in a private window.
  • Undo the last setting you changed. Minify, combine and “delay JavaScript” options are the most common culprits.
  • Check the browser console (F12) for errors.
  • If you see a white screen or a server error, my guide to the WordPress 500 internal server error walks through recovery.

Frequently asked questions

Why is my WordPress site so slow? The most common causes are slow hosting, no page caching, large images, too many plugins and a heavy theme. Measure first, then fix the biggest issue PageSpeed Insights reports.

What is the best caching plugin for WordPress? The best one is usually the one your host recommends, because it works with the server’s own cache. Otherwise, WP Super Cache (free) and WP Rocket (paid) are popular, easy options.

Does site speed affect SEO? Speed is part of Google’s page experience signals, but relevant, helpful content matters more. A faster site mainly keeps visitors from leaving, which supports your SEO and sales. For more, see my technical SEO audit checklist.

How fast should a WordPress site load? Aim to pass Core Web Vitals: main content visible within 2.5 seconds (LCP), responses to clicks within 200 milliseconds (INP) and minimal layout shift (CLS of 0.1 or less).

Sources

About Safikul Islam

Safikul Islam is an Entrepreneur, Business mentor, AI & Business strategist, and CEO of Leelija Web Solutions Pvt. Ltd. I writes about Entrepreneurship, Business growth, Artificial Intelligence, AI agents, Digital marketing, SEO, Branding, Technology, Apps and Software.

Keep learning

Topics: · · ·

Join the conversation

Have a tip, question or experience to share? We’d love to hear from you.

Leave a comment

Leave a Reply

Your email address will not be published. Required fields are marked *