If you want to speed up a WordPress site, the worst thing you can do is install 5 “speed” plugins and hope for the best. I see it all the time. The site gets a little faster on 1 test, slower on another, and something random breaks at checkout. Real WordPress speed optimization starts with measuring, then fixing the biggest bottleneck first.
I have been building websites and online stores since 2010, and I run several WordPress sites for my own businesses today. The pattern is almost always the same. A slow WordPress site is usually caused by 1 or 2 big things, like weak hosting, no page caching or huge images, not 50 tiny things.
In this guide I will walk you through the exact order I would follow: measure with PageSpeed Insights and Core Web Vitals, check your hosting and PHP version, set up page caching and object caching, add a CDN, fix images with WebP or AVIF and lazy loading, audit your plugins, clean the database, and tighten up fonts and scripts. I will also show you how to tell when the host itself is the bottleneck, because no plugin can fix a server that is out of resources.
If you are still choosing a host, start with my web hosting for beginners guide. Speed starts with the server you pick, and that guide explains the hosting types in plain English.
All right, let’s get into it.
Quick note: some links on Web Hosting Paradise may become affiliate links in the future. See our affiliate disclosure for how that works. Everything here is research-based, and I never claim testing I did not do.
Step 0: Back Up Before You Touch Anything
Speed work means changing caching settings, swapping plugins and cleaning the database. Any of those can break a site. So before you change a single setting, take a full backup of your files and database.
If you are not sure how, follow my guide on how to backup a WordPress site. Better yet, make your changes on a staging copy first, then push them live once everything checks out.
Step 1: Measure Your Speed First
You cannot fix what you have not measured. And you need to measure the right things, because a “speed score” on its own can be misleading.
Use PageSpeed Insights
Start with PageSpeed Insights, Google’s free tool. Run your home page, a typical blog post, and your most important money page, like a product page or contact page. Test both mobile and desktop.
PageSpeed Insights shows 2 types of data. Field data comes from real Chrome users visiting your site over time. Lab data is a simulated test run right now. Field data is what actually matters for your visitors, while lab data is useful for diagnosing problems and checking a fix.
Understand Core Web Vitals
Core Web Vitals are the 3 metrics Google uses to measure real user experience. According to web.dev’s Core Web Vitals guide, the “good” thresholds are:
- Largest Contentful Paint (LCP): 2.5 seconds or less. This measures how fast the main content loads.
- Interaction to Next Paint (INP): 200 milliseconds or less. This measures how quickly the page responds when someone clicks or taps.
- Cumulative Layout Shift (CLS): 0.1 or less. This measures how much the page jumps around while loading.
Google measures these at the 75th percentile of page loads, split by mobile and desktop. So your site has to be fast for most visitors, not just on your fast office connection.
Why Speed Matters for SEO (and Sales)
Google’s page experience documentation says Core Web Vitals are used by its ranking systems. It also says good scores do not guarantee top rankings, and chasing a perfect score just for SEO may not be the best use of your time.
That matches what I believe. Speed is not a magic ranking trick. It is about not losing visitors and buyers who give up on a slow page. Aim to pass Core Web Vitals, then spend your energy on content and offers.
Find Your Real Bottleneck
Look at Time to First Byte (TTFB) in the diagnostics. TTFB is how long the server takes to start sending the page. If TTFB is slow, the problem is usually the server, PHP or missing page caching. If TTFB is fast but LCP is slow, the problem is usually images, fonts, CSS or JavaScript on the page.
That 1 split tells you where to spend your time. web.dev has a detailed guide on how to optimize Largest Contentful Paint that breaks LCP into these same parts.
Step 2: Check Your Hosting and PHP Version
Hosting is the foundation. Every other fix sits on top of it.
Update to a Supported PHP Version
WordPress runs on PHP, and newer PHP versions are usually faster and more secure. The official WordPress requirements page recommends PHP 8.3 or greater, plus MySQL 8.0 or MariaDB 10.11 or greater.
Here is the timing piece most people miss. According to PHP’s supported versions page, PHP 8.2 only gets security fixes until December 31, 2026. If your site is on 8.2 or older, plan the upgrade now.
Most hosts let you change PHP from the control panel. Back up first, switch on staging if you can, and check that your theme and plugins still work. Old, abandoned plugins are the usual thing that breaks.
Shared vs Managed vs Cloud Hosting
Cheap shared hosting puts many sites on 1 server. That is fine for a small blog, but when your neighbors get busy, your site can slow down. Managed WordPress hosting usually adds server-level caching, newer PHP, staging and tuned servers.
I break down the real differences in my guide to managed WordPress vs shared hosting. If you want more control without running your own server, cloud platforms are another option, which I cover in my Cloudways review.
Signs Your Host Is the Bottleneck
Here is how I tell when the host is the real problem and not WordPress:
- TTFB stays slow even with page caching turned on
- The site is fast at night and slow during busy hours
- wp-admin is sluggish even on simple screens
- You see “resource limit reached” or 503 errors in your logs or hosting dashboard
- Your host is still on old PHP or MySQL versions and cannot upgrade
- Your plan has hard CPU or memory limits and you keep hitting them
If you see 2 or 3 of these, no plugin will save you. Upgrade the plan or move. My guide to the best WordPress hosting compares the options. Then my pillar guide on how to migrate a WordPress site to a new host walks you through the move step by step.
Watch the Renewal Price
Faster hosting often costs more, especially after the intro price ends. Before you upgrade, compare renewal prices, not just the first-year deal. I explain how in my guide to cheap WordPress hosting.
Step 3: Set Up Page Caching
Page caching is the single biggest speed win for most WordPress sites. Without it, WordPress runs PHP and queries the database on every single visit to build the page from scratch. With it, the finished HTML is saved and served instantly.
The official WordPress caching documentation covers the main types: page caching, browser caching, object caching and server-side caching.
Server Caching vs Plugin Caching
Many managed WordPress hosts include server-level page caching, using tools like Nginx caching or Varnish. If your host has it, use it, and do not stack a second page cache plugin on top unless the host recommends it. 2 page caches fighting each other is a classic cause of weird bugs.
If your host does not include caching, use a caching plugin. Common options include WP Rocket, LiteSpeed Cache (built for LiteSpeed servers), W3 Total Cache and WP Super Cache. Pick 1 and stick with it.
Pages You Should Never Cache
For WooCommerce and membership sites, some pages must stay dynamic. Cart, checkout and my-account pages should be excluded from page caching, along with anything that shows logged-in user data. Most good caching plugins and hosts exclude WooCommerce pages by default, but double check.
Browser Caching
Browser caching tells visitors’ browsers to keep files like images, CSS and JavaScript for a while, so repeat visits load faster. Most caching plugins and managed hosts set these headers for you.
Step 4: Add Object Caching
Page caching helps visitors who are not logged in. Object caching helps everything else: wp-admin, logged-in users, WooCommerce carts and search results.
What a Persistent Object Cache Does
WordPress has a built-in object cache, but by default it only lasts for a single page load. A persistent object cache, usually Redis or Memcached, keeps query results in memory between requests. That means fewer trips to the database.
The WordPress optimization handbook recommends a persistent object cache with a cache server from your host plus a compatible plugin, especially to keep response times steady during traffic spikes.
When You Need It
If you run a WooCommerce store, a membership site, a forum or a busy blog with lots of logged-in users, object caching is worth it. Check whether your host offers Redis or Memcached, then enable it with the matching plugin. Many managed hosts include it on mid-tier plans or above, so check your plan details.
Step 5: Use a CDN
A content delivery network (CDN) stores copies of your static files, like images, CSS and JavaScript, on servers around the world. Visitors download those files from a location near them instead of your origin server.
When a CDN Helps Most
A CDN makes the biggest difference when your visitors are spread out geographically. If your server is in the US and half your readers are in Europe or Asia, a CDN can cut a lot of travel time.
It also takes load off your server. The WordPress optimization handbook says a CDN works best alongside a caching plugin, which is how I would set it up.
Common Options
Cloudflare has a free plan that many site owners start with. Many hosts include a CDN, and some caching plugins have their own. Check what your host already includes before you add another service.
Some CDN setups can also cache full HTML pages at the edge, not just static files. That can make a big difference, but test carefully on stores and membership sites so carts and logged-in pages stay dynamic.
Step 6: Optimize Your Images
Images are usually the heaviest part of a page, and the hero image is often your LCP element. This is where a lot of easy wins hide.
Resize Before You Upload
Do not upload a 5,000-pixel photo straight off your phone or camera for a spot that displays at 1,200 pixels. Resize to the largest size you actually need. WordPress creates smaller versions automatically for different screens, but starting with a sensible size saves storage and processing.
Use WebP or AVIF
Modern formats are much smaller than JPEG and PNG at similar quality. WordPress supports WebP uploads, and since version 6.5 it also supports AVIF, according to the WordPress core announcement that WordPress 6.5 adds AVIF support. Your server’s image library needs to support the format for WordPress to process it, so check with your host.
An image optimization plugin can convert your existing library to WebP or AVIF automatically and compress new uploads. Pick 1 tool for this, not several.
Lazy Load Below the Fold, Not Above It
Lazy loading delays offscreen images until the visitor scrolls near them. WordPress adds native lazy loading to images by default, and web.dev explains how browser-level image lazy loading works.
Here is the catch. Your main hero image should not be lazy loaded, because that delays your LCP. Recent WordPress versions try to skip lazy loading for the first images on the page, but page builders and some plugins can override that. Check the hero image in PageSpeed Insights.
Set Image Dimensions
Always include width and height on images so the browser can reserve space. That stops the page from jumping around as images load, which helps your CLS score.
Step 7: Audit Your Plugins
Plugins are where a lot of WordPress sites quietly get heavy. The number of plugins matters less than what each plugin does.
How to Run a Plugin Audit
- List every active plugin and write down what it actually does for you.
- Delete anything you no longer use. Deactivated plugins still sit on the server, so remove them completely.
- Look for overlap, like 2 SEO plugins, 2 caching plugins or 3 different slider plugins.
- On staging, deactivate plugins 1 at a time and re-test speed to find the heavy ones.
- Replace heavy plugins with lighter alternatives, or with features your host or theme already includes.
The WordPress optimization handbook gives the same advice: deactivate and delete unnecessary plugins and test how individual plugins affect performance.
Watch for These Common Speed Killers
- Page builders that load large CSS and JavaScript files on every page
- Social sharing and chat widgets that pull in third-party scripts
- Related posts plugins that run heavy database queries
- Security plugins that scan constantly on cheap shared hosting
- Backup plugins scheduled to run during peak traffic
That last problem is easy to fix. Schedule backups for your slowest hours. I cover lighter backup options in my roundup of the best WordPress backup plugins.
Step 8: Clean Up Your Database
Over time, the WordPress database fills up with clutter. Old post revisions, spam comments, expired transients and leftover data from deleted plugins all add weight.
What to Clean
- Post revisions: WordPress saves a copy every time you update a post. You can limit them with the WP_POST_REVISIONS setting in wp-config.php.
- Spam and trashed comments
- Expired transients, which are temporary cached data that plugins sometimes forget to delete
- Orphaned tables and options left behind by plugins you removed
- Autoloaded options, which load on every single page request
The WordPress optimization handbook recommends removing database clutter, limiting post revisions and using the InnoDB storage engine.
Do It Safely
Always take a fresh database backup before cleaning. Then use a well-known database cleanup plugin or WP-CLI to remove revisions, transients and spam. Be careful with “orphaned” data tools, because they sometimes flag data a plugin still needs.
On a WooCommerce store, never run cleanup tools on orders or customer tables unless you know exactly what they do.
Step 9: Optimize Fonts and Scripts
Once the server, caching and images are sorted, fonts and scripts are usually what stands between you and a good INP and LCP score.
Fonts
- Use 1 or 2 font families, not 5.
- Load only the weights you actually use.
- Host fonts locally instead of pulling them from a third-party server, if your theme or plugin allows it.
- Use font-display: swap so text shows right away while the font loads.
- Consider a system font stack for body text. It loads instantly because the font is already on the visitor’s device.
CSS and JavaScript
- Defer non-critical JavaScript so it does not block the page from rendering.
- Delay third-party scripts like chat widgets, heatmaps and social embeds until user interaction, where your caching plugin supports it.
- Remove unused CSS where your tools support it, but test carefully because it can break layouts.
- Minify CSS and JavaScript. Most caching plugins do this with a checkbox.
Third-party scripts are the sneaky part. Every tracking pixel, chat widget and embed adds work for the browser. Audit them every few months and remove anything that is not earning its keep.
Choose a Lightweight Theme
Your theme loads on every page. A lean, well-coded theme gives you a fast starting point, while a bloated multipurpose theme with every feature turned on fights you the whole way.
WordPress Speed Optimization Checklist by Impact
Here is the order I would work in, from biggest impact to smallest for a typical site.
| Fix | Typical impact | Effort | Helps which metric |
|---|---|---|---|
| Better hosting and current PHP | High | Medium | TTFB, LCP |
| Page caching | High | Low | TTFB, LCP |
| Image resizing, WebP or AVIF | High | Low | LCP |
| Correct lazy loading (not on hero image) | Medium | Low | LCP |
| CDN | Medium | Low | LCP for distant visitors |
| Object caching (Redis or Memcached) | Medium to high for stores and logged-in sites | Low to medium | TTFB, wp-admin speed |
| Plugin audit | Medium | Medium | INP, LCP |
| Fonts and scripts | Medium | Medium | LCP, INP, CLS |
| Database cleanup | Low to medium | Low | TTFB, wp-admin speed |
| Image dimensions set | Low effort fix | Low | CLS |
This is general guidance, not a promise of specific results. Your bottleneck might be different, which is exactly why Step 1 is measuring.
Speeding Up a WooCommerce Store
Stores have extra challenges because cart, checkout and account pages cannot be fully page cached. That means your server has to do real work on the pages that make you money.
For stores, I focus on:
- Hosting with enough CPU and memory for dynamic pages, not just cached pages
- A persistent object cache like Redis
- Excluding cart, checkout and account pages from page caching
- Keeping the plugin list lean, especially on checkout
- Optimizing product images, since product pages are often image heavy
I go deeper on what to look for in a store host in my guide to the best WooCommerce hosting.
Frequently Asked Questions
Why is my WordPress site so slow?
The most common causes are weak or overloaded hosting, no page caching, large unoptimized images, too many heavy plugins and third-party scripts. Run PageSpeed Insights and check TTFB first. A slow TTFB points to hosting or caching. A fast TTFB with slow LCP points to images, fonts or scripts.
What is a good PageSpeed score for WordPress?
Focus less on the score and more on passing Core Web Vitals in field data: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less. Google itself says chasing a perfect score just for SEO may not be the best use of your time.
Do I need a caching plugin if my host has caching?
Usually not for page caching. If your host provides server-level page caching, adding a second page cache plugin can cause conflicts. You may still use a plugin for image optimization or script settings, but follow your host’s recommendations.
Will a CDN speed up my WordPress site?
It usually helps, especially if your visitors are far from your server. A CDN serves images, CSS and JavaScript from locations near your visitors and takes load off your origin server. It works best together with page caching.
How many plugins is too many?
There is no magic number. 1 badly coded plugin can slow a site more than 20 lightweight ones. Audit what each plugin does, remove what you do not use, and test the heavy ones on staging.
When should I switch hosts for speed?
Switch when TTFB stays slow even with caching, the site slows down at busy times, you keep hitting resource limits, or your host cannot offer a current PHP version. At that point, plugins will not fix the problem.
Your Next Step
Speed is not about chasing a perfect score. Measure first, fix the biggest bottleneck, and work down the list: hosting and PHP, page caching, images, CDN, object caching, plugins, database, then fonts and scripts.
If the host turns out to be your bottleneck, write down what you need using my Start Here page and compare your options. Then follow my guide to moving WordPress to a new host without downtime.
Related Articles
- Best WordPress Hosting
- Managed WordPress vs Shared Hosting
- How to Migrate a WordPress Site to a New Host
- How to Backup a WordPress Site
- Cloudways Review
Trevor Fenner publishes Hosting Paradise and Ecommerce Paradise. His guides cover web hosting, website migration, backups, and software for online businesses.