WordPress is not inherently slow, but it is easy to make it slow. A fresh WordPress installation with a lightweight theme loads in under a second. A WordPress site with 47 plugins, unoptimised images, no caching, shared hosting, and a database that has never been maintained can take eight seconds or more — and at that load time, over half of mobile users have already left. Learning to speed up WordPress is therefore not about finding exotic optimisation tricks. It is mostly about undoing the accumulated decisions that make WordPress slow in the first place: too many plugins, wrong hosting, no caching, and images that are the wrong format and size. I have worked through speed up WordPress optimisation processes on sites ranging from simple blogs to high-traffic WooCommerce stores, and the same interventions deliver the most impact every time. This guide covers them in the order that produces the largest speed gains for the smallest effort, because time spent on the big wins is always more valuable than chasing incremental improvements at the margins. This fits into the wider topic we cover in our Complete Guide to WordPress How.
Measure First — Know Your Speed Baseline Before You Optimise
Before you do anything to speed up WordPress, establish a baseline measurement. Optimisation without measurement is guesswork — you cannot know whether a change improved things, made them worse, or had no effect if you did not record the before state. Speed measurement also tells you which specific metrics are underperforming, which points directly to the right interventions rather than requiring you to try everything.
| Tool | What It Measures | Best Used For |
|---|---|---|
| Google PageSpeed Insights | Core Web Vitals (LCP, CLS, FID/INP), lab data, field data | SEO-relevant speed metrics; understanding real-user experience |
| GTmetrix | Full waterfall, load time, page size, request count | Identifying specific slow resources; before/after comparison |
| WebPageTest | Multi-location testing, video comparison, detailed resource timing | Advanced analysis; testing from different geographic locations |
| Chrome DevTools (Network) | Per-resource load times, render-blocking detection, cache status | Developer-level investigation of specific slow resources |
| Query Monitor plugin | Database query count and time, hook performance, HTTP API calls | WordPress-specific server-side performance issues |
Run a baseline test with Google PageSpeed Insights (pagespeed.web.dev) and GTmetrix before making any changes. Record the scores, the load time, the total page size, and the specific issues flagged by PageSpeed Insights. These numbers are your starting point for measuring how much each subsequent intervention does to speed up WordPress on your specific site. The issues flagged by PageSpeed Insights are also a direct guide to where the biggest gains are available — “Eliminate render-blocking resources” and “Properly size images” are consistently among the highest-impact items on most WordPress sites.
WordPress Hosting — The Foundation That Everything Else Depends On
The single most impactful decision for how to speed up WordPress is the hosting environment the site runs on. Optimisation applied to a site on poor shared hosting produces marginal improvements because the bottleneck is the server itself — its PHP performance, its response time to database queries, and the resources available to process each request. The same optimisation techniques applied to a site on quality managed WordPress hosting produce dramatically larger improvements because the underlying infrastructure is already optimised for WordPress workloads.
The hosting characteristics that most directly affect your ability to speed up WordPress effectively: PHP version (PHP 8.2 and 8.3 are significantly faster than PHP 7.x for WordPress workloads — check your current PHP version in Tools → Site Health and upgrade if below 8.0), server-level caching (NGINX FastCGI cache, LiteSpeed Cache, or Varnish at the server level provides faster caching than any WordPress plugin alone), proximity of the database server to the web server (same-datacenter databases add milliseconds of latency per query; on shared hosting with remote database servers, this adds up), and available RAM and CPU for PHP processes (shared hosting plans with very low memory limits cause WordPress to run slowly even with all other optimisations in place).
If your site is on very cheap shared hosting and you have done everything else in this guide without meaningful speed improvement, the hosting is likely the limiting factor. Upgrading to a managed WordPress host — Kinsta, WP Engine, SiteGround, Cloudways — or to a VPS where you control the server configuration will speed up WordPress more than any combination of plugin-level optimisations. This is the change I recommend first for sites where the GTmetrix Time to First Byte (TTFB) is above 600ms — a high TTFB indicates the server itself is slow before any WordPress processing even begins.
Implement Caching to Speed Up WordPress — The Biggest Single Win
Caching is the most impactful technique to speed up WordPress on any hosting environment. WordPress is a dynamic application — by default, every page request triggers PHP execution, database queries, and content assembly before the response is sent. Caching stores the assembled output of these operations and serves the stored result to subsequent visitors, bypassing the PHP and database work entirely. A cached WordPress page can load in under 100ms; an uncached WordPress page may take 800ms to 2000ms to generate even on decent hosting.
- Install a WordPress caching plugin. WP Super Cache (free), W3 Total Cache (free, more complex), WP Rocket (paid, easiest to configure correctly), or LiteSpeed Cache (free, most powerful if your host uses LiteSpeed/OpenLiteSpeed) are the leading options to speed up WordPress through page caching
- Enable full-page caching — the plugin stores a static HTML version of each page after the first request and serves it directly to subsequent visitors without executing PHP
- Enable browser caching — configure the plugin to set appropriate cache-control headers telling browsers to store CSS, JS, and images locally. Returning visitors load these resources from their own browser cache rather than re-downloading them
- Enable GZIP or Brotli compression — most caching plugins include compression options that reduce the transfer size of HTML, CSS, and JS files by 60-80%
- Enable object caching if your host provides Redis or Memcached — this caches WordPress’s database query results in memory, reducing database load for dynamic elements that are not served from the full-page cache
- Configure cache exclusions carefully — logged-in user pages, WooCommerce cart and checkout pages, and pages with personalised content should be excluded from the full-page cache
- After configuring caching, re-run GTmetrix and PageSpeed Insights and compare to your baseline to confirm the improvement
For sites on WP Engine, Kinsta, or other managed hosts that include server-level caching, the host’s caching system is typically more effective than a WordPress caching plugin — adding a plugin-level cache on top of a server-level cache can cause conflicts. On managed hosts with built-in caching, focus the plugin-level work on asset optimisation (minification, script deferral) rather than page caching, and let the host’s server cache handle the full-page caching to speed up WordPress most efficiently.
Image Optimisation to Speed Up WordPress
Images are typically the largest component of a WordPress page’s total payload, and unoptimised images are the single most common cause of WordPress sites being significantly larger and slower than they need to be. I regularly see WordPress sites with 4MB to 8MB of uncompressed JPEG images on their homepage — switching these to properly compressed WebP format with correct dimensions reduces the page weight by 70–80% and dramatically speeds up WordPress load times for every visitor.
The key image optimisation techniques to speed up WordPress effectively: always use the correct image format for each use case (WebP for photographs and complex images, SVG for logos and icons, PNG only when transparency is required and WebP is not available), resize images to the maximum display size before uploading rather than relying on WordPress to resize large originals, and compress images before upload using a tool like Squoosh (squoosh.app) or an optimisation plugin like Imagify, ShortPixel, or Smush. The Imagify and ShortPixel plugins can bulk-compress the existing media library in addition to automatically optimising new uploads — this is the fastest way to retrospectively speed up WordPress on a site with an existing library of unoptimised images.
Lazy loading — deferring the loading of off-screen images until the user scrolls toward them — is enabled by default in WordPress since version 5.5, which means images that are below the fold do not block the initial page render. Verify lazy loading is not disabled by any plugin or theme by checking that image elements in the page source show loading="lazy" on images other than the first visible image (the first visible image should not be lazy-loaded as it impacts the Largest Contentful Paint metric that directly affects PageSpeed Insights scores and SEO). Together, format optimisation, compression, and lazy loading are the three practices that most efficiently speed up WordPress performance on the image side.
Database Optimisation and Reducing Plugin Bloat
WordPress’s database grows over time with post revisions, transients, spam comments, and plugin data that is never cleaned up. A bloated database is slower to query than a clean one, and the cumulative effect on sites with years of accumulated data is a meaningful page load time contribution. Database optimisation to speed up WordPress on mature sites involves removing unnecessary data and improving query efficiency.
The WP-Optimize plugin (free) handles the most impactful database cleanup tasks: removing post revisions above a configured limit (keeping the last three revisions per post is sufficient for most sites), clearing expired transients (temporary data stored in the database by plugins that is never automatically cleaned), removing spam and trashed comments, and removing orphaned post metadata. Running this cleanup on a site that has never had database maintenance can reduce the database size by 30–50% and correspondingly improve query response times. Schedule WP-Optimize to run weekly for ongoing maintenance rather than waiting for the database to bloat again.
Plugin count is the other major controllable variable to speed up WordPress beyond caching and images. Every active plugin adds PHP code that executes on every page load — adding processing time, potentially making additional database queries, and loading additional JavaScript and CSS. Audit the active plugin list and deactivate any plugin whose function is not actively providing value. A plugin installed for a test three months ago and never deactivated, a slider plugin from a theme that is never used, a form plugin managing zero active forms — each of these adds page weight and processing time without contributing anything. The Query Monitor plugin shows exactly how many database queries and how much processing time each plugin adds per page load, making the cost of each plugin visible and the case for removal concrete.
Our guide on how to speed up WordPress website fast covers the quick-win techniques specifically for urgent speed improvements — the subset of the measures in this guide that deliver the largest gains in the shortest implementation time. Our guide on how to optimise WordPress performance covers more advanced performance techniques including CDN configuration, critical CSS, and server-level tuning that go beyond the plugin-level optimisations in this guide. The Google web.dev performance documentation covers Core Web Vitals in technical depth — the metrics that directly affect how Google evaluates page experience for SEO ranking and that the measures in this speed up WordPress guide are specifically designed to improve. You might also run into How to Restore WordPress Website From Backup Step by Step.
