Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Speed & performance · Guide

How to Optimize WordPress Speed: A Practical, Step-by-Step Plan

How to Optimize WordPress Speed: A Practical, Step-by-Step Plan

Short answer

To optimize WordPress speed, measure your key pages first with PageSpeed Insights, then fix the biggest causes in order: good hosting and a current PHP version, page caching, compressed and modern-format images, fewer and lighter plugins, deferred scripts, efficient fonts and a CDN. Re-test after each change and track Core Web Vitals from real visitors over time.

Key takeaways

  • Measure before and after every change, using real-user Core Web Vitals where available.
  • Hosting, PHP version and page caching usually give the biggest gains.
  • Images are the heaviest part of most pages, so resize, compress and use modern formats.
  • Remove plugins and scripts you do not need before adding optimisation plugins.
  • Change one thing at a time so you know what helped and what broke.

Why does WordPress speed matter?

Faster pages keep more visitors, convert better and give search engines a better signal about page experience, while slow pages lose people before they see your content.

Google measures real-world loading, responsiveness and visual stability with the Core Web Vitals. These metrics reflect what visitors actually feel, not just a lab score.

Speed also affects running costs. Efficient pages use less server time, which matters on busy sites and cheaper hosting plans.

If your site already feels slow and you want to find out why, our guide on why a WordPress website is slow helps you diagnose the cause first.

How do you measure WordPress speed?

Test your homepage and your most important page types with PageSpeed Insights, note the Core Web Vitals and main suggestions, and keep these results as a baseline before changing anything.

PageSpeed Insights shows both field data from real Chrome users, where available, and lab data from a simulated test. Field data is what matters most for visitors and search.

Test several page types, not only the homepage. A blog post, a product page and a category page often have very different problems.

Run lab tests a few times and look at the trend. Single results vary with network conditions and server load.

Is your hosting fast enough?

Good hosting is the foundation: fast servers, enough resources, server-level caching and a data centre near your visitors make every other optimisation more effective.

Cheap shared hosting can be fine for small sites, but busy sites, WooCommerce stores and membership sites often need more power. Slow server response time shows up as a high Time to First Byte.

Our comparison of shared, VPS and managed WordPress hosting explains when an upgrade makes sense.

Which PHP version should you use?

Use a current, supported PHP version that your theme and plugins support, since newer PHP versions run WordPress faster and receive security fixes.

WordPress recommends a recent PHP version on its requirements page, and the PHP project lists which versions are still supported on its supported versions page.

Test the change on a staging site first. Old plugins sometimes break on new PHP versions. Our guide on updating the PHP version in WordPress walks through the process.

How do you set up page caching?

Use your host's built-in page cache if it has one, or install one caching plugin, so visitors receive a ready-made HTML page instead of WordPress building it on every request.

Caching is usually the single biggest improvement for content sites. Browser caching adds a second layer, letting returning visitors reuse files they already downloaded, as MDN's guide to HTTP caching explains. It reduces server work and speeds up the first byte for most visitors.

Use only one page caching layer you control. Running two caching plugins, or a plugin on top of a host cache without care, often causes stale or broken pages.

If your host runs LiteSpeed, our guide to LiteSpeed Cache settings is the place to start.

On other servers, a plugin such as WP Fastest Cache is a simple free option. Our guide to WP Fastest Cache settings shows which options to turn on.

How do you optimise images?

Resize images to the size they are displayed at, compress them, serve modern formats such as WebP or AVIF, and lazy-load images below the first screen.

Images are often the heaviest files on a page. A hero image uploaded straight from a camera can outweigh everything else combined.

WordPress lazy-loads most images automatically and creates several sizes for responsive images. Image optimisation plugins can also convert and compress uploads.

Do not lazy-load the main image at the top of the page. It should load as early as possible because it is often the Largest Contentful Paint element. Our guide to serving images in next-gen formats covers conversion.

How do you reduce plugin and script bloat?

Remove plugins you do not need, replace heavy plugins with lighter ones, and stop scripts and styles from loading on pages that do not use them.

The number of plugins matters less than what they load. One plugin that adds large scripts to every page can cost more than ten small ones.

Check the front end of key pages for unnecessary scripts such as sliders, chat widgets, social embeds and tracking tags. Each third-party script adds requests and work for the browser.

Our guide to eliminating render-blocking resources explains how to defer or delay scripts safely.

How do you handle fonts?

Use fewer font families and weights, host fonts locally or use system fonts, preload the main font if needed, and set font-display so text appears quickly.

Each font weight is a separate file, and each extra file must download before the text can use it. A design using four families in several weights can add many requests before text looks right.

Block themes and the Font Library make local fonts easier to manage. Many page builders also offer an option to load Google Fonts locally.

Should you use a CDN?

Yes, for most sites with visitors in more than one region: a content delivery network serves static files, and sometimes whole pages, from servers close to each visitor.

A CDN reduces distance and offloads traffic from your server. Many hosts include one, and services like Cloudflare offer free plans that are enough for most small and medium sites.

Our guide on setting up a CDN for WordPress shows the steps.

How do you clean up the database?

Remove old revisions, spam and trashed comments, expired transients and leftover tables from deleted plugins, and keep autoloaded options small, after taking a backup.

A bloated database mostly hurts the admin area and uncached pages, such as carts and account pages. It rarely matters for cached pages.

Our guide to optimizing the WordPress database explains safe cleanup methods.

What about the WordPress admin area?

A slow dashboard usually comes from heavy plugins, too many admin notices, the Heartbeat API, slow hosting or a large database, rather than from front-end settings.

Caching plugins do not speed up the admin, because admin pages are personalised. Fixes focus on the server and plugins instead.

Our guide on speeding up the WordPress admin covers these causes in detail.

What about WooCommerce and membership sites?

Stores and membership sites need extra care, because carts, checkouts and account pages cannot be cached for everyone and rely on a fast server and a lean database.

Make sure your caching solution excludes cart, checkout and account pages. Then focus on hosting resources, object caching such as Redis where your host offers it, and keeping order and session data tidy.

Checkout speed directly affects sales. Our guide on speeding up WooCommerce checkout covers store-specific fixes.

Which order should you work in?

Fix the foundation first, then the heaviest items: hosting and PHP, page caching, images, scripts and fonts, then a CDN and database cleanup, testing after each step.

Working in this order avoids wasted effort. Fine-tuning script delays matters little if the server takes two seconds to respond.

How do you keep the site fast over time?

Re-test key pages after updates and new features, watch Core Web Vitals in Search Console, review plugins every few months, and keep images optimised as you publish.

Sites slow down gradually as new plugins, scripts and large images pile up. A short monthly check catches problems early.

Keep a simple log of what you changed and when. If speed drops, you can match the change to the cause quickly.

Set a performance budget for important pages, such as a maximum page weight or a target Largest Contentful Paint. When a new feature would break the budget, you can decide consciously whether it is worth the cost.

Frequently asked questions

What is the fastest way to speed up WordPress?

For most sites, good hosting, a current PHP version and page caching give the biggest gains, followed by image optimisation. Measure before and after each change to confirm the improvement.

Do I need a caching plugin?

Usually yes, unless your host provides page caching at the server level. Use one caching solution rather than several, since overlapping caches cause conflicts.

Does the number of plugins slow WordPress down?

What plugins load matters more than how many you have. A single heavy plugin can slow pages more than many small ones, so check what each plugin adds to the front end.

Why is my PageSpeed score different every time?

Lab tests vary with network conditions and server load. Run several tests and focus on field data from real users, which shows how visitors actually experience your pages.

Will a CDN make my WordPress site faster?

For visitors far from your server, usually yes. A CDN serves files from nearby locations and reduces load on your host, though it cannot fix slow server code on its own.

Sources

  1. Web Vitals web.dev
  2. PageSpeed Insights Google
  3. Supported Versions PHP
  4. Optimization WordPress Developer Resources
  5. HTTP caching MDN Web Docs

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.