Why a slow site costs more than patience
A slow WordPress site doesn't just frustrate visitors — it quietly costs you conversions, search rankings, and repeat traffic. Google's Core Web Vitals factor load speed directly into how pages rank, and most visitors abandon a page that takes more than a few seconds to become usable. The good news is that a handful of well-understood fixes clear up the vast majority of WordPress performance problems.
Below are the five changes that consistently make the biggest difference, roughly in the order I'd tackle them on a sluggish site.
1. Get your caching strategy right
Page caching
Every uncached page load means WordPress rebuilds the page from scratch — running PHP, querying the database, and assembling the theme output all over again. A page caching plugin (or server-level caching if your host supports it) saves a ready-to-serve copy of each page so repeat visits load almost instantly, without touching PHP or MySQL at all.
This alone is usually the single biggest speed win available on a typical WordPress install, especially for content that doesn't change on every request.
Object and database caching
For sites with logged-in users, WooCommerce carts, or heavy custom queries, page caching alone isn't enough. Object caching (Redis or Memcached) keeps the results of expensive database queries in memory so WordPress doesn't have to repeat them on every request — this is what keeps dynamic, personalized pages fast as well.
Together, page and object caching handle the two main sources of WordPress slowness: repeated PHP execution and repeated database work.
2. Optimize every image before it ships
Compress and resize before upload
Uncompressed, full-resolution photos are one of the most common causes of a heavy homepage. Resize images to the dimensions they'll actually display at, and run them through a compression tool or plugin before or after upload — you can usually cut file size by 50–80% with no visible quality loss.
Switch to modern formats like WebP
WebP and AVIF produce noticeably smaller files than JPEG or PNG at the same visual quality. Most modern optimization plugins can convert and serve these formats automatically, falling back to older formats only for browsers that need it.
Lazy-load anything below the fold
Images and embeds further down the page don't need to load until a visitor scrolls near them. Lazy loading — built into modern WordPress core for images — keeps the initial page load light and pushes the rest of the work later, when it's actually needed.
3. Audit your plugins and render-blocking scripts
Every active plugin adds its own PHP, CSS, and JavaScript to the page — and a lot of that weight loads on every single page, whether it's needed there or not. Render-blocking scripts and stylesheets are especially costly, since the browser has to fetch and process them before it can paint anything on screen.
A periodic plugin audit, and a bit of care about how assets are loaded, usually recovers a meaningful chunk of load time without touching a single line of custom code.
- Deactivate and delete plugins you're not actively using — each one is extra weight and attack surface
- Combine or defer render-blocking CSS and JavaScript so the page can paint sooner
- Swap heavy, all-in-one plugins for lighter, single-purpose alternatives where possible
4. Choose hosting built for performance, and add a CDN
No amount of optimization fully compensates for cheap, oversold hosting. Server response time (often called Time to First Byte) sets the floor for how fast any page can possibly load, and it's determined almost entirely by your hosting stack, not your theme.
A content delivery network (CDN) complements good hosting by serving static assets — images, CSS, JavaScript, fonts — from a server physically close to each visitor, cutting the latency that would otherwise come from a single, distant origin server.
- Look for hosting with server-level caching, modern PHP versions, and adequate resources for your traffic
- Put a CDN in front of static assets so they load from a location near each visitor
- Keep PHP, MySQL, and the hosting environment updated to current, supported versions
5. Clean up your database and tighten your queries
Years of post revisions, spam comments, expired transients, and orphaned data quietly bloat the WordPress database, slowing down every query that touches those tables. A regular cleanup — plus limiting how many revisions WordPress keeps per post — keeps queries fast as the site grows.
If a specific page or plugin still feels slow after cleanup, it's usually worth checking for unindexed custom queries; a missing database index can turn a fast lookup into a slow one as content volume increases.
Putting it together
None of these fixes require a rebuild — caching, image optimization, a plugin audit, solid hosting with a CDN, and routine database cleanup can usually be rolled out incrementally without downtime. If you'd rather have someone run through this checklist on your site directly, feel free to get in touch or take a look at my WordPress services.