Free SEO audit for new clients — claim yours
Home/Blog/Technical SEO/WordPress Speed Optimisation: Hosting, Plugins a…
Technical SEO

WordPress Speed Optimisation: Hosting, Plugins and Caching

WordPress Speed Optimisation: Hosting, Plugins and Caching
Table of contents
  1. Diagnosing where a WordPress page spends its time
  2. Hosting and PHP version decisions that set the ceiling
    1. Run a supported PHP version
  3. Caching layers and which one fixes which problem
  4. Cutting plugin and page builder bloat
    1. Page builders and heavy themes
  5. Images, fonts and scripts on the front end
    1. Images
    2. Fonts
    3. CSS and JavaScript
  6. Database clean-up and ongoing maintenance
  7. A worked example: a 42-plugin service business site
  8. Questions WordPress owners ask about speed
    1. What is the single biggest WordPress speed improvement?
    2. Which PHP version should WordPress run?
    3. Do I need Redis object caching?
    4. Can a speed plugin fix a slow WordPress site on its own?
    5. How many plugins are too many?
  9. Making your WordPress site faster, in the right order
  10. Further reading on wordpress speed optimization
  11. Sources for this WordPress speed guide

WordPress itself is not slow. A clean install on decent hosting serves pages quickly. The slow WordPress sites we audit almost always share the same handful of causes: a cheap shared server running an old PHP version, no page caching, a heavyweight theme or page builder, and a plugin list that has grown to 40 or 50 entries over the years, several of which load scripts on every page whether they are needed or not.

The fix is rarely one magic plugin. Speed optimisation plugins can hide some problems, but they cannot make an overloaded server respond quickly or make a 2 MB page builder layout light. The order in which you tackle things matters: diagnose first, then fix the server, then caching, then the front end, then housekeeping.

This guide follows that order. It shows how to find out where the time goes, what to ask of your host and PHP version, how the layers of caching fit together, how to cut plugin and builder bloat, how to handle images, fonts and scripts, and how to keep the database and site fast once you have fixed them.

Diagnosing where a WordPress page spends its time

Every page load has two halves. The server half is the time WordPress and the database take to build the HTML; it shows up as Time to First Byte (TTFB). The browser half is the time spent downloading and running CSS, JavaScript, fonts and images; it shows up in LCP, INP and CLS. The fixes are completely different, so identify which half is the problem first.

  1. Check field data. Open Search Console's Core Web Vitals report (mobile) and note which metric fails. Thresholds at the 75th percentile are LCP 2.5 s, INP 200 ms and CLS 0.1 (Search Console Help).
  2. Measure TTFB uncached. In PageSpeed Insights or WebPageTest, test a page with a cache-busting query string (for example ?nocache=123). If uncached TTFB is above roughly 600–800 ms, the server half needs attention.
  3. Measure TTFB cached. Test the normal URL twice. A cached page should come back very quickly; if it does not, page caching is missing or misconfigured.
  4. Profile the server. Install the free Query Monitor plugin on staging. It shows database queries, slow queries, hooks and which plugin is responsible for each. Look for pages making hundreds of queries or single queries taking hundreds of milliseconds.
  5. Profile the front end. Run Lighthouse and the DevTools Network panel. Sort scripts and styles by size and note which plugin each comes from (the file path usually contains /wp-content/plugins/plugin-name/).
  6. Check Site Health (Tools, then Site Health). It flags outdated PHP, missing persistent object caching on larger sites, and other configuration issues.

Keep the lab and field distinction in mind: a single Lighthouse run on a fast connection can look very different from what mobile visitors experience (web.dev on lab versus field data). Our guide to field data versus lab data explains how to use each.

SymptomMost likely causeWhere to look first
Slow TTFB on every page, even cachedNo page cache, or cache bypassed by cookiesCaching plugin or host cache settings
Slow TTFB only uncached or logged inHeavy queries, slow PHP, weak serverQuery Monitor, PHP version, hosting plan
Slow LCP with fast TTFBLarge hero image, render-blocking CSS, web fontsTheme, page builder, image delivery
Poor INPToo much JavaScript: sliders, builders, chat, trackingPlugin scripts loaded site-wide
Poor CLSImages without dimensions, ads, late banners, font swapsTheme templates, ad and cookie plugins
Admin area slowAutoloaded options, heavy plugins, heartbeat, cronDatabase and Query Monitor in admin

Hosting and PHP version decisions that set the ceiling

Hosting decides the best TTFB you can achieve. On overcrowded shared hosting, CPU and database resources are contended, so uncached requests (logged-in users, WooCommerce carts, search results) stay slow however well the front end is optimised. Our guide to Time to First Byte goes deeper.

What to look for in a host:

  • Current PHP versions with OPcache enabled.
  • Server-level page caching (Nginx FastCGI cache, Varnish or LiteSpeed Cache) or clear support for a caching plugin.
  • A persistent object cache (Redis or Memcached) available on your plan.
  • Data centres close to your audience, or an integrated CDN.
  • Staging environments, so you can test changes safely.
  • Honest resource limits: dedicated CPU or "workers" for WooCommerce and membership sites with many uncached visits.

Run a supported PHP version

WordPress's official requirements page recommends:

“PHP version 8.3 or greater.”

— WordPress.org, Requirements

It also recommends MariaDB 10.11 or greater, or MySQL 8.0 or greater, plus HTTPS support. PHP's own support schedule (as published on php.net) explains why version matters for security as well as speed:

PHP branchActive support untilSecurity support untilStatus in October 2026
8.231 Dec 202431 Dec 2026Security fixes only, ending this year
8.331 Dec 202531 Dec 2027Security fixes only
8.431 Dec 202631 Dec 2028Actively supported
8.531 Dec 202731 Dec 2029Actively supported

Anything older than 8.2 is past end of life. Before upgrading, clone the site to staging, switch PHP there, and check every important template and form, because old plugins are the usual source of incompatibility.

Caching layers and which one fixes which problem

"Caching" in WordPress means several separate mechanisms. WordPress's developer documentation on caching describes browser caching, page caching via plugins or reverse proxies such as Varnish, object caching with engines such as Redis or Memcached, and opcode caching such as OPcache. On choosing between object cache engines it says:

“The caching engine used should be dictated by the needs of the application.”

— WordPress Developer Resources, Cache
LayerWhat it storesHelps withTypical setup
Page cacheFinished HTML for anonymous visitorsTTFB for most trafficHost-level cache, or plugins such as WP Super Cache, W3 Total Cache, LiteSpeed Cache
Object cache (persistent)Results of database queries and computed dataUncached, logged-in and WooCommerce requests; admin speedRedis or Memcached plus a drop-in plugin
Opcode cacheCompiled PHPEvery PHP requestOPcache, enabled by the host
Browser cacheStatic files on the visitor's deviceRepeat visitsCache-Control headers set by server or plugin
CDNStatic files, sometimes full pages, at edge locationsDistance to visitors, bandwidthCloudflare, host CDN, or other providers

Use one page caching solution, not two. Stacking a host cache with a plugin cache that also generates pages causes stale content and confusing bugs. Exclude cart, checkout, account and any personalised pages from the page cache. More on headers in our browser caching guide.

Cutting plugin and page builder bloat

Plugin count alone is not the problem. A plugin that only runs in the admin or only on one page costs little. The problem is plugins that load assets everywhere or run expensive queries on every request.

A plugin audit that works:

  1. Export the plugin list and mark each as essential, useful or unknown.
  2. On staging, use Query Monitor to see each plugin's queries and time, and the Network panel to see which plugins load CSS and JS on the home page, a post and a product.
  3. Remove plugins that duplicate features (two SEO plugins, two form plugins, a slider used on one old page).
  4. Replace single-feature plugins with a few lines of code where a developer is available, such as adding a tracking snippet.
  5. For plugins that must stay, stop them loading assets where they are not used. Many form, slider and gallery plugins have settings for this; otherwise an asset manager plugin or a small function using wp_dequeue_script can limit them to the pages that need them.
  6. Re-test after each removal so you know what changed.

Page builders and heavy themes

Page builders make design easy and pages heavy. They add their own CSS and JavaScript frameworks, deeply nested markup (which increases style calculation and presentation delay, one of the INP subparts web.dev describes), and often icon fonts and animation libraries. Options, from least to most effort:

  • Enable the builder's own performance settings (optimised asset loading, reduced DOM output, disabling unused widgets and icon libraries).
  • Use the builder only for landing pages and the block editor for posts.
  • Rebuild key templates with a lightweight block theme.

Images, fonts and scripts on the front end

Images

WordPress has generated responsive srcset and sizes markup for content images since version 4.4, with a default srcset cap of 1,600 pixels (Make WordPress Core). Make sure your theme's sizes matches its real content width and that hero images in templates or builders also output srcset. Our guide to responsive images with srcset and sizes covers the details. Then:

  • Serve WebP or AVIF through an image optimisation plugin or CDN.
  • Do not lazy-load the LCP image; web.dev says never to do so (Optimize LCP). Many themes and plugins lazy-load everything; exclude the first content image or hero.
  • Add fetchpriority="high" to the hero if the theme does not.

Fonts

Self-host fonts rather than loading from third-party domains, subset them, limit weights, and use font-display: swap or optional. See our web font optimisation guide.

CSS and JavaScript

Optimisation plugins can minify, combine, defer and delay scripts. Use them carefully: "delay JavaScript until interaction" can dramatically improve lab scores while breaking menus, forms or consent banners, and deferring the wrong script can create layout shift. Change one setting at a time and test key journeys. For the principles, see eliminating render-blocking resources and our notes on preload and preconnect resource hints.

Database clean-up and ongoing maintenance

A WordPress database that has run for years collects clutter that slows queries and admin screens:

  • Post revisions. Limit them with define('WP_POST_REVISIONS', 10); in wp-config.php and clean up old ones.
  • Expired transients left by plugins.
  • Autoloaded options. Rows in wp_options with autoload enabled are loaded on every request. Uninstalled plugins often leave large autoloaded rows behind. Query Monitor and database tools can show the total autoload size; investigate anything unusually large.
  • Orphaned tables from removed plugins.
  • Spam and trashed comments.
  • WooCommerce sessions and action scheduler logs, which can grow to millions of rows.

Two background processes also deserve attention. WP-Cron runs scheduled tasks on page loads; on busy sites, set define('DISABLE_WP_CRON', true); and trigger wp-cron.php from a real server cron every few minutes. The Heartbeat API sends regular admin-ajax requests from open admin screens; reducing its frequency helps on shared hosting.

Always take a full backup before any database clean-up, and run it on staging first.

A worked example: a 42-plugin service business site

Hypothetical example for illustration. A home services company runs WordPress on entry-level shared hosting with PHP 7.4, a page builder theme and 42 plugins. Mobile field data shows LCP 4.6 s and INP 340 ms; uncached TTFB is 1.8 s.

StepChangeUncached TTFBMobile LCP p75Mobile INP p75
0Baseline1.8 s4.6 s340 ms
1Move to managed host, PHP 8.4, OPcache, Redis0.6 s3.4 s330 ms
2Server page cache with cart and form pages excluded0.6 s (cached ~0.1 s)2.9 s330 ms
3Remove 15 plugins, limit form and slider assets to their pages0.5 s2.6 s240 ms
4Hero image eager with correct sizes, WebP, self-hosted fonts0.5 s2.2 s230 ms
5Delay chat widget until interaction, remove unused builder widgets0.5 s2.2 s170 ms

The numbers are illustrative; real results vary. The sequence is the lesson: server and caching fixes moved LCP most because the server half was the bottleneck, while plugin and script work moved INP. Doing it in the reverse order would have meant tuning the front end on a server that could not respond in time.

For ongoing checks, Semrush's roundup of website optimisation tools lists options such as PageSpeed Insights, WebPageTest and Search Console. Pick two, use them consistently, and annotate every plugin, theme or hosting change.

Questions WordPress owners ask about speed

What is the single biggest WordPress speed improvement?

On most slow sites it is page caching on decent hosting, because it cuts server response time for the majority of visitors. If TTFB is already fast, the next biggest gain usually comes from removing plugin and page builder bloat.

Which PHP version should WordPress run?

WordPress recommends PHP 8.3 or greater. As of October 2026, PHP 8.4 and 8.5 are in active support, while 8.2 receives security fixes only until the end of 2026. Test upgrades on staging first.

Do I need Redis object caching?

Small brochure sites with full-page caching rarely notice it. WooCommerce, membership and busy editorial sites, where many requests cannot be page cached, usually benefit from a persistent object cache such as Redis.

Can a speed plugin fix a slow WordPress site on its own?

It can help with caching, minification and image delivery, but it cannot make a weak server respond faster or make a heavy page builder layout light. Diagnose server and front-end problems separately.

How many plugins are too many?

There is no fixed number. What matters is what each plugin loads on the front end and how many queries it runs. Ten heavy plugins can be slower than forty lightweight ones.

Making your WordPress site faster, in the right order

Measure uncached and cached TTFB this week. If uncached TTFB is slow, start with hosting, PHP and object caching; if cached TTFB is slow, fix page caching; if TTFB is fine but LCP or INP fail, move on to the theme, plugins, images and scripts. Re-test after each change and let field data confirm the result over the next 28 days. For the SEO side of WordPress setup, see our WordPress SEO guide; if you are comparing platforms, our Shopify speed guide shows the levers on hosted ecommerce.

Want this done for you? Our page speed optimisation service covers hosting, caching and front-end work on WordPress and WooCommerce, and we can recommend SEO-friendly hosting. Request a custom quote or get in touch.

Further reading on wordpress speed optimization

Sources for this WordPress speed guide

  1. WordPress.org: Requirements
  2. PHP: Supported versions
  3. WordPress Developer Resources: Cache
  4. Make WordPress Core: Responsive images in WordPress 4.4 (November 2015)
  5. web.dev: Optimize Largest Contentful Paint
  6. web.dev: Optimize Interaction to Next Paint
  7. web.dev: Why lab and field data can be different
  8. Search Console Help: Core Web Vitals report
  9. Semrush Blog: Website optimization tools
Rohit Choudhary
Written byRohit ChoudharyCo-Founder, My SEO Experts

Rohit Choudhary is the co-founder of My SEO Experts and has more than 14 years of hands-on experience in SEO, paid advertising and digital marketing. Since starting out in 2011 he has helped hundreds of businesses grow through practical, data-driven search strategies, and he also serves as a consulting Digital Marketing Director for several US-based companies.

Keep reading

Related articles

Ready to grow your business online?

Get a free, no-obligation proposal tailored to your goals and budget.

CallFree Quote