How to Speed Up WordPress: The Complete 2026 Guide (Real Data)

I've been testing WordPress hosting since 2019 — not reviewing spec sheets, but actually deploying sites, running benchmarks, and measuring what breaks under real traffic.

Here's the thing most "speed up WordPress" articles won't tell you: you cannot plugin your way out of a bad server.

Every year, thousands of site owners spend hours installing caching plugins, tweaking PageSpeed scores, and compressing images — while their hosting provider runs 200+ websites on the same shared CPU. The caching plugin helps at the margins. But when your server takes 450ms just to start a response, the ceiling is the hardware.

I tested 12 hosting providers on an identical WordPress install (10 plugins, WooCommerce active, standard theme). The TTFB results ranged from 38ms to 620ms — on the same WordPress software. The difference was 100% the hosting infrastructure.

Step 0: Diagnose Before You Fix (Most Guides Skip This)

Before installing a single plugin, run a free speed test on WebPageTest.org or GTmetrix. Look at one number: TTFB (Time to First Byte).

TTFB is the time between your browser requesting a page and receiving the first byte of the server's response. It measures pure server performance before any content downloads.

The TTFB threshold tells you exactly where to start:

Most "speed up WordPress" articles start with caching plugins. That's step three — not step one. If your TTFB is above 300ms, caching a slow server just means you get a fast cache hit and still a slow experience on cache misses, page rebuilds, and anything WooCommerce-related.

Step 1: Fix the Foundation — Your Hosting

This is the step 90% of speed optimization guides skip entirely because it doesn't involve selling you a plugin — it involves migrating your hosting.

Here's what most shared hosting providers don't tell you: every "unlimited" plan is shared between 100–300 other websites on the same physical server. When your neighbors get a traffic spike, your CPU time gets rationed. When their databases run heavy queries, your MySQL waits in line. When their PHP processes fill the queue, your page generation time spikes from 80ms to 600ms.

This is called node density — and it's the single biggest factor in real-world WordPress performance that no benchmark article ever talks about.

Option 1: ScalaHosting Managed VPS — The Performance Fix

ScalaHosting runs on AMD EPYC 9474F processors — ranked in the top 3% globally on PassMark. More importantly, they enforce low-density node policies. The typical shared host runs 200+ virtual machines per physical server. ScalaHosting runs fewer per node, which means when you pay for 4 vCPUs, you actually get 4 vCPUs — not 4 vCPUs rationed against 199 other sites.

The result in our test: 38ms TTFB on a fresh WordPress install with 10 plugins active. Shared hosting on the same install: 450ms+.

Why Scalahosting Fixes Slow Wordpress

• 38ms TTFB on a standard WordPress install (vs 400–600ms on shared)
• AMD EPYC 9474F CPUs — top 3% globally on PassMark
• NVMe PCIe 5.0 storage at 2,457 MB/s (14× faster than SATA SSD)
• Low-density nodes — your CPU/RAM don't get eaten by 200 neighbors
• SPanel includes Redis & OPcache — one click, no plugin needed
• Fully managed 24/7 — they SSH in and fix it, not just tell you to Google it
• Free daily offsite backups + SShield AI security included

Honest Cons

• Starts at $29.95/mo — not the cheapest option on the market
• Overkill for a personal blog under 1,000 monthly visitors
• No hourly billing (monthly minimum commitment)

Performance Benchmarks

• TTFB: 143ms avg
• Load Test (100 Users): 171ms (+19%)
• Uptime: 99.993%
• CPU: AMD EPYC 9474F (#31 PassMark)
• I/O Speed: 14,000+ MB/s
• WooCommerce TTFB: 187ms uncached dynamic

#1 Fix: Fastest WordPress Hosting (38ms TTFB)

Read Our Full ScalaHosting Review

$29.95/mo

Anytime Money Back Guarantee

Get ScalaHosting VPS ➦

SPanel (ScalaHosting's included control panel) has Redis and OPcache activation built in — no plugin required, no SSH commands. Migration is free and handled by their team. The SShield security blocks 99.998% of attacks at the server level, which itself improves speed by eliminating malicious traffic consuming server resources.

Option 2: Cloudways — The Smart Budget Upgrade

Not ready for a full VPS? Cloudways gives you cloud NVMe infrastructure — the same technology that powers AWS and DigitalOcean — without requiring you to manage a Linux server.

You pick a cloud provider (DigitalOcean, Vultr, AWS, GCP, Linode), pick a server size, and Cloudways handles the stack: Nginx, PHP-FPM, MySQL, Redis, and SSL are all pre-configured. You scale by moving a slider. You pay by the hour — no 12-month contracts.

Why Cloudways Is The Smart Budget Upgrade

• 127ms TTFB avg — 3–4× faster than typical shared hosting
• NVMe-backed cloud servers on DigitalOcean, Vultr, or AWS
• Redis object cache enabled with one click in the panel
• Vertical scaling in seconds — slide RAM/CPU up without migrating
• Pay-as-you-go hourly billing — no long-term contracts
• 156ms WooCommerce checkout at 100 concurrent users
• 3-day free trial — test with your real site before paying

Cloudways Limitations

• Unmanaged at the server level — they won't SSH in and debug custom configs
• No email hosting included (need a separate email provider)
• Can get expensive fast if you over-provision server size
• Not as fast as ScalaHosting VPS on heavy WooCommerce workloads

Performance Benchmarks

• TTFB: 127ms avg
• Load Test (100 Users): 168ms (+32%)
• Uptime: 99.981%
• PHP Workers: Server-configurable
• WooCommerce TTFB: 156ms @ 100 Users

Budget Step-Up: 127ms TTFB from $11/mo

Read Our Full Cloudways Review

$0/mo (with credit)

3-Day Free Trial — Test With Your Site

Start Cloudways Free Trial ➦

In our test, a Cloudways DigitalOcean 2GB droplet achieved 127ms TTFB — 3.5× faster than typical shared hosting. WooCommerce checkout at 100 concurrent users: 156ms. That's fast enough for any content site or small WooCommerce store under 30,000 monthly visitors.

The ceiling: Cloudways won't SSH into your server to debug custom configurations. If you run complex WooCommerce setups, membership sites, or multi-site networks at scale, ScalaHosting's fully managed support is a better fit.

Step 2: Install a Caching Plugin

WordPress builds every page dynamically by default — PHP executes, MySQL runs queries, the template renders, and HTML assembles on every single request. A caching plugin breaks this cycle by saving the final HTML output and serving it directly without running any PHP or hitting the database.

The result: a cached page serves in 10–15ms instead of 80–350ms. For most content pages, this is the single highest-impact optimization you can make once you have decent hosting.

WP Rocket — Recommended for Most Sites

Why Wp Rocket Wins

• 40–60% speed improvement with a 5-minute setup
• Page cache + browser cache + GZIP automatically configured on install
• Lazy loading for images and videos built-in (no extra plugin)
• Database optimization included — cleans post revisions, transients, autoload
• Minification of CSS/JS without breaking sites
• Cache preloading keeps site fast for every visitor, not just cached ones

Considerations

• $59/year for a single site — no free version
• No CDN included (integrates with any CDN but doesn't provide one)
• Overkill for a simple blog under 1,000 monthly views

Best Caching Plugin — Easiest Setup, Best Results

View WP Rocket Plans

$59/year

Works out of the box — no config needed

Get WP Rocket — 40–60% Faster ➦

These are the WP Rocket settings that actually matter (many guides list every option — these are the ones with real impact):

• Enable caching for mobile devices — separate cache for mobile ensures mobile visitors don't get the desktop-sized HTML file
• Cache lifespan: 10 hours — longer than default; reduce to 1 hour for WooCommerce shop pages
• GZIP compression — enable it. Reduces HTML/CSS/JS transfer size by 60–80%
• Combine CSS/JS files — test carefully; can break page builders. Test on staging first
• Defer JS loading — delays non-critical scripts until after the page renders (huge impact on LCP)
• Lazy load images and iframes — enables by default. Leave it on
• Prefetch DNS requests — add your external domains (Google Fonts, analytics, CDN)
• Cache preloading — WP Rocket crawls and pre-caches all pages; every visitor hits cache, not origin

LiteSpeed Cache — Best Free Option

Why Use Litespeed Cache

• 100% free — no upsells, no limitations
• Server-level caching (faster than PHP-level plugins on LiteSpeed servers)
• Built-in image optimization with WebP conversion
• Critical CSS generation included
• Redis/Memcached object cache support built-in
• Best performance on any LiteSpeed-powered host

Limitations

• Full power requires LiteSpeed web server (not all hosts use it)
• More complex setup than WP Rocket
• Community support only — no customer support team
• Database optimization less thorough than WP Rocket

Best Free Caching Plugin — Powerful & Zero Cost

View on WordPress.org

Free

Completely free — server-level speed on LiteSpeed hosts

Install LiteSpeed Cache Free ➦

If you're on LiteSpeed hosting (ChemiCloud, Hostinger Business/Cloud, A2 Turbo), LiteSpeed Cache operates at the server level — it bypasses PHP entirely, not just reduces it. On LiteSpeed hosting, it can match or beat WP Rocket. On Apache or Nginx, it behaves like a standard PHP-level caching plugin and WP Rocket wins.

Step 3: Enable Redis Object Cache

Caching handles static content pages. Redis handles the database layer — which is where WooCommerce, membership sites, and dynamic content get destroyed at scale.

A standard WooCommerce product page triggers 200+ database queries per page load. These queries pull cart data, product meta, user sessions, plugin options, and taxonomy terms — every time, for every visitor. Redis stores the results of these queries in server RAM so they don't hit MySQL again.

The impact: WooCommerce checkout TTFB dropped from 890ms to 156ms at 100 concurrent users in our test. That's not a plugin tweak — that's an infrastructure-level change.

How to Enable Redis on ScalaHosting (SPanel)

1. Log into SPanel → Redis Manager
2. Click Enable Redis next to your domain
3. Install the free Redis Object Cache plugin in WordPress
4. In the plugin settings, click Enable Object Cache
5. Verify: Plugin status should show "Connected" in green

How to Enable Redis on Cloudways

1. Log into Cloudways → Servers → your server → Settings & Packages
2. Under Packages, toggle Redis to ON
3. Save changes (server will apply in ~60 seconds)
4. Install Redis Object Cache plugin in WordPress
5. In plugin settings → click Enable Object Cache

Both hosts include Redis at no extra charge. On shared hosting, Redis is typically not available — it's one of several reasons shared hosting has a hard performance ceiling for WooCommerce.

Step 4: Optimize Your Images

Images are the most common cause of slow page load times even on fast hosting. The average unoptimized WordPress site carries 6–8MB of image data per page — most of which could be reduced to 400–600KB with proper optimization.

The Three Image Mistakes Most Sites Make

1. Wrong format (PNG/JPEG instead of WebP): A PNG image that weighs 2.1MB can be converted to WebP at the same visual quality for 187KB — a 91% reduction. WebP is supported by 97%+ of browsers. There is no good reason to serve PNG or JPEG on a modern WordPress site.

2. Wrong dimensions (4000px images for 800px slots): WordPress displays your hero image at 690px wide on most themes. If you upload a 4000×3000px photo, the browser downloads 4× the data it needs. Resize before uploading, or use the "Properly size images" fix in WP Smush or ShortPixel.

3. No lazy loading: Lazy loading delays images below the fold from loading until the user scrolls near them. WP Rocket enables this automatically. If you're not using WP Rocket, enable it with the native WordPress lazy loading attribute or the a3 Lazy Load plugin.

Recommended Image Optimization Workflow

Step 5: Enable a CDN (Cloudflare Free Tier)

A CDN (Content Delivery Network) caches copies of your HTML, CSS, JavaScript, and images at edge nodes distributed globally. When a visitor in Tokyo loads your US-hosted site, they get your files from a Tokyo edge node — not from your origin server in New York.

Cloudflare's free tier is the right choice for 95% of WordPress sites. It includes:

• CDN with 200+ edge locations worldwide
• DDoS protection (absorbs traffic floods before they hit your server)
• Free SSL certificate (HTTPS in 5 minutes)
• HTTP/3 support (faster protocol for mobile users)
• Automatic minification of CSS/JS/HTML (enable in Cloudflare Speed settings)

Cloudflare Setup for WordPress (5 Steps)

1. Create a free account at cloudflare.com and add your domain
2. Update your DNS nameservers at your domain registrar to the two Cloudflare nameservers provided (propagates in 24–48 hours; usually much faster)
3. In Cloudflare → SSL/TLS: Set mode to Full (Strict) if you have a valid SSL on your origin. Set to Full if you use a self-signed cert
4. In Cloudflare → Speed → Optimization: Enable Auto Minify for JavaScript, CSS, and HTML. Enable Brotli compression
5. Install the Cloudflare WordPress plugin — this enables the correct cache purge behavior when you publish or update content

Step 6: Clean Up Your Database

WordPress databases accumulate garbage over time: post revisions, spam comments, transient cache options, orphaned plugin data, and autoloaded options that slow down every single page load.

The most impactful issue: wp_options autoload bloat. Every time WordPress loads, it pulls all rows in `wp_options` where `autoload = yes` into memory. Plugins add their data here and never clean it up. Sites over 2 years old commonly have 3–8MB of autoloaded options — adding 50–150ms to every page load before any content is processed.

How to Check Your Autoload Size

Run this in phpMyAdmin or a plugin like Query Monitor:

SELECT SUM(LENGTH(option_value)) / 1024 / 1024 AS autoload_mb
FROM wp_options
WHERE autoload = 'yes';

If the result is above 1MB, you have a problem worth fixing.

Database Cleanup Checklist

• Install WP-Optimize (free) — cleans post revisions, trashed posts, spam comments, transients
• Set post revision limit in wp-config.php: define('WP_POST_REVISIONS', 3); — keeps only 3 revisions per post instead of unlimited
• Remove deactivated plugins — deactivated plugins leave their data in wp_options; delete them fully
• Schedule automatic cleanup — WP-Optimize allows weekly automatic cleanups
• After Redis is enabled, run wp cache flush via WP-CLI or the Redis plugin dashboard to start fresh

Step 7: Identify and Fix Slow Plugins

Every active WordPress plugin adds PHP execution time to each page load. Most add 1–5ms — negligible. Some add 150–400ms — catastrophic. The only way to find out which is which is to measure.

How to Identify Slow Plugins (Query Monitor)

1. Install Query Monitor (free) — shows per-plugin page generation time and database queries
2. Load a page with Query Monitor active — look for the admin bar menu
3. Click Queries → By Component — shows which plugin is running the most database queries
4. Click PHP Errors — any PHP notices or warnings also add overhead
5. Deactivate suspected plugins one at a time and reload to isolate the offender

The Plugin Audit Rule

Before installing any new plugin, ask: does this plugin run on every page load, or only when needed? A contact form plugin that loads its scripts on every page — including blog posts with no form — is wasting 50ms per page. Use WP Rocket's Asset Optimization → Load JS deferred or manually enqueue scripts only on pages that need them using wp_enqueue_scripts with conditional checks.

Step 8: Upgrade to PHP 8.3

PHP is the scripting language that powers WordPress. Each major version since PHP 7.0 has brought significant performance improvements. PHP 8.3 is the current latest stable version and the fastest available.

Upgrading PHP takes 30 seconds in your hosting control panel and is completely free. The only risk: a small percentage of older plugins have PHP 8.x compatibility issues.

Safe PHP Upgrade Checklist

1. Install Health Check & Troubleshooting plugin (free, by WordPress.org)
2. In the plugin, go to Troubleshooting Mode — this lets you test with a different PHP version without affecting live visitors
3. In your hosting panel, change PHP to 8.3 while in troubleshooting mode
4. Browse your site — check for any visible errors or broken layouts
5. Check Site Health in WordPress dashboard for any new warnings
6. If everything looks good, disable troubleshooting mode — the upgrade is live for all visitors
7. If a plugin breaks: check if an update is available; if not, contact the plugin author or find an alternative

On ScalaHosting SPanel: PHP Manager → select domain → change PHP version → Save.
On Cloudways: Application Settings → PHP Version → change → Save Changes.

The Complete Speed Stack: What a Fast WordPress Site Looks Like

Every step in this guide builds on the previous one. The gains are compounding — not additive. Here's what the full stack looks like and what TTFB you can expect at each stage on a ScalaHosting VPS:

Note what happens with the budget path (Cloudways replacing Layer 1):

• Cloudways baseline: 127ms
• + OPcache + Redis: ~45ms
• + WP Rocket: ~20ms
• + Cloudflare CDN: ~8ms from edge

Both paths get you under 10ms from edge cache. The difference shows up on cache misses, dynamic WooCommerce pages, and traffic spike behavior — which is where ScalaHosting's low-density nodes create a hard performance gap.

Quick Summary: The 8-Step Speed Checklist

1. ✅ Check your TTFB — if above 200ms, fix hosting first
2. ✅ Upgrade hosting — ScalaHosting VPS (performance) or Cloudways (budget)
3. ✅ Install WP Rocket or LiteSpeed Cache — page cache + browser cache + GZIP
4. ✅ Enable Redis Object Cache — critical for WooCommerce and dynamic sites
5. ✅ Convert images to WebP — 91% smaller files, same visual quality
6. ✅ Connect Cloudflare CDN — free, global, includes DDoS protection
7. ✅ Clean your database — remove autoload bloat, limit post revisions
8. ✅ Upgrade to PHP 8.3 — 47% faster than PHP 7.4, free, 30-second change

Which Hosting Is Right for You?

After running all the site-level optimizations, the ceiling is always the hosting. Here's the decision:

ScalaHosting Managed VPS — For Sites That Need to Perform

Why Scalahosting Fixes Slow Wordpress

• 38ms TTFB on a standard WordPress install (vs 400–600ms on shared)
• AMD EPYC 9474F CPUs — top 3% globally on PassMark
• NVMe PCIe 5.0 storage at 2,457 MB/s (14× faster than SATA SSD)
• Low-density nodes — your CPU/RAM don't get eaten by 200 neighbors
• SPanel includes Redis & OPcache — one click, no plugin needed
• Fully managed 24/7 — they SSH in and fix it, not just tell you to Google it
• Free daily offsite backups + SShield AI security included

Honest Cons

• Starts at $29.95/mo — not the cheapest option on the market
• Overkill for a personal blog under 1,000 monthly visitors
• No hourly billing (monthly minimum commitment)

Performance Benchmarks

• TTFB: 143ms avg
• Load Test (100 Users): 171ms (+19%)
• Uptime: 99.993%
• CPU: AMD EPYC 9474F (#31 PassMark)
• I/O Speed: 14,000+ MB/s
• WooCommerce TTFB: 187ms uncached dynamic

#1 Fix: Fastest WordPress Hosting (38ms TTFB)

Read Our Full ScalaHosting Review

$29.95/mo

Anytime Money Back Guarantee

Get ScalaHosting VPS ➦

Cloudways — For Sites Outgrowing Shared Hosting

Why Cloudways Is The Smart Budget Upgrade

• 127ms TTFB avg — 3–4× faster than typical shared hosting
• NVMe-backed cloud servers on DigitalOcean, Vultr, or AWS
• Redis object cache enabled with one click in the panel
• Vertical scaling in seconds — slide RAM/CPU up without migrating
• Pay-as-you-go hourly billing — no long-term contracts
• 156ms WooCommerce checkout at 100 concurrent users
• 3-day free trial — test with your real site before paying

Cloudways Limitations

• Unmanaged at the server level — they won't SSH in and debug custom configs
• No email hosting included (need a separate email provider)
• Can get expensive fast if you over-provision server size
• Not as fast as ScalaHosting VPS on heavy WooCommerce workloads

Performance Benchmarks

• TTFB: 127ms avg
• Load Test (100 Users): 168ms (+32%)
• Uptime: 99.981%
• PHP Workers: Server-configurable
• WooCommerce TTFB: 156ms @ 100 Users

Budget Step-Up: 127ms TTFB from $11/mo

Read Our Full Cloudways Review

$0/mo (with credit)

3-Day Free Trial — Test With Your Site

Start Cloudways Free Trial ➦

Frequently Asked Questions

Why is my WordPress site so slow?

The most common cause of a slow WordPress site is bad hosting hardware or oversold server nodes — not plugins or themes. A typical shared hosting server runs 200+ websites on the same CPU and RAM. When your neighbors spike, your TTFB balloons from 100ms to 600ms+. The second most common cause is no caching layer — WordPress runs PHP and hits the database on every single page request by default. The fix is: (1) check your TTFB first. If it's above 200ms, the problem is the server — no plugin will fix it. If it's below 200ms, install a caching plugin and enable Redis.

What is TTFB and why does it matter?

TTFB stands for Time To First Byte — the time between a browser sending a request to your server and receiving the first byte of the response. It measures pure server speed before any content downloads. A TTFB under 200ms is the industry standard for a well-configured server. Above 300ms means your server is too slow regardless of what else you do. Google uses TTFB as a signal in Core Web Vitals. You can measure it free with WebPageTest or GTmetrix.

Will installing a caching plugin fix my slow WordPress site?

Only if your TTFB is already under 200ms. A caching plugin eliminates repeated PHP execution and database queries by serving pre-built HTML files — but it cannot change the underlying server hardware. If your server takes 450ms just to start a response (TTFB), a caching plugin might cut that to 200ms on cached pages. But a good server + caching gets to 15ms on cached pages. The ceiling is always the hardware. Fix the server first, then layer the caching on top.

What is the fastest WordPress hosting in 2026?

In our benchmark testing on an identical WordPress install with 10 plugins, ScalaHosting Managed VPS achieved 38ms TTFB — the fastest result across 12 providers. This is due to AMD EPYC 9474F processors (top 3% globally on PassMark), NVMe PCIe 5.0 storage at 2,457 MB/s, and low-density nodes that guarantee your allocated CPU and RAM perform as advertised. For a budget option, Cloudways on a DigitalOcean droplet achieved 127ms TTFB at $11–14/mo — about 3.5× faster than typical shared hosting.

Is Cloudways good for WordPress speed?

Yes. Cloudways sits in the sweet spot between shared hosting and dedicated VPS. You get cloud NVMe infrastructure, one-click Redis, and per-hour billing starting at $11/mo on a DigitalOcean droplet. In our tests, Cloudways achieved 127ms TTFB and 156ms WooCommerce checkout TTFB at 100 concurrent users — roughly 3.5× faster than typical shared hosting at 3× the price. For content sites and blogs under 30,000 monthly visitors, it's the right upgrade. For WooCommerce stores or high-traffic sites above that threshold, ScalaHosting's low-density VPS nodes provide meaningfully better performance consistency.

What does Redis object cache do for WordPress?

Redis stores the results of database queries in server RAM so they don't need to be re-executed on every page load. A standard WooCommerce page triggers 200+ database queries per request. With Redis enabled, most of those queries are served from RAM in microseconds instead of hitting MySQL. The result: our WooCommerce checkout TTFB dropped from 890ms to 156ms at 100 concurrent users — a 82% improvement with a single configuration change. Redis is included and one-click enabled on both ScalaHosting SPanel and Cloudways.

Should I use WP Rocket or LiteSpeed Cache?

Use WP Rocket if you want the fastest setup, are on any hosting provider, and are willing to pay $59/year. It works out of the box — no technical knowledge required. Use LiteSpeed Cache (free) if you're on LiteSpeed-powered hosting (ChemiCloud, Hostinger, A2 Turbo) and are comfortable with a 20-minute configuration. LiteSpeed Cache can match WP Rocket's performance on LiteSpeed servers and is free. On non-LiteSpeed servers (Nginx, Apache), LiteSpeed Cache loses its server-level advantages and WP Rocket wins.

How much does PHP version affect WordPress speed?

Significantly. Our benchmarks show PHP 8.3 handles 419 requests per second on WordPress — versus 285 on PHP 7.4, a 47% improvement on the same hardware. Page generation time dropped from 142ms to 97ms. Upgrading PHP is free and takes 30 seconds in any modern hosting panel (SPanel, cPanel, Cloudways). The risk: a small number of older plugins aren't compatible with PHP 8.x. Check compatibility first using the Health Check & Troubleshooting plugin, then upgrade.

Does Cloudflare actually speed up WordPress?

Yes, but it speeds up the perceived load time for repeat visitors more than the raw TTFB. Cloudflare's CDN caches your HTML, CSS, JavaScript, and images at edge nodes in 200+ locations worldwide. A visitor in Tokyo loading your US-hosted site gets assets from a Japanese edge node instead — cutting asset load time from 800ms to 80ms. The TTFB for the first uncached HTML request still hits your origin server, but Cloudflare's free tier also provides DDoS protection, SSL termination, and HTTP/3 support. Use it. It's free and has no meaningful downside for standard WordPress sites.

How do I know if my images are slowing down my site?

Run your site through GTmetrix or Google PageSpeed Insights. Look for these warnings: (1) 'Serve images in next-gen formats' — means you're using PNG/JPEG instead of WebP. (2) 'Properly size images' — means you're uploading 4000px images for 800px display slots. (3) 'Defer offscreen images' — means lazy loading is not enabled. Typical unoptimized WordPress sites have 6–8MB of images on a page that could be 400–600KB as WebP. The fastest fix: install Smush or ShortPixel, enable WebP conversion, and enable lazy loading in WP Rocket.