WordPress running slow? Here's how to make a WordPress site faster

A slow WordPress site almost always comes down to the same combination: too many plugins, unoptimised images, a heavy theme, and cheap shared hosting straining under everyone else's traffic too. Speed is measured with Core Web Vitals — LCP, INP and CLS — and improved by prioritising hosting, images, caching and cutting unnecessary plugins. Below you'll find what each factor does, what actually moves the needle, and when a speed problem is really a sign that WordPress isn't the right platform.

What "fast" actually means: Core Web Vitals explained

Google uses three measurable signals to judge whether a page feels good to visitors. These are the Core Web Vitals:

Metric	What it measures	Target
LCP (Largest Contentful Paint)	How quickly the largest visible element (often a hero image or heading) loads	Under 2.5 seconds
INP (Interaction to Next Paint)	How quickly the page responds to a click or tap, measured across the whole session	Under 200 milliseconds
CLS (Cumulative Layout Shift)	How much the page "jumps" while elements load (think of an ad suddenly taking up space)	Under 0.1

INP replaced the older First Input Delay metric as an official Core Web Vital in March 2024 (source: web.dev/inp). Together, these three values partly determine how Google scores your page — and they're also a genuinely useful proxy for how a visitor experiences your site: does it load fast, does it respond instantly, does everything stay stable.

Why WordPress sites end up slow

WordPress itself isn't slow — the way most sites get built often is. The most common causes:

• Page builders with heavy overhead. Drag-and-drop builders tend to generate stacks of nested divs and their own CSS/JS per section, making pages needlessly heavy.
• Plugin sprawl. Every plugin loads its own scripts and styles, often on every page — even where it does nothing. Ten to twenty active plugins is common, and it adds up fast.
• Unoptimised images. Photos uploaded straight from a camera or phone are often five to ten times larger than the web actually needs.
• Cheap shared hosting. On budget hosting you share server resources with hundreds of other sites. When one of them gets busy, you feel the slowdown too.
• Render-blocking assets. CSS and JavaScript the browser must load before anything appears on screen directly delays the first paint.
• Heavy, generic themes. Multipurpose themes with dozens of built-in features often load code for functionality you never use.

If you want to know what structural upkeep can do here, take a look at WordPress maintenance — speed and maintenance largely go hand in hand.

What actually works: a prioritised list

Not everything pays off equally. Based on real-world impact, this is the order we work through:

1. Hosting. A specialised WordPress host with enough resources and server-side caching often solves half your speed problems before you touch anything else.
2. Images. Compress and resize images to their actual display size, and use modern formats like WebP or AVIF instead of JPEG or PNG. This is usually the biggest win per hour of work.
3. Caching and a CDN. Page caching stops WordPress from rebuilding the whole page on every visit. A CDN (content delivery network) serves static files from a server close to the visitor.
4. Fewer plugins. Every plugin you remove is less code to load and maintain. For each one, ask: can this work without it, or with a lighter alternative?
5. A lean theme. A theme built specifically for your purpose — or custom-built — loads only what you actually use, instead of a generic library of options.
6. Database hygiene. Revisions, spam comments and expired transients pile up in the database and slow down queries. Cleaning up periodically keeps the site responsive.

Symptom → likely cause → fix

Symptom	Likely cause	Fix
Page loads slowly on first visit	No caching active, slow hosting	Set up page caching, move to faster hosting
Hero image appears late (high LCP)	Oversized image files, lazy loading applied in the wrong place	Compress images, pick the right size, preload the hero image
Clicking menus or buttons feels sluggish (high INP)	Too much JavaScript from plugins, page builder scripts	Remove unnecessary plugins, defer scripts
Page "jumps" while loading (high CLS)	Images or ads without fixed dimensions	Set explicit width and height on images and embeds
Site is slower in the evening than during the day	Shared hosting getting busy from other sites on the same server	Move to hosting with guaranteed resources
Admin panel (wp-admin) feels slow	Bloated database, too many active plugins	Clean up the database, audit plugins

How to actually measure speed

Use at least two types of data:

• Lab data, from tools like PageSpeed Insights or Lighthouse, simulates a single visit under controlled conditions. Useful for quick checks after a change.
• Field data, from the Chrome UX Report, shows how real visitors experience your site over time — across different devices, networks and locations.

Lab and field data can diverge. A page that loads fast in a test can still feel slow in practice for visitors on a poor mobile connection. Look at both, not just a single score in one tool.

Want to know where your site actually stands? The free website scan gives you a concrete picture without a sales pitch.

When speed is a platform problem, not a settings problem

Sometimes the issue can't be solved with hosting, caching and cleanup — for example, heavy WooCommerce catalogues with thousands of products, sites with extensive custom functionality that keeps hitting plugin limits, or teams that repeatedly run into what a page builder can't do. In those cases, it's more honest to look at WordPress alternatives: a headless setup, Shopify for e-commerce, or a custom-built application. At that point speed isn't a configuration issue — it's an architecture question.

Speed and search visibility are also connected: Google uses Core Web Vitals as one of many ranking signals, though content quality still matters most. Read more about that in WordPress SEO.

Frequently asked questions about WordPress speed

How fast should my WordPress site load?

Aim for an LCP under 2.5 seconds for most of your visitors — that's the threshold Google considers "good." Anything below that is a bonus, but above 4 seconds visitors clearly notice the delay.

Is a caching plugin enough to make my site fast?

Caching helps, but it doesn't fix underlying issues like oversized images, slow hosting or too many plugins. Treat it as one part of a broader approach, not a quick fix that solves everything.

Does the theme really make that much difference to speed?

Yes. A generic multipurpose theme often loads code for features you never use. A lean or custom-built theme can be significantly lighter, which directly affects load time and INP.

How many plugins are too many for WordPress?

There's no fixed number, but every plugin has a cost in load time and maintenance. Quality matters more than quantity: a few well-built, lightweight plugins weigh less than a handful of heavy, poorly maintained ones.

Can cheap hosting be the reason my site is slow?

Yes, and it's one of the most underrated causes. On shared hosting you share server resources with other customers, so someone else's traffic spike affects your load time. Moving to hosting with guaranteed resources often delivers an immediate, noticeable improvement.

What's next?

Not sure whether your site is slow because of settings, plugins or the platform itself? Book a free call and we'll figure out together where the real gains are — whether that's a quick technical fix or a more fundamental choice.