Performance Playbook
15 Ways to Make a Slow WordPress Site Load Faster
The full playbook for speeding up WordPress — from the hosting stack underneath to the images, scripts, and plugins sitting on top.
NVMe
SSD storage underpinning every fast WordPress stack
15
Proven fixes covered in this playbook
24/7
Human support for diagnosing a stubborn slowdown
Free
CDN-ready SSL and managed migration to a faster host
In short
Speeding up WordPress comes down to fixing the same handful of bottlenecks: slow hosting infrastructure, no caching, oversized images, render-blocking scripts, and plugin bloat. The highest-impact fixes, in order, are moving to NVMe-based hosting with LiteSpeed, enabling page caching, compressing and lazy-loading images, minifying CSS/JS, and serving static assets through a CDN.
Most sites that feel permanently slow are missing three or more of these fixes at once, which is why isolated tweaks (installing just one plugin) rarely produce a dramatic change — the fixes compound.
Every WordPress speed guide eventually lists the same core techniques, but the ones that actually move the needle are usually buried under a dozen minor tips that barely register. This guide sorts fifteen fixes roughly by impact, starting with the foundation (hosting) and working up through caching, media, code, and cleanup.
Rather than trying to explain caching or image optimization in full depth here, each major topic links out to its own dedicated guide — this page is the map, showing how the pieces fit together and which order to tackle them in for the fastest visible improvement.
Fixes 1-4: The Hosting Foundation
No amount of plugin tuning fixes a server that's fundamentally slow, so this is where the list starts. Fix 1 is moving off spinning-disk or overcrowded shared hosting onto NVMe SSD storage, which cuts database query and file-read times dramatically compared to older storage. Fix 2 is a server stack built on LiteSpeed rather than a slower default web server, since LiteSpeed handles concurrent requests more efficiently under real traffic.
Fix 3 is enabling server-level caching (LiteSpeed Cache or similar) rather than relying purely on a plugin's PHP-based caching, since server-level caching skips PHP execution entirely for repeat visitors. Fix 4 is making sure PHP itself is running a current version, since each major PHP release has historically brought measurable performance gains for WordPress specifically.
Fixes 5-8: Caching and a Content Delivery Network
Fix 5 is page caching, which stores a fully rendered version of each page so WordPress doesn't rebuild it from the database on every visit — see the dedicated caching guide for full setup steps. Fix 6 is browser caching, telling a returning visitor's browser to reuse files like logos and stylesheets instead of re-downloading them. Fix 7 is object caching, which speeds up dynamic, logged-in, or WooCommerce pages that page caching alone can't fully cover.
Fix 8 is a CDN, which serves images, CSS, and JavaScript from servers geographically closer to each visitor rather than a single origin server. For a site with visitors spread across regions, a CDN often shaves more time off load speed than any single plugin setting.
Fixes 9-12: Images and Front-End Code
Fix 9 is resizing images to the actual dimensions they display at, since uploading a 4000px-wide photo for a 800px-wide blog column wastes bandwidth on every load. Fix 10 is compressing and converting images to WebP or AVIF, which shrink file size substantially compared to older JPEG and PNG formats at a similar visual quality — see the dedicated image optimization guide for the full process.
Fix 11 is lazy loading, deferring images below the visible fold until a visitor actually scrolls to them. Fix 12 is minifying and combining CSS and JavaScript files, reducing both file size and the number of separate requests a browser has to make before a page can finish rendering.
Fixes 13-15: Plugin Cleanup and Ongoing Maintenance
Fix 13 is auditing installed plugins and removing or deactivating anything not actively used — every active plugin adds at least some database queries or script loading, and a site with 40 plugins installed 'just in case' is rarely as fast as one running 15 that are all needed. Fix 14 is cleaning the database periodically, removing spam comments, expired transients, and old post revisions that accumulate and slow down queries over time.
Fix 15 is checking Core Web Vitals scores regularly (via Google Search Console or a free speed-testing tool) rather than optimizing once and assuming the site stays fast forever — a new plugin, theme update, or added page can quietly undo earlier gains, so periodic re-checking closes the loop on this whole list.
A Hosting Stack That Covers Fixes 1 Through 4 Automatically
Hosting Cheap's plans run on pure NVMe SSD storage with LiteSpeed as the web server, which means the foundational fixes at the top of this list are already handled the moment a site is migrated over — no separate purchase or configuration required.
Free managed migration moves an existing slow WordPress install onto this faster stack without downtime, and the cPanel-style panel makes it straightforward to layer caching plugins and a CDN on top once the foundation is already fast.
- Pure NVMe SSD storage on every hosting plan
- LiteSpeed web server for faster concurrent request handling
- Free managed migration onto the faster stack
- 24/7 human support for diagnosing what's actually slowing a site down
Why Hosting Cheap
What you get
NVMe SSD Foundation
Faster storage speeds up every database query and file read before any plugin is even installed.
LiteSpeed Web Server
Handles concurrent visitor requests more efficiently than older default server software.
Free Managed Migration
Move a slow existing WordPress site onto faster infrastructure without doing it manually.
1-Click Caching Plugins
Install LiteSpeed Cache or another caching plugin straight from the panel's installer.
24/7 Human Support
Get a second opinion when a site is still slow despite trying the obvious fixes.
Daily Backups
A safety net before making bigger changes like a plugin cleanup or database cleanup.
How It Works
Get set up in a few steps
Fix the hosting foundation first
Move to NVMe SSD hosting on LiteSpeed before spending time on smaller plugin-level tweaks.
Layer on caching and a CDN
Enable page, browser, and object caching, then add a CDN for visitors outside the origin server's region.
Clean up images, code, and plugins
Compress images, minify CSS/JS, and remove unused plugins, then re-check Core Web Vitals periodically.
Included
Everything you need, on every plan
- Hosting runs on NVMe SSD with a LiteSpeed web server
- Page, browser, and object caching all enabled
- CDN configured for visitors outside the origin region
- Images resized, compressed, and converted to WebP or AVIF
- Below-the-fold images set to lazy load
- CSS and JavaScript minified and combined where possible
- Unused plugins removed rather than just deactivated
- Core Web Vitals re-checked after each round of changes
FAQ
Frequently asked questions
What's the single biggest factor in WordPress speed?
Hosting infrastructure tends to matter most, since NVMe SSD storage and a fast web server like LiteSpeed set the ceiling every other optimization works within. Caching and image fixes matter enormously too, but they can't fully compensate for a slow underlying server.
How many plugins is too many for a fast WordPress site?
There's no fixed number — a well-coded plugin used actively has less impact than a poorly coded one sitting mostly idle. The better test is auditing what each plugin actually does and removing anything not delivering clear value.
Will switching hosts alone fix a slow WordPress site?
It fixes the foundation but usually isn't the whole answer — a site with unoptimized images and no caching will still load slowly even on faster hosting, just less slowly than before. Combining better hosting with caching and image fixes produces the biggest jump.
How often should I re-test my site's speed?
Checking after any major change (new plugin, new theme, redesign) is the minimum, with a periodic check every month or two as good practice, since plugin updates and added content can quietly reintroduce slowdowns.
Do Core Web Vitals actually affect search rankings?
Google has confirmed page experience signals, which include Core Web Vitals, are a ranking factor, though content relevance and quality still weigh more heavily overall. A fast site removes speed as a limiting factor rather than guaranteeing a top ranking on its own.
Should I optimize images or set up caching first?
Caching usually delivers a faster, more immediate improvement since it affects every page at once, while image optimization pays off most on media-heavy pages. Doing both together is ideal, but caching first is the better order if only tackling one at a time.
Related hosting
Give WordPress a Faster Foundation to Build On
Move to NVMe SSD hosting with LiteSpeed and free managed migration, then layer on the rest of this playbook.
Get Started