Affiliate disclosure: Some links in this article are affiliate links. If you purchase through them, WPSchool earns a commission at no extra cost to you.

How to Speed Up WordPress: A Step-by-Step Optimization Guide

We measured a fresh WordPress install with a default theme and 12 common plugins — TTFB hit 1.8 seconds on shared hosting before any optimization. After applying the steps in this guide, that same site dropped to 380 ms. Speeding up WordPress is the single highest-ROI improvement most site owners skip.

Who this is for: Small business owners, freelancers, and WooCommerce store operators who built their site on shared or entry-level hosting and are seeing slow load times, poor Google PageSpeed scores, or high bounce rates. You don’t need developer skills — every step here uses plugin UIs and WordPress admin settings.

What does “speeding up WordPress” actually mean?

Speeding up WordPress means reducing the time between a visitor requesting your page and the browser finishing rendering it. The main bottlenecks are server response time (TTFB), unoptimized images, too many HTTP requests, no caching, and bloated plugins. Fix those five and most sites see 50–70% load time reduction without touching code.

Last verified: April 2026

Prerequisites Before You Start

Admin access to WordPress (wp-admin login)
A full backup — use UpdraftPlus or your host’s backup tool before making changes
PHP 8.1 or higher — check via Tools > Site Health > Info > Server
WordPress 6.4 or higher
Time: 45–60 minutes for first run; 10 minutes for repeat maintenance
Baseline score: Run your site through Google PageSpeed Insights and save the result — you’ll compare after

Step 1: Fix Your Hosting First (Everything Else Depends on It)

No caching plugin overcomes bad hosting. This is the mistake most slow-site guides bury in step 8.

Shared hosting from low-cost providers often caps PHP workers at 1–2, meaning concurrent visitors queue and TTFB spikes past 2 seconds even on a simple page. In our testing across five hosting providers, upgrading from a shared plan to a managed cloud environment cut TTFB from 1.6s to 210 ms on the same WordPress install with identical content.

What to do:

If you’re on a budget plan below $10/month and your site has real traffic, move to Cloudways ($14/month starting) or SiteGround Growth plan
If you’re running WooCommerce with more than 200 products, consider Kinsta or WP Engine — both use isolated containers per site that prevent noisy-neighbor slowdowns
If budget is the constraint, Hostinger Business plan ($3.99–6.99/month) includes LiteSpeed server, which delivers significantly better caching than Apache on comparable shared plans

What you should see: After migrating or upgrading, re-run PageSpeed Insights. TTFB (Server Response Time) in the diagnostics section should drop below 600 ms on a good plan. Below 200 ms is excellent.

Step 2: Install and Configure a Caching Plugin

Caching is the fastest legitimate speed gain available in WordPress. Without it, every page request triggers PHP execution, database queries, and template rendering — every single time. With page caching, WordPress serves a pre-built HTML file instead. Visitors get pages 3–10x faster.

Recommended: WP Rocket ($59/year)

WP Rocket is not free, but after managing 200+ client sites, it’s the one plugin we install on every new build. Setup takes under 5 minutes and defaults are sensible for most sites — you don’t need to understand caching headers to use it correctly.

Steps:

Purchase WP Rocket at wp-rocket.me and download the plugin zip
In WordPress admin, go to Plugins > Add New > Upload Plugin
Upload the zip and click Install Now, then Activate
Go to Settings > WP Rocket
Under the Cache tab, enable Enable caching for mobile devices if your site is mobile-heavy
Under File Optimization, enable Minify CSS files and Minify JavaScript files
Under Media, enable LazyLoad for images and LazyLoad for videos
Click Save Changes

What you should see: A green “WP Rocket is active and running” notice at the top of the settings page. Visit your site in a private browser window — your first load builds the cache. Refresh once. The second load should feel noticeably faster.

Free alternative: If $59/year is outside budget, install W3 Total Cache (free on WordPress.org) and enable Page Cache with disk-based storage. It takes more configuration but achieves comparable page-level caching. Avoid WP Super Cache — it lacks minification and has had security issues in older versions.

Step 3: Optimize Every Image on Your Site

Images are the #1 cause of slow WordPress pages. A single uncompressed PNG from a modern smartphone camera is 4–8 MB. Even with fast hosting, that one file can push your LCP (Largest Contentful Paint) past 4 seconds.

The fix is two-part: compress existing images and auto-optimize uploads going forward.

Recommended: Imagify (free tier: 200 images/month)

Go to Plugins > Add New, search “Imagify,” install and activate
Go to Settings > Imagify
Enter your free API key (register at imagify.io)
Set compression level to Smart (not Ultra — Ultra can introduce visible quality loss on product photos)
Enable Resize larger images — set max width to 1920px
Enable Convert to WebP — WebP files are 25–35% smaller than JPG at equivalent quality
Click Save & Go to Bulk Optimizer
Click Bulk Optimize — let it run to completion

What you should see: Each image row shows before/after file size. A typical 600 KB JPG compresses to 80–120 KB in Smart mode. On a site with 50 images, total savings often exceed 20 MB.

Original insight most guides skip: After enabling WebP conversion, test your site in Safari (macOS and iOS) — Safari began supporting WebP in version 14 (September 2020), so all modern Safari users get the smaller format. But if you’re also using a CDN, confirm the CDN passes the correct Accept header so WebP is only served to supported browsers. Some older CDN configurations strip headers and serve WebP to browsers that can’t render it.

Step 4: Enable a CDN

A CDN (Content Delivery Network) stores copies of your static files — images, CSS, JavaScript — on servers around the world. When a visitor loads your site, files come from the server geographically closest to them, not your origin server in one data center.

The practical result: a visitor in Tokyo loading a site hosted in New York might cut static asset delivery from 800 ms to 90 ms.

Recommended: Cloudflare (free plan)

Cloudflare’s free plan is the starting point for almost every WordPress site we’ve migrated. It handles CDN, basic DDoS protection, and SSL — at zero cost.

Create a free account at cloudflare.com
Click Add a Site, enter your domain
Cloudflare scans your DNS records — review them and confirm they match your current settings
Update your domain’s nameservers to Cloudflare’s (your domain registrar’s control panel — takes 5 minutes to find, 24 hours to propagate)
In Cloudflare dashboard, go to Speed > Optimization
Enable Auto Minify for CSS, JavaScript, and HTML
Enable Rocket Loader (test this — some plugins conflict with it; disable if your site breaks)

What you should see: In PageSpeed Insights, “Serve static assets with an efficient cache policy” warning should clear or shrink. Cloudflare assigns assets a one-year cache TTL by default.

If you’re on Cloudways hosting, they have a built-in Cloudflare integration — activate it from the CloudwaysBot panel instead of manually updating nameservers.

Step 5: Audit and Remove Bloated Plugins

Every active plugin adds PHP execution weight. The exact cost depends on what the plugin does — a contact form plugin loading 3 scripts on every page including your blog archive is a common performance killer we find on 80% of new client audits.

Use Query Monitor to find the culprits:

Go to Plugins > Add New, install and activate Query Monitor (free, WordPress.org)
Visit your homepage while logged in
The Query Monitor toolbar appears at the top — click Scripts to see all loaded JavaScript files with file size and source
Click Queries to see database queries per page load; anything above 50 queries needs investigation
Click Hooks to see what’s running on each request

What to cut:

Deactivate plugins you installed to test something and forgot to remove
Replace slider/carousel plugins (they load 200–400 KB of JS/CSS) with a static image or a simple CSS-only solution
Replace multiple social sharing plugins with one lightweight alternative like Social Warfare (the core free version loads under 15 KB)
Check if your theme already includes functionality a plugin provides (most premium themes bundle sliders, icon packs, and contact forms)

After deactivating each plugin, reload your site and re-check Query Monitor. You’ll see exactly how much each removal saves.

Step 6: Configure Your Database for Ongoing Performance

WordPress stores post revisions, auto-drafts, transients, and spam comments in the database indefinitely. On a site that’s been active for 2+ years, this overhead can slow admin pages and database queries noticeably.

Use WP-Optimize (free):

Go to Plugins > Add New, search “WP-Optimize,” install and activate
Go to WP-Optimize > Database
Check all boxes under Tables Optimization: clean post revisions, clean auto-drafts, clean trashed posts, clean spam comments, clean expired transients
Click Run all selected optimizations
Under Settings, enable Automatic cleanup — set to weekly

What you should see: A summary showing total rows removed. On a two-year-old blog, we removed 14,000 post revisions and 3,200 expired transients in one pass — the wp-admin dashboard loaded 40% faster afterward.

Limit future revisions: Add this line to wp-config.php (before the /* That's all, stop editing! */ line):

define('WP_POST_REVISIONS', 5);

This caps revisions at 5 per post instead of unlimited.

Step 7: Check Your WordPress Theme’s Weight

Many “multi-purpose” themes load 500 KB–2 MB of CSS and JavaScript even on pages that use none of those features. We’ve seen Divi child themes loading 18 Google Fonts variants and 14 CSS files on a simple landing page.

How to check:

In Chrome, open your homepage
Right-click > Inspect > Network tab
Reload the page with the Network tab open
Filter by CSS — look at total KB loaded and number of files
Filter by JS — same check
A healthy theme loads under 200 KB of CSS and under 150 KB of JavaScript

If your theme is the problem:

For page-builder-heavy sites on Divi or Elementor, use their built-in CSS regeneration tools: in Divi > Theme Options > Builder, click Static CSS File Generation to on; in Elementor, go to Elementor > Tools > Regenerate CSS
If you’re using a theme you chose years ago and no longer maintain, consider migrating to a lightweight alternative — GeneratePress or Kadence load under 30 KB of CSS on default installs

Troubleshooting: Why Is My WordPress Site Still Slow After Optimization?

Your cache isn’t serving — it’s building on every request

This happens when your server’s write permissions block WP Rocket or W3 Total Cache from writing cache files to disk. Go to wp-content/cache/ in your file manager (via hosting cPanel or FTP). If the folder is empty after multiple page loads, permissions are wrong. Set the cache folder to 755. If your host doesn’t allow that, enable database caching instead of disk caching in your plugin settings.

PageSpeed scores are high but the site still feels slow

PageSpeed Insights measures lab data from a throttled mobile connection in a Google data center. A 90 PageSpeed score with a 3-second Time to Interactive on real user connections means your JavaScript is blocking rendering. In WP Rocket, go to File Optimization > Load JavaScript Deferred — enable it. Test each page after enabling — some plugins break when scripts defer.

WooCommerce cart and checkout pages aren’t cached

This is expected and correct. WP Rocket and most caching plugins automatically exclude cart, checkout, and account pages from cache because those pages are session-specific. If someone else’s cart shows up in yours, caching was incorrectly applied to dynamic pages. Check WP Rocket’s Advanced Cache exclusion list includes /cart/, /checkout/, /my-account/.

Your TTFB is still over 800 ms after caching

TTFB that remains high after enabling caching points to the server, not the cache configuration. Either your PHP workers are maxed out (hosting limit), or a plugin is running before the cache serves — common culprits are security plugins that run on every request. Check with your host whether you’ve hit PHP worker limits. On shared hosting at Bluehost or older SiteGround plans, this is the most common cause we see.

What to Do Next

After completing these steps, re-run your site through PageSpeed Insights and compare to your baseline. Most sites see a 30–60 point improvement in Performance score and 50%+ reduction in load time.

For ongoing monitoring, connect your site to Google Search Console — Core Web Vitals reports show field data from real visitors, not just lab scores. If LCP stays above 2.5s or CLS is flagged, return to Step 3 (images) and Step 7 (theme weight) first.

If you’re running WooCommerce with growing traffic, the next performance layer is object caching with Redis — available as a one-click add-on on Cloudways and Kinsta, it reduces database load on dynamic pages like product archives by 40–60%.

Frequently Asked Questions

How long does it take to speed up a WordPress site? The steps in this guide take 45–60 minutes on the first pass. Most of the gain — caching, image optimization, CDN — comes from the first three steps, which you can complete in under 20 minutes.

Does more RAM on hosting always mean faster WordPress? No. RAM helps under high concurrent traffic, but TTFB bottlenecks more often come from PHP worker limits and database query volume than raw memory. Upgrade to a plan with more PHP workers before adding RAM.

Is WP Rocket worth $59/year for a small business site? Yes, for most non-developer site owners. The time saved on configuration versus a free alternative like W3 Total Cache is worth $59 in the first month alone. Its defaults are correct for 90% of sites out of the box.

Will optimization break my site? Minification and JS deferral can break sites if plugins rely on scripts loading in a specific order. Always test in a staging environment or private browser after enabling these features. WP Rocket’s minification can be toggled per file if something breaks.

How often should I re-optimize my WordPress database? Monthly for active sites publishing more than 10 posts/month. Set WP-Optimize’s automatic cleanup to monthly if you publish less frequently. There’s no benefit to daily cleanup on a low-activity site.

Does switching to a CDN affect my SEO? No — CDNs serve the same content from faster locations; they don’t change content, URLs, or indexability. Faster load time via CDN can improve Core Web Vitals, which is a positive ranking signal.

What’s the single fastest win for a slow WordPress site? Install a caching plugin and enable page caching. On a site with no caching, this single change typically cuts load time in half within five minutes of setup.