Guide
How to speed up a WordPress site: 12 proven steps
The biggest WordPress speed gains come from page caching, smaller images, fewer plugins and a lighter theme, on hosting with a fast web server. Our plans use LiteSpeed, with the free LiteSpeed Cache plugin and Redis object caching, on UK servers. Measure before and after on a phone, change one thing at a time, and keep what helps.
Where the gains are
Typical impact of each step
A rough ranking, from our experience, of how much each step usually helps. Your site will differ.
These are our own estimates to show relative size. They are not measured results.
First
Measure before you change anything
You cannot tell whether a change helped unless you measured first. Use a speed testing tool on your key pages, and test on a mobile connection, because that is where most visitors are and where slow sites hurt most. Write down the results.
Look at three things in particular: how soon the main content appears, how long the page takes to become usable and whether things jump around as the page loads. Google reports these as Core Web Vitals, and they are a useful common language. Change one thing at a time, so you know what worked.
Caching
Steps 1 to 3: stop doing work twice
1. Turn on page caching
Install the free LiteSpeed Cache plugin and keep the default page cache on.
2. Add object caching
Connect Redis from the plugin settings to reduce database work.
3. Enable browser caching
Let returning visitors reuse files they already have.
Worked example
A photographer's portfolio goes from sluggish to quick
A photographer has a portfolio page with forty images, each uploaded straight from the camera at several megabytes. The page takes many seconds to appear on a phone. She follows a simple order of work, measuring before and after each step.
First she resizes and compresses the images to the size they are actually displayed, and converts them to a modern format, which removes most of the page weight. Second she turns on lazy loading so images below the screen load only when needed. Third she enables page caching, so the server stops rebuilding the page for every visitor. Fourth she deactivates two plugins she barely uses.
The page now appears in a fraction of the time, and the biggest single gain came from the images, not from any clever setting. The lesson is to find the heaviest item first and fix that before touching anything else.
Diagnosis
Match the symptom to the likely cause
| Symptom | Likely cause | First thing to try |
|---|---|---|
| Whole site slow, even simple pages | Slow hosting or no caching | Enable page caching and check your server response time |
| One page much slower than the rest | Huge images or heavy embeds | Compress images and lazy load embeds |
| Admin area very slow | Too many plugins or no object cache | Remove unused plugins and use an object cache |
| Fast at night, slow at midday | Busy server or traffic spikes | Check resource usage and caching |
| Layout jumps as the page loads | Images without set sizes | Add width and height to images |
| Slow only on mobile | Large scripts and unoptimised images | Reduce scripts and serve smaller images |
Measuring
Test properly or you are guessing
Speed work without measurement is guesswork. Pick two or three important pages, such as the home page and your main product or service page, and test them with a free tool such as PageSpeed Insights before you change anything. Write the results down.
Test more than once, because a single run can vary, and test mobile as well as desktop. Make one change at a time and test again. If a change gives no improvement, undo it, since every setting you add is something else to maintain. Pay attention to the visitor experience measures, such as how quickly the main content appears and whether the page jumps around, rather than chasing a perfect score.
Common mistakes
Things that waste time or make it worse
Installing three caching plugins at once is a classic. They fight each other, and the result is often slower and broken. Use one, and use the caching that your host provides where possible. Another mistake is adding a speed plugin while leaving enormous images untouched, which is like polishing a car with flat tyres.
Owners also pile on sliders, social feeds, chat widgets and tracking scripts, each of which loads extra code. Ask of every feature whether visitors would miss it. Finally, avoid a heavy page builder theme when a lighter one will do, since the theme sets the baseline for everything else.
- Run one caching plugin only
- Fix oversized images before anything else
- Remove features that nobody uses
- Pick a lightweight theme
- Test on a real phone, not just a fast desktop
- Re-test after every plugin update
Hosting side
What your host can do for you
Plugins can only do so much if the server underneath is slow. Our hosting runs on the LiteSpeed web server with servers in London, which suits UK visitors, and includes Redis object caching to take repeated database work off the site. See our pages on LiteSpeed hosting and Redis object cache for how these help WordPress in particular.
Combine a good server with sensible content and you will rarely need anything exotic. If you have done the basics and the site is still slow, contact us through live chat, open 24/7, and we can help you look at where the time is going.
LiteSpeed and Redis on every plan
The fast foundation for a quick WordPress site, from 84p a month (£10.03 billed yearly).
Content
Steps 4 to 7: make what you send smaller
4. Compress images
Resize to the display size and compress. Use WebP where you can.
5. Lazy load below the fold
Load images further down the page only when needed.
6. Minify and combine carefully
Smaller CSS and JavaScript load faster, but test after each change.
7. Limit fonts
Use one or two font families and the weights you need.
Code
Steps 8 to 12: trim the load
8. Remove unused plugins
Every active plugin adds work. Delete those you do not need.
9. Choose a light theme
Heavy multipurpose themes load a lot of code you never use.
10. Use a current PHP version
Newer PHP versions are faster. Choose one in the control panel.
11. Tidy the database
Remove old revisions and spam comments occasionally.
12. Be careful with third-party scripts
Chat widgets, ad tags and trackers can dominate load time.
Images
The image problem in detail
Images usually make up most of a page's weight. A photograph straight from a phone might be 4 MB, but the same picture resized to the width of your layout and compressed can be 150 KB. Multiply by a gallery and the difference decides whether your page loads in two seconds or ten.
Resize before upload when you can. Use a plugin to compress automatically, create WebP versions and serve the right size to each device. Check that large "hero" images at the top of the page are optimised, because they are what visitors wait for. Finally, avoid sliders with many large images, which add a lot of weight for little benefit.
Hosting and site
What your host does and what you do
Our hosting provides
- UK servers close to UK visitors
- The LiteSpeed web server
- Redis object caching
- Free SSL and HTTP/2 or newer protocols
- Isolation so neighbours do not slow you
You still manage
- Image sizes and formats
- Plugin choice and count
- Theme weight
- Third-party scripts
- The caching settings you choose
Troubleshooting
Common speed problems and likely causes
| Problem | Likely cause | Try |
|---|---|---|
| Slow first response | No page cache, or heavy plugins | Enable caching, remove heavy plugins |
| Fast on desktop, slow on mobile | Large images and scripts | Compress images, defer scripts |
| Layout jumps as it loads | Images without set sizes | Set width and height on images |
| Slow admin area | Too many plugins or no object cache | Add Redis, remove plugins |
| Fast then slow at busy times | Heavy traffic or bots | Check for bot traffic, use caching |
Keep it fast
Speed is a habit, not a one-off job
Sites slow down gradually, as plugins are added, images pile up and scripts accumulate. Re-test every few months and after any big change. Keep a note of what you changed and what it did, so you can undo something that hurts.
Remember the visitor. A fast site is a better experience, and it supports conversions and the page experience measures Google reports. It does not need heroic tuning, just sensible choices, good hosting and a little regular care.
FAQ
Common questions
What is the quickest way to speed up WordPress?
Turn on page caching with the LiteSpeed Cache plugin, and compress your images.
Do I need a CDN?
It can help if you have many visitors outside the UK. For UK audiences on UK servers, it is usually not necessary at first.
Does hosting really affect speed?
Yes. The web server, location and caching support all matter. LiteSpeed, UK servers and Redis give a strong start.
How many plugins is too many?
There is no fixed number. Quality and weight matter more than count, so remove those you do not need.
How do I test speed?
Use a speed testing tool on key pages on a mobile connection, and repeat a few times.
Keep reading
Related pages
Start from a fast foundation
LiteSpeed, Redis and UK servers on every plan.