Your WordPress site scores 38 on Lighthouse. You installed a caching plugin. It's now 42. You're frustrated. Here are 15 fixes that actually move the needle — the ones we apply on every client site audit.
This isn't a list of generic tips you've already read. These are the exact optimizations we run through on every WordPress performance audit, ordered by impact. Some are free. Some require a plugin. A few require a developer. All of them work.
How We Measure Impact
Before we start, let's agree on what "fast" means:
- Largest Contentful Paint (LCP): Under 2.5 seconds. This is how fast your main content loads.
- Cumulative Layout Shift (CLS): Under 0.1. This is how much your page jumps around while loading.
- Interaction to Next Paint (INP): Under 200ms. This is how fast your page responds to clicks.
- Lighthouse Performance Score: 90+ on mobile. Desktop is easy — mobile is where most sites fail.
Every fix below includes an expected impact rating: Low (1-5 points), Medium (5-15 points), or High (15-30+ points).
Part 1: Server & Hosting
Fix 1: Upgrade to PHP 8.2+
Impact: Medium-High | Difficulty: Easy | Cost: Free
PHP 8.2 is 15-25% faster than PHP 7.4 in real-world benchmarks. Most quality hosts let you switch PHP versions from your control panel in under a minute.
How to do it:
- Check your current PHP version: Tools > Site Health > Info > Server
- Test compatibility: Install the "PHP Compatibility Checker" plugin
- Switch via your host's control panel (cPanel, Plesk, or custom dashboard)
- Clear all caches after switching
Watch out for: Old plugins that haven't been updated for PHP 8.x. The compatibility checker will flag these. Update or replace them before switching.
Fix 2: Move to Application-Level Hosting
Impact: High | Difficulty: Medium | Cost: $25-100/month
Shared hosting ($5/month GoDaddy, Bluehost, Hostinger basic) is the single biggest performance bottleneck for most WordPress sites. You're sharing CPU, RAM, and disk I/O with hundreds of other sites.
The upgrade path:
| Hosting Tier | Examples | Typical LCP | Monthly Cost |
|---|---|---|---|
| Shared hosting | GoDaddy, Bluehost, Hostinger basic | 4-8 seconds | $3-10 |
| Managed WordPress | Cloudways, SiteGround GoGeek, A2 Turbo | 1.5-3 seconds | $25-50 |
| Premium managed | Kinsta, WP Engine, Flywheel | 1-2 seconds | $30-100 |
| VPS (self-managed) | DigitalOcean, Vultr, Linode | 1-2 seconds | $12-50 |
For most business sites doing under 100K monthly visits, Cloudways ($14/month for a 1GB DigitalOcean droplet) gives you 80% of the performance of a $100/month Kinsta plan.
Fix 3: Enable Server-Level Caching
Impact: High | Difficulty: Easy | Cost: Free (with good hosting)
Plugin-level caching (WP Super Cache, W3 Total Cache) is fine. Server-level caching is better. The difference: server-level caching serves the cached HTML before WordPress even loads. PHP never executes. The database never gets queried.
- Cloudways: Varnish cache built-in. Enable it in the dashboard.
- Kinsta: Edge caching on their CDN. Automatic.
- Nginx FastCGI Cache: If you manage your own server, this is the gold standard.
- LiteSpeed Cache: If your host runs LiteSpeed/OpenLiteSpeed (many shared hosts do), the LiteSpeed Cache plugin leverages server-level caching.
Pro tip: Don't stack caching plugins. Pick one. If your host has server-level caching, you likely don't need a caching plugin at all — just a cache-clearing mechanism.
Fix 4: Add a CDN
Impact: Medium-High | Difficulty: Easy | Cost: Free-$20/month
A CDN (Content Delivery Network) serves your static files — images, CSS, JS, fonts — from servers physically close to your visitors.
- Cloudflare Free: DNS-level CDN, basic optimization, DDoS protection. Good enough for most sites.
- Cloudflare Pro ($20/month): Adds image optimization (Polish), Mirage (lazy loading for mobile), and better cache rules.
- BunnyCDN ($1/month for most sites): If you don't want Cloudflare's DNS proxy model, BunnyCDN is the fastest pure CDN at the lowest cost.
Impact on LCP: If your audience is geographically distributed (e.g., India + US + UK), a CDN can cut LCP by 500ms-2 seconds for distant visitors.
Part 2: Images & Media
Fix 5: Serve Images in AVIF/WebP Format
Impact: High | Difficulty: Easy | Cost: Free
JPEG and PNG are dinosaurs. AVIF is 50% smaller than JPEG at equivalent quality. WebP is 25-30% smaller. Your site is probably serving megabytes of unoptimized images.
Best plugins:
- ShortPixel (free tier: 100 images/month): Converts to AVIF/WebP, serves the right format based on browser support. Also compresses originals.
- Imagify: Similar to ShortPixel. The free tier is more generous (20MB/month).
- EWWW Image Optimizer: Handles conversion locally (no API limits) but uses more server resources.
How it works: These plugins generate AVIF/WebP versions of your images and serve them via <picture> elements or .htaccess rewrite rules. Old browsers get the JPEG fallback automatically.
Fix 6: Implement Proper Lazy Loading
Impact: Medium | Difficulty: Easy | Cost: Free
WordPress 5.5+ has native lazy loading via the loading="lazy" attribute. But it's not enough:
- Above-the-fold images should NOT be lazy loaded. Your hero image, logo, and any image visible without scrolling should load immediately. Lazy loading your LCP image kills your LCP score.
- Add
fetchpriority="high"to your hero/LCP image. This tells the browser to prioritize downloading it.
How to fix it:
// In your theme's functions.php
add_filter('wp_img_tag_add_loading_attr', function($value, $image, $context) {
// Don't lazy load images in the header/hero
if ($context === 'the_content') {
// First image in content should not be lazy loaded
static $first = true;
if ($first) {
$first = false;
return false; // Removes loading="lazy"
}
}
return $value;
}, 10, 3);
Or use the Perfmatters plugin ($24.95/year), which gives you granular control over lazy loading per element.
Fix 7: Use Responsive Image Sizes
Impact: Medium | Difficulty: Medium | Cost: Free
WordPress generates multiple image sizes on upload (thumbnail, medium, large, full). But many themes serve the full-size image regardless of the container size. A 2400px wide image in a 600px container is wasted bandwidth.
Check for this issue: Right-click any image > Inspect. If the rendered size is much smaller than the intrinsic size, you're serving oversized images.
Fix:
- Ensure your theme uses
wp_get_attachment_image()orthe_post_thumbnail()with a defined size, not just the full URL. - Add custom image sizes that match your layout breakpoints:
add_image_size('card-thumb', 400, 300, true);
add_image_size('hero-desktop', 1200, 600, true);
add_image_size('hero-mobile', 600, 400, true);
- Regenerate thumbnails after adding new sizes (use the "Regenerate Thumbnails" plugin).
Fix 8: Replace Video Embeds with Facades
Impact: Medium-High | Difficulty: Easy | Cost: Free
A single YouTube embed adds 500KB-1.5MB of JavaScript, CSS, and iframe overhead. If you have 3 YouTube videos on a page, you're loading 1.5-4.5MB of YouTube's code before your visitor even clicks play.
The fix: Use a lightweight facade that shows the video thumbnail and only loads the full YouTube player when clicked.
- WP YouTube Lyte (free plugin): Replaces embeds with a facade automatically.
- Perfmatters: Has a YouTube lazy load feature built in.
- Manual: Replace the iframe with a thumbnail image + play button, and load the iframe on click with JavaScript.
On one client WooCommerce site, replacing 4 YouTube embeds with facades dropped the page weight from 6.2MB to 1.8MB and improved LCP from 5.1s to 2.3s.
Part 3: Code & Assets
Fix 9: Remove Unused CSS and JavaScript
Impact: High | Difficulty: Medium | Cost: $0-49/year
The average WordPress site loads 15-30 plugins. Each one enqueues its CSS and JS on every page — even pages where it's not needed. A contact form plugin loading its 50KB stylesheet on your homepage? That's dead weight.
Tools:
- Asset CleanUp (free): Shows you every CSS/JS file loaded per page. Lets you disable them selectively. This is the single most impactful free optimization tool.
- Perfmatters ($24.95/year): Same concept, cleaner UI, plus script manager for granular control.
- WP Rocket ($59/year): Includes unused CSS removal (generates used CSS per page type).
How to use Asset CleanUp:
- Install and activate.
- Visit each major page type (homepage, single post, product page, contact page).
- The plugin shows every CSS/JS file loaded. Disable the ones that page doesn't need.
- Test thoroughly after each change.
Typical savings: 200KB-800KB per page. That's enormous.
Fix 10: Optimize Font Loading
Impact: Medium | Difficulty: Medium | Cost: Free
Google Fonts loaded via <link> in the <head> are render-blocking. Every font family you add is another round-trip to Google's servers before your text renders.
Fixes (in order of impact):
- Self-host your fonts. Download them and serve from your own domain. Eliminates the DNS lookup + connection to fonts.googleapis.com. Use the google-webfonts-helper tool.
- Use
font-display: swapin your@font-facedeclarations. Text renders immediately with a fallback font, then swaps when the custom font loads. - Preload critical fonts. Add
<link rel="preload" href="/fonts/your-font.woff2" as="font" type="font/woff2" crossorigin>to your<head>. - Limit font weights. Every weight (400, 500, 600, 700) is a separate file. Most sites need 2-3 weights max.
- Use WOFF2 only. WOFF2 has 99%+ browser support. Don't serve WOFF, TTF, or EOT.
Fix 11: Inline Critical CSS
Impact: Medium | Difficulty: Easy (with plugin) | Cost: $0-59/year
Critical CSS is the minimal CSS needed to render above-the-fold content. Inlining it in the <head> means the browser can render the visible page immediately without waiting for external stylesheets.
- WP Rocket: Generates and inlines critical CSS automatically. One-click setup.
- Autoptimize + CriticalCSS.com: Free plugin + $2/month API for automatic critical CSS generation.
- Manual: Use the Chrome DevTools Coverage tab to identify critical CSS, then inline it with a
<style>tag in your theme'sheader.php.
Fix 12: Defer Non-Critical JavaScript
Impact: Medium | Difficulty: Easy | Cost: Free
By default, JavaScript in the <head> blocks HTML parsing. The browser stops rendering until the script is downloaded and executed. Most scripts don't need to run until after the page loads.
Add defer or async to non-critical scripts:
defer: Downloads in parallel, executes after HTML parsing. Use for most scripts.async: Downloads in parallel, executes immediately when ready. Use for analytics/tracking scripts.
How:
- Flying Scripts (free plugin): Delays JavaScript execution until user interaction (scroll, click, keypress). Dramatically improves initial load metrics.
- WP Rocket: Has a "Delay JavaScript execution" feature that does the same thing.
- Manual: Use
wp_script_add_data($handle, 'strategy', 'defer')in WordPress 6.3+.
Part 4: Database
Fix 13: Clean Up Post Revisions and Transients
Impact: Low-Medium | Difficulty: Easy | Cost: Free
WordPress saves every revision of every post. A post edited 50 times has 50 revision rows in the database. Multiply that across hundreds of posts, and your wp_posts table is bloated with data nobody uses.
Fix:
- Limit revisions in
wp-config.php:define('WP_POST_REVISIONS', 5); - Delete old revisions with WP-Optimize (free plugin) or WP-Sweep.
- Clean expired transients: WP-Optimize does this automatically. Transients are temporary cached values that sometimes don't get cleaned up.
- Optimize database tables: WP-Optimize can optimize (defragment) your MySQL tables in one click.
Impact on WooCommerce: WooCommerce stores create massive wp_options tables with autoloaded transients. A WooCommerce store with 5,000+ products can have an wp_options table that takes 500ms+ to query. Cleaning autoloaded data can cut TTFB by 200-400ms.
Fix 14: Audit Autoloaded Data in wp_options
Impact: Medium (especially WooCommerce) | Difficulty: Medium | Cost: Free
The wp_options table has an autoload column. Every row marked autoload = yes is loaded into memory on every single page load. Plugins love marking their options as autoloaded — even when they shouldn't.
Audit it:
SELECT SUM(LENGTH(option_value)) as total_bytes
FROM wp_options
WHERE autoload = 'yes';
If the result is over 1MB, you have a problem. We've seen sites with 5-10MB of autoloaded data.
Common culprits:
- Abandoned plugin settings (plugin deleted but options remain)
- Action Scheduler logs (WooCommerce)
- Expired transients that weren't cleaned
- Logging plugins storing data in options
Fix: Use the Query Monitor plugin to identify slow queries on wp_options, then selectively set non-critical autoloaded options to no or delete orphaned plugin data.
Fix 15: WooCommerce-Specific Database Optimization
Impact: High (WooCommerce only) | Difficulty: Medium-Hard | Cost: Free-$99
WooCommerce sites have unique performance challenges because of how they store product data, order data, and session data.
Key optimizations:
Enable HPOS (High-Performance Order Storage): WooCommerce 8.2+ supports custom order tables instead of storing orders as posts. This dramatically reduces
wp_postsandwp_postmetatable sizes. Enable in WooCommerce > Settings > Advanced > Features.Use a persistent object cache: Install Redis or Memcached and use the Object Cache Pro plugin ($99/year) or the free Redis Object Cache plugin. This caches database queries in memory, reducing database load by 50-80%.
Disable WooCommerce cart fragments on pages that don't need them: Cart fragments make an AJAX request on every page load to update the cart icon. If a page doesn't have a cart icon, this request is wasted.
add_action('wp_enqueue_scripts', function() {
if (!is_cart() && !is_checkout() && !is_product()) {
wp_dequeue_script('wc-cart-fragments');
}
});
- Limit WooCommerce analytics data retention: WooCommerce stores analytics data indefinitely. Set a retention period in WooCommerce > Settings > Advanced > WooCommerce.com.
Summary Impact Table
| Fix | Impact | Difficulty | Cost | Priority |
|---|---|---|---|---|
| 1. PHP 8.2+ | Medium-High | Easy | Free | Do first |
| 2. Better hosting | High | Medium | $25-100/mo | Do first |
| 3. Server caching | High | Easy | Free | Do first |
| 4. CDN | Medium-High | Easy | Free-$20/mo | Do first |
| 5. AVIF/WebP images | High | Easy | Free | Do first |
| 6. Smart lazy loading | Medium | Easy | Free | Week 1 |
| 7. Responsive images | Medium | Medium | Free | Week 1 |
| 8. Video facades | Medium-High | Easy | Free | Week 1 |
| 9. Remove unused CSS/JS | High | Medium | $0-49/yr | Week 1 |
| 10. Font optimization | Medium | Medium | Free | Week 2 |
| 11. Critical CSS | Medium | Easy | $0-59/yr | Week 2 |
| 12. Defer JavaScript | Medium | Easy | Free | Week 2 |
| 13. Revision cleanup | Low-Medium | Easy | Free | Week 2 |
| 14. Autoload audit | Medium | Medium | Free | Week 3 |
| 15. WooCommerce DB | High | Medium-Hard | $0-99 | Week 3 |
Monthly Speed Maintenance Checklist
Speed isn't a one-time fix. Plugins get updated, content gets added, and performance degrades. Run this monthly:
- Run Lighthouse audit on 3 key pages (homepage, top landing page, product/service page)
- Check Core Web Vitals in Google Search Console (CWV report)
- Review recently installed/updated plugins for performance impact
- Clean up post revisions and expired transients (WP-Optimize)
- Check autoloaded data size in wp_options (keep under 1MB)
- Verify CDN is serving static assets (check response headers)
- Test on a real mobile device, not just Lighthouse emulation
- Review server response time (TTFB under 200ms)
- Check for broken images or 404 assets (use Screaming Frog or Broken Link Checker)
- Update PHP version if a new stable release is available
FAQ
Which caching plugin is best for WordPress?
It depends on your hosting. If you're on LiteSpeed hosting, use LiteSpeed Cache (free, tightly integrated). For any other host, WP Rocket ($59/year) is the best all-in-one solution. If budget is zero, a combination of WP Super Cache + Asset CleanUp gets you 80% of the way there.
Does page speed actually affect SEO rankings?
Yes, but nuance matters. Google uses Core Web Vitals as a ranking signal, but it's a tiebreaker, not a primary factor. A slow page with great content will outrank a fast page with thin content. That said, page speed directly affects bounce rate and conversion rate — which indirectly affect SEO through engagement signals.
My Lighthouse score is different every time I test. Why?
Lighthouse scores fluctuate because of network conditions, server load, browser extensions, and test environment variability. Always test in an incognito window, run 3-5 tests, and average the results. Use PageSpeed Insights (which runs Lighthouse on Google's servers) for more consistent results.
How fast should my WordPress site be?
Targets for a good user experience: LCP under 2.5 seconds on mobile, TTFB under 200ms, total page weight under 2MB, Lighthouse performance score 85+ on mobile. These are achievable for any WordPress site with the right hosting and optimizations.
Is WP Rocket worth $59/year?
For most site owners, yes. It replaces 3-5 individual plugins (caching, critical CSS, lazy loading, JS deferral, database cleanup) with one well-integrated tool. The time saved in configuration alone justifies the cost. If you're technically savvy and enjoy configuring individual tools, you can replicate 90% of WP Rocket's features with free plugins.
Should I switch from WordPress to a faster platform?
Only if WordPress is genuinely holding you back. A properly optimized WordPress site loads in under 2 seconds. The problem isn't WordPress — it's poorly configured hosting, 40 plugins, unoptimized images, and bloated themes. Fix those first. Replatforming is expensive and rarely justified for performance reasons alone.
How do I speed up WooCommerce specifically?
Start with fixes 13-15 in this guide (database and WooCommerce-specific optimizations). Then: enable HPOS, install a persistent object cache (Redis), disable cart fragments on non-shop pages, and use a lightweight theme (GeneratePress, Kadence) instead of a page builder theme. WooCommerce on optimized hosting with Redis can serve product pages in under 1 second.
Your Site Deserves Better Than a 42
Every point on your Lighthouse score represents real users who waited too long, bounced, and went to a competitor. Speed isn't vanity — it's revenue.
We audit WordPress sites for free. Get your speed report and action plan within 48 hours. No sales pitch, no commitment. Just a clear list of what's slow and how to fix it.