How to Improve a Slow WordPress Website
By Guru Prasad Y · Published
Speed advice on the internet is mostly folklore: install this plugin, switch that setting, buy this hosting. Some of it helps. A lot of it does nothing, and a few things can break your site. The reliable approach is the boring one: measure, find the cause, fix that, measure again.
Step 1: Measure before you touch anything
You cannot tell whether a change helped without a baseline.
- Test your most important pages (homepage, a key service page, a product or contact page), not just the homepage.
- Test on mobile, because that is where most visitors are and where problems show first.
- Run each test a few times. Scores vary from run to run.
Google’s published targets for a good experience, from its Web Vitals programme, are:
| Metric | What it measures | Good target |
|---|---|---|
| Largest Contentful Paint (LCP) | How quickly the main content appears | 2.5 seconds or less |
| Interaction to Next Paint (INP) | How quickly the page responds to taps and clicks | 200 milliseconds or less |
| Cumulative Layout Shift (CLS) | How much the layout jumps while loading | 0.1 or less |
Treat these as targets to aim at, not guarantees. Results depend on your hosting, content and visitors.
If your site has enough traffic, Google Search Console reports real-world Core Web Vitals for your pages. See Google’s About Search Console.
Step 2: Find out what is making it slow
Slow WordPress sites usually suffer from a handful of causes. In rough order of how often they matter:
Oversized images
Photos uploaded straight from a phone or camera can be several times larger than the page needs. This is the most common cause of slow pages, and one of the easiest to fix.
Fix: resize images to the largest size they will actually appear, compress them and use modern formats where your setup supports it. Add loading="lazy" to images below the first screen. WordPress does this by default for most images.
Too many plugins, or heavy ones
Every plugin can add files and database queries. Some load their scripts on every page even where they do nothing.
Fix: list your plugins and ask what each is for. Remove anything unused. Replace heavy plugins that do a small job. Do not delete blindly: take a backup first and test afterwards.
Heavy page builders and unused features
Page builders are convenient, but a page assembled with deeply nested sections and many widgets loads more code than a simple one. See Elementor website development for how we keep builder sites lean.
Fix: simplify the layout, use fewer widgets, and turn off built-in features you do not use.
Fonts
Loading many font families and weights from external servers adds delay.
Fix: use fewer fonts and weights, and host them yourself if you can.
No caching, or weak hosting
If every visit makes the server rebuild the page from scratch, it will be slow under any load. A very cheap, overloaded server has the same effect.
Fix: use page caching, and check whether your hosting plan suits your site. We do not push a particular host. We test, then say whether hosting is the limit.
A bloated database
Years of old post revisions, expired temporary data and large “autoloaded” settings add weight to every request. Autoloaded options in particular are loaded on every page, so leftovers from removed plugins can quietly slow the whole site.
Fix: clean up revisions and expired transients, and review autoloaded options, always after taking a backup. Our own free plugin, Guru Site Health, checks for these quiet problems and explains them in plain language.
Third-party scripts
Chat widgets, social feeds, tracking tags and ad scripts each pull in code from other sites.
Fix: keep only the ones you actually use.
Step 3: Fix one thing at a time
Change one thing, retest, and note the result. If you change five things at once and the site breaks, you will not know why. Always take a backup before making changes to a live site.
Step 4: Retest and compare
Run the same tests as in step 1 on the same pages. Compare the numbers. If something did not help, undo it. If it helped, keep it.
What not to do
- Do not chase a perfect score. A score of 100 is not the goal. Real visitors on real phones are.
- Do not install five “speed” plugins. They often conflict, and the extra code can slow the site.
- Do not skip the backup. Optimisation changes are exactly the kind that can break a site.
- Do not trust one test. Run several.
When to get help
If your site is business-critical, built with a heavy page builder or an online shop, or you are not comfortable making changes to a live site, getting help is cheaper than a broken site. Our website performance optimization service follows exactly the steps above: measure, diagnose, back up, fix and re-test, with before-and-after numbers.
Sources
- web.dev, Web Vitals
- web.dev, Optimize Largest Contentful Paint
- Google Search Console Help, About Search Console
Guru Prasad YFounder, BuildWithGuru
I write these guides from what I see building and maintaining small-business websites. Ask me anything about them, with no obligation.