How to Speed Up WordPress: Practical Steps for a Faster Site and Better Rankings

A visitor opens your page on their phone, waits one second, then two, then taps the back button and goes to your competitor. This happens every day on slow websites, and the site owner never sees it. All they see is traffic that doesn't turn into orders. That's why speeding up WordPress isn't a side technical tweak. It's part of the success of the business itself.

In this guide you'll learn the metrics Google uses to measure page experience, how to measure your site's speed with free tools, and then practical steps to make it faster: from hosting and your PHP version, to caching, images and fonts, ending with a priority list that starts with the highest impact and lowest effort.

Why WordPress speed matters

Speed affects three connected things:

• Visitor behavior: people on mobile are less patient, and every delay increases the chance they leave before the page loads.
• Conversions: a contact form that lags or a buy button that jumps around while the page loads means lost orders.
• Search results: Google uses Page Experience signals, including Core Web Vitals. These signals aren't the most important factor (good content still comes first), but they can tip the balance in your favor against a competitor with similar content.

The good news is that WordPress is a flexible platform, and most speed problems have well-known fixes that don't require a developer.

Core Web Vitals in plain language

Core Web Vitals are three metrics Google uses to measure real user experience:

Note that INP replaced FID (First Input Delay) in March 2024, so if you read an older article that talks about FID, know that it's no longer one of the core metrics.

How to measure your site's speed

• PageSpeed Insights: Google's free tool. It shows real-user data (if available for your site) alongside a lab test with detailed recommendations.
• Google Search Console: its Core Web Vitals report groups similar pages and shows which ones need improvement, on both mobile and desktop.
• GTmetrix: shows the loading waterfall so you can see which file or image takes the longest.

Test your home page and your most important product or service page, and record the results before making any changes so you can compare afterward.

Tip: Don't chase a score of 100 in PageSpeed. The goal is for all three metrics to fall in the "good" range for your real visitors, because that's what matters to both visitors and search engines.

The foundation: hosting quality and PHP version

No plugin can make up for a slow server. Server response time (TTFB) is the first thing a visitor waits for before anything starts to appear.

What to look for in hosting

• NVMe drives instead of traditional disks, because WordPress constantly reads from the database and files.
• Enough resources for the size of your site, with the option to upgrade as traffic grows.
• A data center reasonably close to your audience, or a CDN, as we'll explain later.

If you're comparing offers, our guide to choosing the right web hosting explains the criteria in detail.

Update your PHP version

WordPress is written in PHP, and newer PHP 8 releases are faster and more secure than older versions that are no longer supported. Choose a PHP 8.x release that is still officially supported. You can usually change it in cPanel through the Select PHP Version or MultiPHP Manager tool, depending on your host.

Take a backup before switching, then test your site thoroughly, because some older themes or plugins may not be compatible with the new version.

Caching: the biggest win for the least effort

By default, WordPress builds each page from scratch for every visitor: it runs PHP, queries the database, then sends the result. Caching saves the finished result and serves it directly.

Types of caching

1. Page Cache: saves a ready-made HTML copy of the page. This is the biggest improvement for most sites.
2. Browser Cache: tells the visitor's browser to keep images and CSS and JS files, so they aren't downloaded again when moving between pages.
3. Object Cache: stores database query results in memory using Redis or Memcached. It benefits stores and large dynamic sites, if your server supports it.

Choosing a caching plugin

There are well-known plugins for this, including WP Super Cache and W3 Total Cache. If your hosting server runs LiteSpeed, the LiteSpeed Cache plugin is designed to integrate with it: its page caching feature relies on the LiteSpeed server (or related services), so there's no point choosing it for that purpose on a different server. No plugin is "mandatory". What matters is that you use only one caching plugin, because running two together causes conflicts.

After activating it, exclude the cart, checkout and account pages from page caching if you run a store, then test the site while logged out.

Images: often the heaviest part of the page

On many WordPress sites, images are the number one cause of slow LCP.

• Modern formats: WebP and AVIF produce smaller files at similar quality compared with JPEG and PNG. WordPress supports uploading WebP, while AVIF support depends on your WordPress version and the server's libraries.
• Correct dimensions: don't upload a 4,000-pixel-wide image to display in an 800-pixel space. Resize it before uploading.
• Lazy loading: WordPress adds it to images automatically, so images further down the page load only as the visitor approaches them. But don't lazy-load the main image at the top of the page, because that delays LCP.
• Set width and height: including image dimensions in the code reserves their space in advance and prevents content from jumping, which improves CLS.

Image optimization plugins can convert old images to WebP and compress them in bulk, which is useful for sites that have accumulated a lot of images.

Theme, plugins, and CSS and JS files

A lightweight theme

Some multipurpose themes load dozens of files and features you'll never use. A lightweight theme built with clean code gives you a much faster starting point. If you use a page builder, enable its options for loading files only where needed, if available.

Fewer, better plugins

The problem isn't the number of plugins in itself, but heavy or poorly coded plugins. Review your list:

• Delete deactivated and unused plugins.
• Replace plugins that do one small job with a simple code snippet or a feature already built into your theme.
• Watch for plugins that load their files on every page, such as contact forms and chat widgets.

Minify and defer JavaScript and CSS

• Minify: removes spaces and comments from files to reduce their size.
• Defer: loads JavaScript after the content renders so it doesn't block the page from appearing, which helps LCP and INP.
• Remove unused CSS: some caching plugins offer this, but it can break your design, so test after each change.

Most caching plugins include these options. Enable them one at a time and check your site after each step.

CDN, database and fonts

Content Delivery Network (CDN)

A CDN (Content Delivery Network) copies your static files, such as images, CSS and JS, to geographically distributed servers, so visitors download them from the nearest location. It's especially useful if your audience is spread across different countries, for example between the Gulf, Turkey and Europe.

Database cleanup

Over time, your database accumulates post revisions, spam comments and expired transients. Cleaning them out regularly reduces its size. Always do this after taking a backup, and read our website backup strategy if you don't have a plan yet. You can also limit the number of saved revisions by adding this line to your wp-config.php file:

define( 'WP_POST_REVISIONS', 5 );

Fonts

Arabic fonts in particular can be large files. To improve their performance:

• Use one or two font families and only a few weights (for example, regular and bold only).
• Host fonts on your own server in WOFF2 format if possible.
• Use font-display: swap so text appears immediately in a fallback font, then switches once the font loads:

@font-face {
  font-family: "MyArabicFont";
  src: url("/fonts/myfont.woff2") format("woff2");
  font-weight: 400;
  font-display: swap;
}

WordPress speed priority checklist

Start at the top of the table. These steps are roughly ordered by expected impact versus effort, and results may vary depending on your site:

Frequently asked questions

Does site speed directly affect Google rankings?

Speed and page experience are among the signals Google takes into account, but they aren't the strongest factor: how well your content matches the user's search still matters more. In practice, improving speed also helps rankings indirectly, because visitors stay longer and engage more.

How many WordPress plugins is too many?

There's no set number. A site with twenty lightweight plugins can be faster than one with five heavy plugins. What counts is each plugin's impact on performance, which you can measure by temporarily deactivating it on a staging copy and comparing the results.

Why does my PageSpeed score change every time I test?

Lab tests are affected by network and server conditions at the moment of measurement, so it's normal for the score to vary slightly. Rely on the average of several tests, and above all on the real-user data in Search Console, because it reflects your visitors' actual experience over several weeks.

Do I need a CDN if my site is local?

If your audience is in one country close to your hosting data center, a CDN's impact may be limited. It's still useful for reducing server load and speeding up static files, so decide after measuring speed from your actual visitors' locations.

Can a caching plugin break my site?

Problems such as a broken layout or a shopping cart that doesn't update can appear, especially with file combining and deferring options. Enable options gradually, test your site after each change, and exclude dynamic pages from caching.

Conclusion

Speeding up WordPress is a methodical process, not magic. Measure first with tools like PageSpeed Insights and Search Console, then start with the highest-impact steps such as caching, image compression and updating PHP, and move on to plugins, files, fonts and a CDN after that. Measure again after each stage so you know what actually made the difference.

And if the server itself is what's slowing your site down, NetNexus hosting with NVMe drives, cPanel and free migration of your existing site could be your next step. Browse our hosting plans.