Slow WordPress site? Five fixes without a line of code

Speeding up a WordPress site usually works without any coding: a proper caching plugin, image compression and pruning unnecessary plugins solve the majority of slowness problems. The hard part is knowing which actions actually matter and which are a waste of time.

In this guide I go through speeding up in order of importance: measurement first, then the big wins, and fine-tuning last. The instructions work on an ordinary WordPress site without a developer.

Why speed shows up directly in euros

Slowness costs in three ways. Visitors leave: every extra second of load time drops conversions, and on mobile impatience is even less forgiving. Google takes speed and the Core Web Vitals metrics into account in rankings. And if you buy advertising, you pay for clicks that a slow landing page wastes before the visitor even sees your offer.

Measure first, fix second

Run your site through two tools before making changes:

• PageSpeed Insights gives you the Core Web Vitals values and lists the biggest problems. Look at the mobile result; that is the one that counts.
• GTmetrix shows a waterfall chart where you can see which individual files take the most time.

Write the starting numbers down. Without them you will not know whether anything helped.

The big wins: these five cover most of the benefit

1. Install a proper caching plugin

Caching serves pages pre-built instead of having WordPress assemble them again for every visitor. This is the single most effective action there is. Good options include LiteSpeed Cache (if the server runs LiteSpeed, as many hosts do), WP Rocket (paid, easiest) or W3 Total Cache. Use one, never two at the same time.

2. Compress and size your images

Oversized images are the most common single cause of slowness. Three rules:

• Upload images at the right size: a 4000-pixel camera photo is pointless on a blog, 1600 pixels is almost always enough.
• Use a modern format: WebP is typically clearly lighter than JPEG. Conversion works via a plugin (Imagify, ShortPixel or LiteSpeed Cache’s own optimisation, for instance).
• Make sure lazy loading is on: images load only once the visitor scrolls to them. In recent WordPress versions this is on by default.

3. Prune the plugins

Every active plugin can add load time, and some add a lot. Go through the list honestly: remove everything you do not actually use, and find a lighter alternative for the heaviest ones. Typical culprits are page-builder add-on packs, do-everything plugins where you use one feature, and old stats plugins. Deactivated is not enough; delete them.

4. Check your hosting tier

The cheapest shared servers are slow regardless of what you do on the site. If server response time (TTFB in the PageSpeed report) is consistently high, the problem is the hosting. For a local audience, the server should sit in or near your own country. Saving a few euros a month on hosting can cost many times that in lost customers.

5. Take the measure of your theme

A heavy do-everything theme loads hundreds of kilobytes of code of which you use a fraction. If you are rebuilding the site, choose a light theme (GeneratePress, Astra or a custom one) rather than an everything-for-everyone behemoth. On an existing site a theme change is a bigger project, so do points 1–4 first.

Fine-tuning: once the basics are done

Minifying and deferring CSS and JavaScript. Caching plugins do this with a setting. Test the changes one at a time, because aggressive combining can break the layout or the forms.

Lightening the fonts. Two font families and a few weights is enough. Every extra font file is added weight on every page load.

An inventory of external scripts. Chat widgets, tracking pixels, embedded videos and maps are often the heaviest part of the page. Ask of each one: does this produce more than it slows down? Load videos on click rather than automatically.

Database cleanup. Old revision histories, trash and transient data bloat the database over the years. Cleaning works via the caching plugin’s tools in a couple of minutes.

Realistic targets

Metric	Good level
LCP (largest contentful paint)	under 2.5 s
INP (response to user actions)	under 200 ms
CLS (layout stability)	under 0.1
Page size	under 2 MB, preferably under 1 MB

Staring at PageSpeed scores in pursuit of 100 makes no sense: the difference between 100 and 90 shows neither to the visitor nor, in practice, in rankings. Green Core Web Vitals on mobile is the right target.

What the Core Web Vitals metrics actually measure

The three metrics sound technical, but they describe very everyday things.

LCP measures how quickly the page’s largest content element (usually the main image or heading) appears. In practice it answers the question: how quickly does the visitor see something meaningful? The most common cause of a poor LCP is a big uncompressed hero image.

INP measures how quickly the page responds to the user’s clicks. A poor value usually means too much JavaScript clogging the browser.

CLS measures layout stability: does content jump around while loading so that you accidentally click the wrong thing? The most common cause is an image or ad with no space reserved for it in advance.

The most common mistakes when speeding a site up

Two caching plugins at once. They interfere with each other and can break the site. One is always enough.

Aggressive optimisation without testing. Combining CSS and deferring JavaScript can break menus, forms or carousels. Turn on one setting at a time and check the site afterwards, on mobile too.

Optimising only the front page. Visitors arrive from search engines onto subpages. Test the service pages and articles too; they are often slower than the front page.

Forgetting the cache during testing. The first load after clearing the cache is always slow. Test three times and look at the settled result.

When to call in a professional

The basics are worth doing yourself: they are easy and bring the biggest benefit. Professional help pays off once the basic actions are done and the result is still not enough, when the site is business-critical or when the problem is at server level.

Always ask for before and after measurements. The result of speed work is exceptionally easy to verify, so it should not be left to faith.

Summary: a half-day speed project

On most WordPress sites the biggest benefit comes in a single afternoon. First measure the starting level with PageSpeed Insights on mobile and write the numbers down. Then install a caching plugin and turn on page caching and compression.

Next run image optimisation across the whole media library and convert the images to WebP. Go through the plugin list and remove everything you do not use. Finally measure again and compare against the starting level.

If the Core Web Vitals values are green on mobile after that, you are done. If not, the next step is usually the hosting tier or the weight of the theme, and those are bigger decisions.

Frequently asked questions

How do I speed up my WordPress site?

In order of importance: install a caching plugin, compress images to WebP and to the right size, remove unnecessary plugins, make sure the hosting is adequate, and only then fine-tune scripts and fonts. Measure results before and after with PageSpeed Insights.

Why is my WordPress site slow?

The most common causes are uncompressed images, too many or too heavy plugins, missing caching, a cheap shared server and a heavy theme. It is rarely WordPress itself.

What is a good load time for a web page?

The practical target is for the page’s main content to appear on mobile in under 2.5 seconds (LCP). That is also Google’s Core Web Vitals threshold for a good experience.

Does site speed affect search rankings?

It does, though content matters more. Speed is a ranking factor Google has confirmed, and the indirect effect is larger: a slow page loses visitors and conversions regardless of ranking.

Is it worth chasing a hundred in PageSpeed scores?

No. The difference between a hundred and ninety shows neither to the user nor, in practice, in rankings. Green Core Web Vitals on mobile is the right and sufficient target.