The short answer
Most slow WordPress sites come down to cheap or crowded hosting, no working page cache, no CDN, heavy images, an old PHP version, or too many plugins and third-party scripts. Test first so you know which one is yours, then fix the foundations in order. If you only watch two numbers, get LCP under 2.5 seconds and TTFB under 0.8 seconds.
- Test first: check your Core Web Vitals and TTFB before you change anything.
- Get good hosting, in the country most of your visitors are in.
- Use one caching plugin, such as WP Rocket or FlyingPress. Never run two.
- Put Cloudflare in front as your CDN. The free plan is enough for most small sites.
- Shrink your pages: compress images, use JPEG or WebP for photos and lazy load below the fold.
- Run HTTPS everywhere and check you’re on HTTP/2 or HTTP/3.
- Run the highest PHP version your site supports, after a backup and a test.
- Clean up your plugins: update the ones you need and delete the ones you don’t.
Want us to look at it for you? Request a FREE site audit and one of our team will review your site and tell you how we can help.
Most people fix a slow WordPress site the wrong way. They install another plugin, change a few settings they read about on a forum, run a speed test, then do it all again. It’s stabbing in the dark. The site stays slow, the score barely moves, it still fails Core Web Vitals, and every so often something breaks.
We’ve optimised more than 5,000 WordPress sites since we started WP Speed Fix in 2016. The ones that end up fast all follow the same order: work out what’s actually causing the problem, fix the foundations (hosting, caching, CDN, page weight), then tidy up the rest. This guide walks through that order in 8 steps.
Prefer to watch? The video below covers the same steps.
Free checklist: want something to work through as you go? Our 34-point WordPress speed checklist is further down this page. It follows the same 8 steps, with every item rated by impact so you know what to do first.
On this page
- The short answer
- Why is your WordPress site slow?
- How to fix a slow WordPress site: the 8 steps
- 1. Test first: diagnose before you fix
- 2. Get good hosting
- 3. Use one caching plugin
- 4. Put a CDN in front: Cloudflare
- 5. Shrink your pages: images and lazy loading
- 6. HTTPS, HTTP/2 and HTTP/3
- 7. Run the highest PHP version your site supports
- 8. Update plugins, remove the ones you don’t use and old code
- Advanced fixes
- The free WordPress speed checklist (34 points)
- How site speed affects SEO
- Frequently asked questions
- Use The WPSpeedFix Service | We’ll Fix Your Site or Your Money Back
- About the author
- More guides
Why is your WordPress site slow?
Slow WordPress sites nearly always come back to the same handful of causes. Roughly in order of how often we see them:
- Cheap, crowded hosting, or hosting in a different country to most of your visitors
- No page caching, or a caching plugin that’s installed but not actually working
- No CDN, so every single request lands on your server
- Heavy pages: uncompressed images, photos saved as huge PNGs, sliders and videos loading up front
- An old PHP version, or a host that doesn’t support HTTP/2
- Too many plugins, outdated plugins, and leftover code from ones removed years ago
- Third-party scripts such as chat widgets, tracking pixels, popups and review badges
- Database and backend problems, mostly on older or larger sites and WooCommerce stores
The catch is you can’t tell which of these is your problem just by looking at the site. That’s why step one is testing, not tweaking.
How to fix a slow WordPress site: the 8 steps
Work through these in order. Each one is explained in detail further down.
- Test first: diagnose before you fix
- Get good hosting
- Use one caching plugin
- Put a CDN in front: Cloudflare
- Shrink your pages: images and lazy loading
- HTTPS, HTTP/2 and HTTP/3
- Run the highest PHP version your site supports
- Update plugins, remove the ones you don’t use and old code
1. Test first: diagnose before you fix
Every fix in this guide works, but only on the problem it’s meant for. A site whose server takes three seconds to respond won’t get fast from image compression. So before you change anything, find out where the time is going.
Core Web Vitals is your real speed data
When someone visits your site in a Chrome-based browser, Google records how fast each page loaded and pools it into the Chrome User Experience Report (CrUX). Core Web Vitals is built from that data, so it’s the speed your real visitors actually get. That makes it the best data set to diagnose from.
A PageSpeed Insights score or GTmetrix grade is a lab test: one simulated page load from one location. It’s handy for spotting specific issues, but a site can score 100 and still fail Core Web Vitals. Don’t chase the score.
As a rule of thumb, you need around 50 to 100 visits a day for Google to have Core Web Vitals data on your site. Below that, lab tests are what you’ve got.
Free tools to start with
- Core Web Vitals report – our free report showing your real-visitor data and which metrics pass or fail.
- WordPress speed test – our free lab test, with recommendations in plain English.
- PageSpeed Insights – Google’s tool. Shows field data (when there’s enough traffic) plus lab results, with more technical advice.
The numbers to aim for
| Metric | Good | What it measures |
|---|---|---|
| Largest Contentful Paint (LCP) | 2.5 seconds or less | When the main content (usually the hero image or headline) appears |
| Interaction to Next Paint (INP) | 200 milliseconds or less | How quickly the page reacts to a click or tap |
| Cumulative Layout Shift (CLS) | 0.1 or less | How much the layout jumps around while loading |
| Time to First Byte (TTFB) | 0.8 seconds or less | How long the server takes to start sending the page (not a Core Web Vital, but it feeds into LCP) |
If you only watch two numbers, make them LCP and TTFB. Get LCP under 2.5 seconds and TTFB under 0.8 seconds (lower is better) and the site will generally be fast. They also tell you where to look: a slow TTFB points at hosting and caching (steps 2 to 4), while a slow LCP with a healthy TTFB usually means the page is too heavy (step 5). We have separate guides on reducing TTFB and improving LCP.
Write down your starting numbers and take a full backup before you touch anything. Then change one thing at a time and retest.
2. Get good hosting
Poor hosting is the most common cause of a slow WordPress site we see. Most people are on a $2 or $5 a month plan, and that kind of host is a low-cost airline: you’ll get there eventually, squeezed in with a crowd of other sites.
Good hosting doesn’t cost a fortune. Instead of the price of a cup of coffee a month, budget around the price of a nice lunch. For a business site, that’s small next to the enquiries a slow site quietly loses.
The two hosts we recommend sit at opposite ends of the spectrum, so pick based on how hands-on you want to be:
- Cloudways – a VPS you manage yourself. You choose the cloud provider and data centre, and the server stack comes tuned for WordPress. Good value if you’re happy looking after it yourself.
- WP Alpha – fully managed WordPress hosting for small businesses. The server side is looked after for you, so you can get on with running the business.
If you’d rather a premium managed host and don’t mind paying more, Kinsta is a solid choice. At the budget end, SiteGround is a reasonable step up from the bargain-basement hosts. In our experience the big budget brands, GoDaddy, Bluehost and HostGator among them, are where most of the slow sites we’re asked to fix are hosted. There’s more detail in our fastest WordPress hosting comparison.
Host in the country your visitors are in
If your customers are in Australia and your server is in the US, every page load starts with a long round trip across the Pacific. Pick a data centre in or near the country where most of your visitors are. A CDN (step 4) narrows the gap but doesn’t close it.
Check TTFB before and after any hosting move. It’s the clearest sign of whether the new host is doing its job.
3. Use one caching plugin
Without caching, WordPress builds every page from scratch for every visitor: it runs the PHP, queries the database, then assembles and sends the HTML. A page cache does that work in advance, so visitors get a finished page straight away. It’s one of the quickest ways to bring TTFB down.
We recommend one of two plugins:
- WP Rocket – the DIY-friendly option, with sensible defaults and hard to break. If you’re not technical, go for this one. A single-site licence is US$59.95 a year at the time of writing.
- FlyingPress – a little faster in our experience, but more technical to set up. Better suited to developers.
Never run two caching plugins. They compete over the same files and rules, and the usual result is a slower site or a broken one. Before installing a new plugin, deactivate and delete the old one (WP Super Cache, W3 Total Cache, LiteSpeed Cache or whatever’s there) and check it hasn’t left rules behind in your .htaccess file.
Host-level caching counts too. Many managed hosts cache pages on the server, and some block certain caching plugins for that reason. If yours does, ask support how to set up a plugin alongside it.
Have a backup and FTP or file manager access ready first. Occasionally a caching plugin clashes with a theme or plugin, and renaming its folder gets the site back up in a minute. For a wider comparison, see our guide to the best WordPress caching plugins.
4. Put a CDN in front: Cloudflare
A content delivery network (CDN) keeps copies of some or all of your site on servers spread across the globe and serves each visitor from the nearest one. Files travel a shorter distance, and many requests never reach your hosting at all.
We recommend Cloudflare. Its free plan is excellent and is enough for most small sites: fast DNS, a CDN for your images, CSS and JavaScript, free SSL certificates, and protection from attacks and junk bot traffic.
The next step up is Automatic Platform Optimization (APO), which is US$5 a month on the free plan and included in Cloudflare’s paid plans. APO caches your full HTML pages across Cloudflare’s network, so most page views are served without touching your hosting. It’s switched on through the Cloudflare WordPress plugin. If you’re running paid traffic, APO is definitely worth the $5: you’re paying for every click, and a traffic spike lands on Cloudflare instead of your server.
Never stack two CDNs. If your host has its own CDN and you also run the site through Cloudflare, the two caching layers get in each other’s way and problems become much harder to track down. Pick one. If your host has a built-in Cloudflare integration, use that rather than adding a separate Cloudflare account on top.
5. Shrink your pages: images and lazy loading
Page weight is the total size of everything a visitor downloads to see a page, and images are usually the biggest part of it. Aim to keep pages under 3MB.
Compress your images
Install an image optimisation plugin, run it across your existing media library, and let it compress new uploads automatically. The two we use:
- EWWW Image Optimizer – has a free mode that compresses images using your own hosting’s CPU, so it’s a good option on a tight budget. The paid plans move that work off your server.
- ShortPixel – compresses on its own servers, so it doesn’t load up your hosting, and gets files small without a visible drop in quality.
Stick with lossless or light compression. A slightly smaller file isn’t worth a blurry product photo. More detail is in our WordPress image compression guide.
Use the right format and size
Photos should be JPEG (or WebP, which both plugins can create for you), not PNG. A photo saved as a PNG is often several times the size of the same photo as a JPEG. Keep PNG for logos and graphics that need transparency.
Resize before you upload, too. A 4,000 pixel wide phone photo shown at 800 pixels wide is dead weight every visitor downloads.
Lazy load what’s below the fold
Lazy loading means images and videos further down the page only load when the visitor scrolls near them. WordPress has lazy loaded images natively since version 5.5, and WP Rocket and FlyingPress extend it to iframes and videos.
The exception is the main image at the top of the page. That’s usually your LCP element, and lazy loading it delays exactly what Core Web Vitals is timing, so exclude it. For YouTube embeds, set your caching plugin to show a preview image that only loads the player when someone clicks play.
6. HTTPS, HTTP/2 and HTTP/3
Your site should run on HTTPS only. Google has used HTTPS as a ranking signal since 2014, browsers label plain HTTP pages as not secure, and in practice the faster modern protocols, HTTP/2 and HTTP/3, only run over HTTPS.
Force HTTPS everywhere
An SSL certificate alone isn’t enough: every HTTP request needs to redirect to HTTPS. Most hosts have a “force HTTPS” setting, and Cloudflare has an “Always Use HTTPS” switch. In WordPress, check that both addresses under Settings > General start with https://.
To test it, type http://yourdomain.com into your browser. You should land on the https:// version with no warnings. Fix any mixed content (images or scripts still loading over http://), which shows up in your browser’s developer console.
Once HTTPS works everywhere, including any subdomains you plan to cover, turn on HSTS (HTTP Strict Transport Security). It tells browsers to skip the HTTP redirect and go straight to HTTPS on return visits. Don’t turn it on earlier: browsers remember the setting, so anything broken on HTTPS stays broken for those visitors until you fix it.
Check for HTTP/2 and HTTP/3
With the old HTTP/1.1 protocol, the browser fetches files over a handful of connections and the rest queue up. HTTP/2 downloads many files at once over one connection, and HTTP/3 copes better again with patchy mobile connections. Any decent host supports HTTP/2, and Cloudflare can serve HTTP/3 with one setting.
To check, open your browser’s developer tools, go to the Network tab, right-click a column heading and turn on Protocol. You should see h2 or h3. If you’re stuck on HTTP/1.1 and your host can’t fix it, that’s another reason to move.
7. Run the highest PHP version your site supports
WordPress is written in PHP, and newer PHP versions generally run it faster. Older versions also stop receiving security fixes, which is a problem in its own right.
You can find the version your site is on under Tools > Site Health > Info > Server in the WordPress dashboard. Compare it with the minimum WordPress recommends on its requirements page and the versions still supported on php.net. Most hosts let you switch versions in their control panel. If you can’t find the setting, ask support.
Don’t just flip the switch on an older site. Each PHP release removes functions that older themes and plugins may still rely on, and when that happens pages break or go blank. Take a backup, update your theme and plugins first, then make the change on a staging copy (most good hosts give you one) and click through your key pages, forms and checkout. Once it all works there, change the live site. If your host can’t offer a current PHP version at all, go back to step 2.
8. Update plugins, remove the ones you don’t use and old code
Older sites collect clutter: a plugin installed for a one-off job, a page builder you stopped using, three different form plugins. Every active plugin can add scripts, styles and database queries to your pages.
- Take an inventory. For each plugin, ask what the site would lose without it. If the answer is nothing, delete it.
- Keep the rest updated. Updates fix bugs and often improve performance. Back up first, and update big plugins (page builders, WooCommerce) one at a time.
- Replace abandoned plugins. If a plugin hasn’t been updated in a couple of years, look for a maintained alternative.
- Clear out old code. Some plugins leave database tables behind after you delete them, and old themes and builders leave shortcodes and scripts in your content.
- Find the heavy ones. The free Query Monitor plugin shows which plugins are running the most database queries on a slow page.
Watch for plugins that pull in code from other companies’ servers, such as chat widgets, popups and heatmaps. That code is outside your control and often the heaviest thing on the page (see third-party scripts below).
Advanced fixes
The 8 steps fix most slow WordPress sites. If your numbers are still poor after them, the cause is usually one of these.
Database problems
Older WordPress databases often still use MyISAM tables. Converting them to InnoDB generally makes them faster and more reliable under load, and clearing out old revisions, expired transients and oversized autoloaded options helps too. Our guide to speeding up WordPress database queries walks through it. Back up first.
Object caching with Redis
Page caching can’t help logged-in users, carts or the admin area, because those pages differ for each person. Object caching keeps database query results in memory so WordPress doesn’t repeat them on every load. Many hosts, Cloudways included, offer Redis, and a plugin such as Redis Object Cache connects WordPress to it.
Third-party scripts
Tracking pixels, chat widgets, review badges and heatmaps are some of the heaviest code on a typical page, and they often drag down INP. Instead of adding them through plugins or your theme, move them into Google Tag Manager and fire the non-essential ones on the Window Loaded trigger. That way they load after your content instead of competing with it.
Slow WordPress admin
When the dashboard is slow but the front end is fine, the cause is usually the database, a plugin doing heavy work on every admin page, or the Heartbeat API. See our guide on fixing a slow WordPress admin.
WooCommerce
Carts, checkouts and logged-in customers can’t be served from a page cache, so hosting, object caching and the database matter even more on a store. If your extensions support it, turn on High-Performance Order Storage (HPOS). Our WooCommerce speed optimisation guide covers the rest, and our WooCommerce caching plugins guide explains how to cache a store without breaking the cart.
More guides
- Cloudflare rules for WordPress – block bad bots and junk traffic before it reaches your server.
- Speed up WordPress without plugins – for when you’d rather fix things at the server and theme level.
The free WordPress speed checklist (34 points)
This is the checklist we work through on real optimisation jobs, in the same 8 steps as the guide above. Take a backup before you touch anything.
Impact shows how much each item moves the needle. Work down from Extreme and Very High. Anything rated Medium or Low is worth doing, it will not rescue a slow site on its own.
Step 1 checklist: test first
| Action item | Impact | How to check, what to do |
|---|---|---|
| Take a full backup of files and database before you change anything | Very High | Caching plugins and database work are the two changes most likely to bite. Take a full backup, confirm you can restore it, and make sure you have hosting panel or SFTP access so you can pull a change back out if the site goes blank. We use BlogVault – blogvault.net |
| Check your Core Web Vitals field data first | Very High | Core Web Vitals is Google's record of real page loads from Chrome visitors to your site. It is the real speed of your website, so it is the data to diagnose from, not a PageSpeed score. Run the free Core Web Vitals report. Google needs roughly 50 to 100 visits a day before it holds a data set for a site; below that, use the lab test in the next rows. |
| Check LCP is under 2.5 seconds and TTFB is under 0.8 seconds | Very High | These two numbers tell you most of the story. Largest Contentful Paint (LCP) is when the main content appears, and Google rates under 2.5 seconds as good. Time to first byte (TTFB) is how long the server takes to start sending the page: aim for under 800 milliseconds, and faster is better. Pass both and the site will generally feel fast. A slow TTFB points at hosting, caching or the database. A slow LCP with a good TTFB points at the page itself, usually images or render-blocking code. |
| Run a lab speed test and write the numbers down | High | A lab test is a single simulated load. It is good for spotting what is heavy on a page and useless as a goal in itself, so do not chase a score of 100. Run the free WordPress Speed Test (no opt-in, about 90 seconds), note load time, total page size and TTFB, then re-test after every change so you know which fix moved the number. |
| Work out where the site is slow | Very High | Front end or admin? Logged-out visitors or only logged-in users? Every page, or one template? The answer changes the fix. Slow everywhere including the admin points at hosting or the database. One slow page points at whatever plugin, embed or image is on that page. |
Step 2 checklist: good hosting
| Action item | Impact | How to check, what to do |
|---|---|---|
| Stop paying $2 to $5 a month for hosting | Extreme | A $2 a month host is a low-cost airline: it gets there, slowly, crammed onto one server with thousands of other sites. Budget around the price of a nice lunch a month rather than the price of a coffee. Check your plan and invoice. If it is a cheap shared plan with unlimited everything, that is very likely your bottleneck. |
| Move to Cloudways (a VPS you manage) or WP Alpha (fully managed) | Extreme | They sit at opposite ends of the spectrum. Cloudways – cways.net gives you your own VPS that you look after through their panel, a good fit if you are happy to be hands-on. WP Alpha – wpalpha.com is managed WordPress hosting, where the server side is looked after for you. Pick on how hands-on you want to be, then migrate on a quiet day and re-test. |
| Host the site in the country where most of your visitors are | Very High | Distance adds delay to every request that is not served from a CDN, and it shows up directly in TTFB. We often find Australian businesses on US servers wondering why the site drags. Check where your traffic comes from in your analytics, then check where the server is, and pick a data centre close to your customers. |
| Confirm OPcache is enabled on the server | High | Without OPcache, PHP recompiles WordPress on every request. It is a server setting, not a plugin. Check Tools > Site Health > Info > Server, a phpinfo page, or ask your host. Good hosts have it on by default; if yours cannot turn it on, that is another reason to move. |
Step 3 checklist: one caching plugin
| Action item | Impact | How to check, what to do |
|---|---|---|
| Install one page caching plugin: WP Rocket or FlyingPress | Extreme | Page caching builds each page ahead of time, so the PHP and database work is already done when the visitor arrives. WP Rocket – wprocketplugin.com is the DIY-friendly one and the pick if you are not technical. FlyingPress – flyingpress.net is a little faster but takes more technical setup. |
| Never run two caching plugins, and count your host's cache | Very High | Two caching plugins fight over the same files and rules, and it is one of the most common causes of broken or slower sites we see. Host-level caching counts as one: if your host already caches pages, either use that or set the plugin up the way the host documents, not both blindly. Deactivate and delete any leftover caching plugins. |
| Confirm pages are actually served from cache | High | Open the site in a private window (logged out) and check the response headers in your browser's developer tools for a cache hit, or view source for the caching plugin's footer comment. TTFB on a cached page should drop to a few hundred milliseconds. If it does not, something is bypassing the cache. |
Step 4 checklist: a CDN in front
| Action item | Impact | How to check, what to do |
|---|---|---|
| Put Cloudflare's free plan in front of the site, and use only one CDN | Very High | Cloudflare – cloudflare.com serves your files from servers near each visitor, handles your DNS, and adds a firewall against bad bots and attacks. The free plan is excellent. Before you switch nameservers, copy every DNS record across, or email can break. Do not stack a second CDN behind it from your host or a plugin; two layers are often slower than one and much harder to debug. |
| Add Cloudflare APO if the site makes money or runs paid traffic | High | Automatic Platform Optimization (APO) caches the whole HTML page at Cloudflare's edge, so most visits never reach your server. It is US$5 a month on the free plan and included on the paid plans. It moves a lot of the work off your hosting and lets the same server handle far more visitors. On paid traffic it is definitely worth it. |
| Set Cloudflare cache and firewall rules for WordPress | Medium | Make sure the admin, logged-in users and anything personal (cart, checkout, account pages) bypass the cache, and block the junk bot traffic that eats server time. Our guide has the rules we use. |
Step 5 checklist: smaller pages
| Action item | Impact | How to check, what to do |
|---|---|---|
| Compress your images with EWWW or ShortPixel | Very High | EWWW – ewww.io/plans/ref/332 has a free option that compresses on your own hosting CPU, a good choice on a tight budget. ShortPixel – shortpixel.com/h/af/DOSKA1B500675 does the work on its own servers. Run a bulk optimise over the existing media library, not just new uploads, and let it create WebP versions. Stick to lossless or a light setting; blurry product photos cost more than they save. |
| Keep total page weight under about 3MB | High | Check total transferred size in the speed test. Pages much over 3MB are slow on mobile and, in our experience, tend to rank worse. Fix the biggest files first: hero images, sliders, background videos and embedded media are the usual culprits. |
| Use JPEG for photos and resize images before you upload them | High | A photo saved as a PNG is often many times the size of the same photo as a JPEG. Keep PNG for logos and graphics with flat colour. Resize each image to roughly the largest size it displays at; a 4000 pixel camera photo shown at 800 pixels wide is wasted weight. |
| Lazy load images and video below the fold, never above it | Medium | WordPress adds lazy loading to images by default, and WP Rocket and FlyingPress extend it to iframes and video embeds. Check that the hero image and anything else on the first screen is NOT lazy loaded, because that delays LCP. |
Step 6 checklist: HTTPS, HTTP/2 and HTTP/3
| Action item | Impact | How to check, what to do |
|---|---|---|
| Force HTTPS everywhere in a single redirect hop | High | Type yourdomain.com into a browser: it should land on the https:// version in one 301 redirect, not a chain through www and back. On Cloudflare, Always Use HTTPS does this in one switch. While you are there, fix mixed content: old http:// image and script URLs in posts get blocked or flagged by browsers, so update them with a search and replace. |
| Turn on HSTS once HTTPS works on every page | Medium | HSTS tells browsers to go straight to HTTPS, which skips the redirect on repeat visits. Only turn it on after every page, and every subdomain you include, works over HTTPS, because browsers will refuse the http:// version for as long as the max-age you set. |
| Confirm your server supports HTTP/2, and ideally HTTP/3 | High | HTTP/2 loads many files over one connection, and HTTP/3 does better again on patchy mobile networks. The speed test flags HTTP/2, http3check.net checks HTTP/3. Cloudflare can serve HTTP/3 to visitors even if your host does not. If your host still serves HTTP/1.1, that is a reason to move. |
Step 7 checklist: the highest PHP version
| Action item | Impact | How to check, what to do |
|---|---|---|
| Check which PHP version the site runs | High | WordPress shows it under Tools > Site Health > Info > Server, and your hosting panel will have a PHP version setting. Compare it against the version WordPress currently recommends on its requirements page. If your host will not let you change PHP, that is a hosting problem. |
| Test the newest version on staging, then switch the live site | Very High | Copy the site to staging, change the PHP version there, then click through the key pages, forms and checkout. Watch the error log or Query Monitor for fatal errors and deprecation warnings; old themes and abandoned plugins are the usual failures. Once staging is clean, switch live and note the old version so you can roll back. |
Step 8 checklist: plugins and old code
| Action item | Impact | How to check, what to do |
|---|---|---|
| Update WordPress, your theme and plugins on a schedule | High | Updates often carry performance fixes as well as security patches. Back up first. Minor releases are usually safe to auto update; anything that changes how the site looks or the checkout works should be updated on staging first. |
| Delete plugins you don't use, and find the heavy ones with Query Monitor | High | Take an inventory and delete what you no longer need, rather than leaving it deactivated. Then install Query Monitor (free), load a slow page and sort queries by component: it names the plugin responsible instead of you switching things off at random. Live chat, page builders, social feeds and sliders are common offenders. |
| Remove old code: dead tracking snippets, theme hacks and .htaccess clutter | Medium | Look in the theme header and footer, functions.php and .htaccess for code nobody can account for: tracking tags for tools you cancelled, hand-added speed rules that duplicate your caching plugin, and long lists of old redirects. Move bulk redirects into a redirect plugin and strip the rest. |
Advanced fixes checklist
| Action item | Impact | How to check, what to do |
|---|---|---|
| Convert every MyISAM table to InnoDB | High | MyISAM locks a whole table while one row is written, so on a busy site writes queue and everything waits. InnoDB locks per row. It shows up hardest where page cache cannot help: the admin, checkout and membership pages. Servebolt Optimizer converts in one click. On a database of several GB, do it outside peak hours and get a developer on it. |
| Clean the database: expired transients, revisions and autoloaded options | Medium | Neglected sites carry tens of thousands of dead transient rows and post revisions, and plugins leave large autoloaded options behind after you remove them. WP-Optimize or WP Rocket clear the routine junk. Our database guide covers the autoload check. |
| Turn on object caching (Redis) if the site is database heavy | High | Redis, driven by the Redis Object Cache plugin, answers repeat database queries from memory. It helps the parts page caching cannot touch: the admin, cart, checkout and anything behind a login. Your host has to provide Redis. Set a cache key salt in wp-config.php so sites on the same server cannot share cache entries. |
| Load third-party scripts through Google Tag Manager on Window Loaded | High | Chat widgets, ad pixels, heatmaps and analytics extras compete with your own content. Move them out of plugins and theme code into Google Tag Manager and fire the non-essential ones on the Window Loaded trigger, so they load after the page instead of in front of it. |
| Fix a slow admin separately from the front end | Medium | Page caching and a CDN do nothing for wp-admin. A slow dashboard usually comes down to hosting, the database, object caching or one plugin calling an external service on every admin page load. Query Monitor on the slow admin screen narrows it down. |
| WooCommerce: keep cart, checkout and account out of the page cache | High | Those pages are personal to each shopper and must never be cached; caching plugins exclude them by default, so check yours does. Stores also need the database and object caching work above more than most sites. The WooCommerce speed guide and our WooCommerce caching plugins guide (wpspeedfix.com/woocommerce-caching-plugins) cover the store-specific fixes. |
| Monitor uptime and Core Web Vitals so you catch it going backwards | Medium | A site that is down has no speed at all. Run uptime monitoring, and re-check the Core Web Vitals report each month. Speed usually slips back through a plugin update, a new marketing tag or a big new image. |
How site speed affects SEO
Speed won’t push weak content to the top of Google, but it can hold good content back in three ways:
- Core Web Vitals. Google uses Core Web Vitals in its ranking systems as part of page experience. Passing won’t beat a better answer, but when two pages are otherwise close, a poor experience can cost you.
- Uptime. A site that’s down has no speed at all, and pages that regularly throw errors are hard for Google to crawl and keep indexed. Cheap hosting is where we see the most outages.
- Page weight. In our experience, sites with lots of pages over 3MB tend to rank worse, and sites with many pages in the 5 to 10MB range struggle more. Lighter pages are also quicker for Google to crawl, which matters on larger sites.
Then there’s the part that isn’t about Google at all: a faster site turns more of the visitors you already have into enquiries.
Frequently asked questions
Why is my WordPress site so slow?
Usually cheap hosting, no page caching, heavy images or too many plugins. Test before you change anything: a slow TTFB points at hosting and caching, while a slow LCP with a good TTFB points at page weight.
Does hosting really make a difference to WordPress speed?
Yes, more than any other single factor in our experience. Caching and a CDN only hide so much of a slow server. If TTFB is still well over 0.8 seconds with caching on, the hosting is the likely problem.
Which caching plugin should I use?
WP Rocket if you want something easy to set up and hard to break, FlyingPress if you’re technical and want a bit more speed. Use one, never both, and check whether your host already caches pages first.
Is the free Cloudflare plan enough?
For most small sites, yes. If you’re running paid traffic or your hosting struggles under load, add APO for US$5 a month so whole pages are served from Cloudflare.
How fast should a WordPress site load?
Aim to pass Core Web Vitals on real visitor data: LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, with TTFB under 0.8 seconds. Those matter more than any speed test score.
Will deleting plugins speed up my site?
Removing plugins you don’t need usually helps, especially ones that load scripts on every page. What each plugin does matters more than how many you have, so find the heavy ones with Query Monitor rather than deleting at random.
Use The WPSpeedFix Service | We’ll Fix Your Site or Your Money Back
You can avoid all these issues and any server-side issues by using our simple WordPress speed optimization service. With WP Speed Fix, we’ll take a look at all the aspects of your site that may be slowing it down and find out exactly what you need to do to fix them.
We’ll go through all of the options you have and what we recommend. If we can’t do it, we’ll tell you straight away. You won’t find any hidden charges or unexpected fees when you use WP Speed Fix for your WordPress optimization needs.
What to expect from WPSpeedFix
Our team consists of WordPress specialists who have worked with some of the biggest websites in the world. All of our fixes are reversible and completely safe for your site.
In just a few days, we’ll have everything fixed and ready for you to go live with faster load times! We can’t wait to help you get your site running better than ever again.
Whether that’s because you’re hosting on a slow server, need to update your WordPress version, want to move to a faster hosting package, or just want us to review and fix any code that may be slowing down your site you should contact us!
We have worked with countless customers from all over the world and have seen it all. Our service isn’t available publicly as we’d rather work with you personally.
WP Speed Fix will save your business time, money and resources that would otherwise be wasted on slow loading times. Overloading servers or under-optimizing files are just a few of the problems that have been solved by our WordPress speed optimization service. So, what are you waiting for? Contact us today!





