Speed Why your WordPress site is slow, and what to check first

How to measure your site’s speed with real data, and the most common causes of a slow WordPress site, in order of priority.

Updated October 16, 20263 min readLume Digital

In short

A slow WordPress site almost never has a single cause. The most common are heavy images, plugins and scripts that load on every page, an overweight theme or page builder, missing caching and a slow-responding host. Measure first and fix in that order, so your effort goes where it shows most.

Before you install another plugin or switch hosts, measure and review the causes in order. This guide tells you what to look at and where to start.

Measure first

Run your home page and one service page through PageSpeed Insights (pagespeed.web.dev). Look at two kinds of data: field data comes from real visits and only appears if your site gets enough traffic; lab data is a simulation that helps you find causes. If you have Search Console, its Core Web Vitals report shows which groups of pages have problems.

For reference, Google considers a page good when its main content appears within 2.5 seconds (LCP), it responds to interactions within 200 milliseconds (INP) and its elements barely shift while loading (CLS of 0.1 or less), measured at the 75th percentile of visits. Source: web.dev, Core Web Vitals.

Images that are too heavy

It’s the easiest cause to spot. A photo uploaded straight from the camera can weigh several megabytes and display in a small space. Check that images match the size they’re shown at, use modern formats like WebP or AVIF, and that those below the fold only load as the visitor gets close. The page’s main image, however, shouldn’t be lazy-loaded.

Plugins that load too much

The number of plugins matters less than what each one loads. A form plugin that adds its files to every page, even though the form is on just one, slows down the whole site. Review what each plugin does, deactivate the ones you no longer use and look for alternatives to those that load resources where they aren’t needed.

Third-party scripts

Chat widgets, ad pixels, maps, embedded videos and analytics tools all download code from other servers. Each one competes with your own content for the visitor’s connection. Ask whether each script is still needed, and load the ones that are after the main content, or only when the visitor uses them.

The theme and the page builder

Some themes and page builders load a lot of code to offer options your site doesn’t use. If everything else is optimized and the site is still slow, the foundation may be the limit. Then it’s worth weighing whether improving what you have costs more than rebuilding on a lighter base.

Hosting and caching

If the server takes a long time to respond before sending anything, no front-end optimization can make up for it. Well-configured caching cuts that time by serving pre-built pages instead of generating them on every visit. If the server is still slow with caching, your hosting may be the problem.

Where to start

Measure your home page and most important pages, and save the results as your baseline.
Optimize the main image and the heaviest images.
Remove plugins and scripts you don’t use.
Set up caching and check the server response time.
Measure again and compare with your baseline.

If you’d rather we handle it with you

Web performance

We measure where loading time is lost, fix it in order of impact and show you the difference with before-and-after measurements.

Frequently asked questions

Will switching hosts fix a slow site?

Only if the server is the main cause. Measure the server response time first: if it’s low and the site is still slow, the problem is in the site itself.

How many plugins is too many?

There’s no magic number. What matters is what each plugin loads and on which pages. One badly configured plugin can weigh more than ten lightweight ones.