How to Speed Up WordPress: What Actually Moves the Needle

Your WordPress site is slow and you know it. You have read ten articles about WordPress speed optimization. You installed a caching plugin, maybe two. You activated "lazy loading" somewhere. And your PageSpeed score is still in the 30s.

I get it. Most guides on how to speed up WordPress read like a plugin shopping list. Install this, toggle that, add another one. Before you know it, you have 40 plugins fighting each other and a site that is somehow slower than when you started.

I have spent years optimizing WordPress and WooCommerce sites for businesses here in Louisville and across Kentucky. The work I have done ranges from local restaurant sites running on shared hosting to WooCommerce stores processing hundreds of orders a week. And the pattern is always the same: a handful of changes make 90% of the difference. Everything else is noise.

This is the guide I wish someone had handed me years ago. No fluff. No plugin lists. Just the things that actually make WordPress faster, in the order that matters.

First, Measure Where You Actually Stand

Before you touch anything, you need a baseline. Otherwise you are guessing. And guessing is how people end up with six caching plugins and a broken site.

Two tools matter here:

• Google PageSpeed Insights - Free. Tests both mobile and desktop. Gives you Core Web Vitals scores and specific recommendations. This is what Google actually uses to evaluate your site speed for rankings.
• Your browser's developer tools (Network tab) - Open it, reload your page, and look at the waterfall. You will see exactly which files are loading, how big they are, and how long each one takes. This tells you where the bottleneck lives.

The number to watch first is Time to First Byte (TTFB). This measures how long it takes your server to start responding. If your TTFB is over 800ms, you have a server-side problem and no amount of front-end tweaking will fix it. For Largest Contentful Paint (LCP), your target is under 2.5 seconds on mobile.

Write down your current scores. Screenshot them. You will want to compare after each change so you know what actually helped and what did not.

Page Caching: The Single Biggest Win

Every time someone visits a WordPress page, the server runs PHP code, queries the database, assembles the HTML, and sends it back. That process takes time. On a busy server or a complex page, it takes a lot of time.

Page caching solves this by generating the HTML once and then serving that saved copy to every visitor after. Instead of rebuilding the page from scratch on every request, the server hands over a static file. It is the difference between cooking a meal from scratch for every customer versus having it ready on the counter.

For most WordPress sites, this one change cuts load time by 40-60%. That is not an exaggeration. I have seen WooCommerce sites go from a 4-second TTFB to under 500ms just by configuring page caching correctly.

Object Caching with Redis

Page caching handles visitors who see the same page. But what about logged-in users, WooCommerce cart pages, or dynamic content that cannot be page-cached? That is where object caching comes in.

Redis stores frequently-used database query results in memory so WordPress does not have to hit the database every time. For WooCommerce sites especially, this is a significant gain. Database queries that took 200ms now take 2ms.

Your host needs to support Redis. Most managed WordPress hosts (Cloudways, Kinsta, WP Engine) include it. If you are on basic shared hosting, you probably do not have this option, and that is one reason to consider upgrading.

Browser Caching

Browser caching tells a visitor's browser to save files locally so it does not download them again on the next visit. Your logo, your CSS file, your JavaScript, your fonts. None of those change between page loads, so the browser should not re-download them.

This is usually handled through your .htaccess file or your caching plugin's settings. Set cache expiration to at least 30 days for static assets. If you use Cloudflare, it handles a lot of this automatically.

Image Optimization: Smaller Files, Same Quality

Images are almost always the heaviest part of a WordPress page. A single unoptimized photo from your phone can be 3-5MB. Multiply that by six images on a page and you are asking visitors to download 20MB before they see anything useful.

Three things matter here:

Convert to WebP

WebP is a modern image format that is 25-35% smaller than JPEG at the same visual quality. Every major browser supports it now. If you are still serving JPEG or PNG images, you are sending larger files than necessary.

ShortPixel or Imagify can convert your existing image library to WebP automatically. They process images on their servers so your hosting is not affected.

Lazy Loading

Lazy loading delays the loading of images until a visitor scrolls to them. If you have a long page with 15 images, only the first 2-3 load initially. The rest load as the user scrolls down.

WordPress has built-in lazy loading as of version 5.5. But make sure your above-the-fold hero image is NOT lazy loaded. That image should load immediately. Lazy loading your hero image actually hurts your LCP score because the browser waits to load the most important visual element.

Responsive Images (srcset)

Your 2000px wide hero image does not need to be 2000px when someone views it on a 375px wide phone screen. The srcset attribute tells the browser to download the right size image for the device. WordPress generates multiple image sizes automatically when you upload, but your theme needs to use them correctly.

Check your theme. If your images are rendering at full size on mobile, you are wasting bandwidth and killing your mobile speed score.

CDN Configuration

A Content Delivery Network stores copies of your site's files on servers around the world. When someone in Louisville visits your site, they get files from a server in Nashville or Atlanta instead of wherever your hosting is located. When someone in Seattle visits, they get files from a West Coast server.

For a local business in Kentucky targeting Louisville customers, a CDN is less critical than for a national site. But it still helps because CDN servers are optimized for fast file delivery in ways that standard hosting is not.

Cloudflare is the easiest starting point. The free plan gives you a global CDN, browser caching headers, basic DDoS protection, and free SSL. For most small business WordPress sites, the free Cloudflare plan is more than enough. I set this up for nearly every contractor site I build because the security benefits alone are worth the five minutes it takes to configure.

Minification and Concatenation

Minification strips whitespace, comments, and unnecessary characters from your CSS and JavaScript files. A 100KB CSS file might become 70KB. That adds up across multiple files.

Concatenation combines multiple CSS or JavaScript files into fewer files, which reduces the number of HTTP requests the browser has to make. Instead of downloading 12 separate JavaScript files, the browser downloads 2.

Most caching plugins handle this. WP Rocket does it well. Autoptimize is a free option that focuses specifically on minification and concatenation. One warning: aggressive JavaScript optimization can break things. If your site looks wrong or features stop working after enabling minification, start by turning off JavaScript optimization and leaving CSS minification on. CSS rarely breaks. JavaScript often does.

Database Optimization

Your WordPress database accumulates junk over time. Post revisions, spam comments, transient options, orphaned metadata from plugins you deleted months ago. On a site that has been running for a few years, this can add up to tens of thousands of unnecessary rows.

A bloated database means slower queries, which means slower page generation, which means slower load times.

What to clean up:

• Post revisions - WordPress saves every draft and edit by default. A single post can have 50+ revisions. Limit revisions to 5 in wp-config.php and delete the old ones.
• Spam and trashed comments - Delete them. They are sitting in your database taking up space.
• Transients - Temporary data that plugins store. Often the plugins that created them are long gone but the data remains.
• Unused tables - Plugins create database tables when installed and often do not clean them up when deleted. WP-Optimize can identify and remove these.
• Autoloaded data - Some plugins dump large amounts of data into the options table and mark it as autoloaded, meaning it gets pulled into memory on every single page load. This is one of the most common hidden performance killers.

WP-Optimize or Advanced Database Cleaner handle all of this. Run a cleanup monthly. Set it and forget it.

The Plugin Problem

Here is where most "how to speed up WordPress" guides fail. They tell you to install 8 new plugins to make your site faster. The irony is thick.

Every plugin you add is code that runs on your server. Some plugins are lightweight. Some are not. A single poorly coded plugin can add 500ms to your load time by loading JavaScript on every page, running database queries on every request, or calling external APIs synchronously.

Deactivate plugins you are not using. Replace heavy plugins with lighter alternatives. And resist the urge to install a plugin for every small feature. Sometimes 10 lines of custom code in your functions.php is better than a plugin that loads 200KB of JavaScript on every page.

Hosting Matters More Than You Think

You can optimize everything on this list and still have a slow site if your hosting is the bottleneck. Shared hosting means your site shares server resources with hundreds of other sites. When those other sites get traffic spikes, your site slows down.

For a WordPress site that needs to perform well, here is my general recommendation:

• Basic business site (under 10K monthly visitors) - A quality shared host like SiteGround or A2 Hosting is fine. Avoid the cheapest tier.
• WooCommerce or high-traffic site - Managed WordPress hosting (Cloudways, Kinsta, or WP Engine). The built-in server-level caching, staging environments, and Redis support make a measurable difference.
• If your TTFB is consistently over 1 second - Your hosting is likely the problem. No plugin will fix a slow server.

I have moved retail and e-commerce sites from bargain shared hosting to Cloudways and watched TTFB drop from 1.8 seconds to 300ms with zero other changes. Hosting is the foundation. If the foundation is bad, nothing built on top of it will perform well.

The Order That Actually Matters

If you are going to speed up your WordPress site, do it in this order. Each step builds on the last:

1. Measure your baseline - PageSpeed Insights, TTFB, and LCP. Write them down.
2. Evaluate your hosting - If TTFB is over 1 second, upgrade first. Everything else is a band-aid.
3. Set up page caching - One plugin. Configured correctly. This is your biggest single win.
4. Optimize images - Convert to WebP, enable lazy loading (except hero images), check srcset.
5. Add a CDN - Cloudflare free plan at minimum.
6. Clean the database - Remove revisions, transients, orphaned data.
7. Audit plugins - Use Query Monitor. Remove or replace the heavy ones.
8. Minify CSS and JavaScript - Carefully. Test after each change.
9. Measure again - Compare to your baseline. Celebrate the wins.

Most sites will see dramatic improvement after steps 2 through 4. Steps 5 through 8 are refinement. Do not skip the measurement steps. They keep you honest and prevent you from breaking things without realizing it.

What I Have Seen in the Real World

A WooCommerce store I worked on last year had a mobile PageSpeed score of 22. TTFB was 2.3 seconds. The owner had been told by a previous developer to "just add a caching plugin." They had three caching plugins installed. Three. All fighting each other.

Here is what I did: removed all three caching plugins, moved them to better hosting, installed one caching plugin configured properly, set up Redis for object caching, optimized their product images (they were uploading 4000px photos straight from a DSLR), added Cloudflare, and cleaned a database that had 180,000 post revisions.

The result: mobile PageSpeed went from 22 to 81. TTFB dropped from 2.3 seconds to 340ms. The site went from losing visitors to converting them. That is what focused, methodical optimization looks like versus the "install more plugins" approach.

I see similar patterns with businesses across Louisville. A salon booking site bogged down by a theme that loaded 14 JavaScript files on every page. A common website mistake I write about often. A contractor's site where the contact form plugin alone added 1.2 seconds to load time. These are not rare edge cases. This is what most WordPress sites look like under the hood.

When to Stop Optimizing and Start Rebuilding

Sometimes a WordPress site is so loaded with technical debt that optimizing it costs more than starting fresh. If your theme is a bloated page builder with hardcoded scripts, if you have 50+ plugins and half of them are abandoned, if your database is a graveyard of old migrations and broken tables, it might be time to have an honest conversation about building something new.

I wrote about why I build most of my client sites without WordPress for exactly this reason. Static HTML sites load in under a second with zero optimization because there is nothing to optimize. No database. No PHP. No plugins. For a lot of small businesses, that is the better path forward.

But if your business needs WordPress for its CMS, for WooCommerce, or for specific functionality that requires it, then optimizing what you have is absolutely worth the effort. Follow the steps above in order, measure your results, and you will see a real difference.

Your website's speed is not a vanity metric. It directly affects how many people stay, how many convert, and how Google ranks you. Fix it once, maintain it monthly, and move on to growing your business.