WordPress Website Speed Optimisation

Why WordPress is slow by default

WordPress powers 43% of the web. That popularity comes with a cost: the platform is built to be flexible for everyone, not fast for your specific site. Out of the box, WordPress generates pages dynamically on every request — meaning PHP, MySQL queries, plugin hooks, and theme templates all fire before a single byte reaches the visitor's browser.

Layer on a visual page builder (Elementor, Divi, WPBakery), a contact form plugin, a slider, a social sharing widget, a cookie consent banner, and a few SEO tools, and you've easily added 20–40 additional HTTP requests and 2–4 MB of JavaScript the browser must parse before anything appears on screen. This is why keeping plugins lean and regularly audited is part of ongoing site maintenance — not a one-off task.

The 6 root causes of a slow WordPress site

Core Web Vitals explained for WordPress owners

Google uses three metrics — collectively called Core Web Vitals — to measure real-world page experience. These are ranking signals. They are measured from real Chrome users visiting your site and reported in Google Search Console under "Core Web Vitals."

For most WordPress sites, images are the single largest contributor to page weight and slow LCP. The good news: image optimisation is the highest-impact fix you can make without a developer.

What to do

• Convert all images to WebP format. WebP is 25–35% smaller than JPEG at the same quality. Most modern image plugins (ShortPixel, Imagify, EWWW) do this automatically.

• Compress images before uploading. A hero image should be under 200KB. A blog thumbnail under 50KB. Use Squoosh.app to check sizes before any plugin touches them.

• Add width and height attributes to every <img> tag. This prevents layout shift (CLS). Page builders often strip these — check in DevTools.

• Enable lazy loading for below-the-fold images. WordPress adds loading="lazy" by default since version 5.5, but some themes override this.

• Never lazy-load the hero image. The LCP element must load immediately. Add fetchpriority="high" to the hero image tag (see Fix 8 for the full LCP fix).

• Use srcset for responsive images. WordPress generates srcsets automatically — confirm your theme is not overriding them.

Realistic impact: Image optimisation alone typically reduces page weight by 40–70% and improves Lighthouse Performance by 10–25 points on image-heavy pages. For sites built specifically around conversions — like landing pages — image speed is especially critical as every extra second directly reduces conversion rate.

Without caching, WordPress runs PHP and MySQL on every single page request — even when nothing on the page has changed. A caching plugin generates static HTML files and serves those instead, bypassing most of the stack entirely.

Which caching plugin to use

Realistic impact: Enabling page caching reduces Time to First Byte (TTFB) from 800ms+ to under 200ms on most WordPress installs. This alone can improve Lighthouse by 15–30 points.

A CDN stores copies of your site's static files (images, CSS, JS) on servers distributed globally. When a visitor loads your page, files are served from the nearest server — not from your hosting server in, say, Frankfurt — cutting latency significantly.

Cloudflare's free plan is the standard starting point for WordPress sites. It takes 15 minutes to set up (change your nameservers), adds basic DDoS protection, and its CDN covers 300+ cities worldwide. Most caching plugins (WP Rocket, LiteSpeed Cache) integrate directly with Cloudflare.

For sites with large image libraries or video content, Cloudflare's paid plans or a dedicated image CDN like BunnyCDN (from £8/month) offer better cache control and image transformation features.

Realistic impact: Adding a CDN typically reduces load time for non-UK visitors by 30–60% and improves Lighthouse (which simulates a US location) by 5–15 points.

Every active WordPress plugin adds PHP execution time, database queries, and potentially additional CSS and JavaScript files. Plugins are not inherently bad — but unused and poorly coded ones are a major drag.

How to audit your plugins

• Install the Query Monitor plugin temporarily. It shows you exactly which plugins are adding the most database queries and PHP execution time. Uninstall it after the audit.

• Deactivate every plugin you have not used in 30 days. Test your site after each deactivation. You will be surprised how many are safe to remove.

• Replace multiple single-purpose plugins with one comprehensive tool. Example: replace a separate slider plugin, a lightbox plugin, and an animation plugin with CSS-only equivalents.

• Check if your page builder offers everything. Elementor includes forms, popups, and sliders — you may not need Contact Form 7, Ninja Popups, and a separate slider plugin alongside it.

• Delete deactivated plugins. Deactivated plugins still load their files on the server — delete them completely if you are not going to use them.

Google Fonts loaded via a remote stylesheet are one of the most common causes of render-blocking requests on WordPress sites. Each font call requires a DNS lookup, a connection, and a file download — before the browser can render text.

The fix

• Self-host your Google Fonts. Download the font files (use google-webfonts-helper.herokuapp.com) and serve them directly from your server or CDN. This eliminates the external DNS lookup.

• Add font-display: swap to your @font-face declarations. This tells the browser to show fallback text immediately and swap in the web font when it loads — preventing invisible text during load (FOIT).

• Preload your primary font file. Add <link rel="preload" as="font"> for the woff2 file of your body font in your theme's <head>.

• Reduce font variants. Every font weight and style is a separate file. If your design uses Regular, Bold, and Italic — that is 3 files. If you have loaded 6 weights "just in case," remove the unused ones.

/* In your theme's functions.php — remove Google Fonts */
function remove_google_fonts() {
    wp_dequeue_style('wp-block-library-theme');
}
add_action('wp_enqueue_scripts', 'remove_google_fonts');

/* In your CSS — self-hosted font declaration */
@font-face {
    font-family: 'Inter';
    src: url('/fonts/inter-v13-regular.woff2') format('woff2');
    font-weight: 400;
    font-style: normal;
    font-display: swap;
}

Render-blocking JavaScript and CSS are a major cause of poor Lighthouse scores. If a script loads in the <head> without defer or async, the browser stops building the page until that script finishes loading and executing.

What to do

• Defer non-critical JavaScript. WP Rocket and LiteSpeed Cache both have a "Defer JS" option. Enable it — but test thoroughly, as some plugins break when deferred.

• Minify CSS and JS. Remove whitespace and comments from your stylesheets and scripts. Every caching plugin offers this. 5–15% file size reduction is typical.

• Remove unused CSS. Tools like PurgeCSS or the Critical CSS feature in WP Rocket generate a minimal stylesheet for each page, stripping out classes from your theme that are never used.

• Inline critical CSS. The CSS needed to render above-the-fold content can be inlined in the <head> so the browser does not need to wait for the external stylesheet. WP Rocket's "Load CSS Asynchronously" does this.

• Load third-party scripts (chat widgets, analytics, social embeds) with a delay. WP Rocket's "Delay JavaScript" can postpone scripts like Intercom or Hotjar until after the page is interactive.

A bloated WordPress database increases query times. Over years of use, WordPress accumulates thousands of post revisions, transients, spam comments, and orphaned metadata. Cleaning the database takes minutes and can reduce query overhead noticeably on large sites.

Database cleanup

• Install WP-Optimize or Advanced DB Cleaner. Run a cleanup to remove: post revisions (limit to 5 per post in wp-config.php), auto-draft posts, spam and trashed comments, expired transients, and orphaned meta.

• Schedule regular cleanups. Once a month is sufficient for most sites. WP-Optimize can run on a schedule automatically.

When to upgrade hosting

If your TTFB (Time to First Byte — measured in Chrome DevTools Network tab, or PageSpeed Insights) is consistently above 600ms even with caching enabled, your hosting is the bottleneck. No amount of plugin optimisation will fix a slow server.

LCP (Largest Contentful Paint) is the Core Web Vital that Google weights most heavily in ranking decisions. On most WordPress sites, the LCP element is the hero image or the H1 heading. Getting LCP under 2.5 seconds — especially on mobile — is where you will see the most measurable ranking impact.

How to identify your LCP element

Open Chrome DevTools (F12), go to Performance → record a page load. Click the LCP marker in the timeline. Chrome will highlight the element. Alternatively, run your URL through PageSpeed Insights — it flags the LCP element in the diagnostics.

The LCP fix checklist

• Serve the hero image in WebP format, sized correctly for the display dimensions (not the full camera resolution). For a full-width desktop hero, 1440px wide at 80% WebP quality is the ceiling.

• Add fetchpriority="high" to the hero <img> tag. This tells the browser to download this image before anything else. Most page builders do not do this by default — it requires manual template editing.

• Remove lazy loading from the hero image. Never add loading="lazy" to the LCP element. If your theme applies it globally, exclude the hero image specifically.

• Preload the hero image in the <head>: <link rel="preload" as="image" href="/hero.webp" fetchpriority="high">. This gives the browser a head start before it even parses the HTML body.

• Ensure the LCP image is in the HTML source, not injected by JavaScript. Images set as CSS backgrounds or rendered by JS frameworks are discovered late by the browser and almost always fail LCP.

<!-- In your theme's header.php, inside <head> -->
<link
  rel="preload"
  as="image"
  href="/wp-content/uploads/hero.webp"
  fetchpriority="high"
>

<!-- In your theme template — the hero img tag -->
<img
  src="/wp-content/uploads/hero.webp"
  width="1440"
  height="810"
  alt="[Descriptive alt text]"
  fetchpriority="high"
>

Realistic before/after expectations

Speed optimisation results vary significantly based on your starting point, hosting, and theme. Here are realistic ranges — not best-case marketing numbers.

Frequently asked questions

Sourced from what WordPress site owners actually search for.