How to Speed Up WordPress: 10 Fixes That Actually Move the Score
A slow WordPress site does not feel slow in one place. It feels slow everywhere: the page takes a moment to start, the words appear late, the images jump around, and the button you want to tap moves just as your finger reaches it. Visitors do not diagnose that. They leave, or they try again on a competitor site. Speed is mostly about what loads before the first words appear, not about the total size of the page. This guide shows you how to measure it properly, then the ten fixes that actually move the score, in the order that matters most.

Most speed advice is a long list of small tweaks, with no order and no warning about what can break. That is how sites end up faster on a test, and broken for real visitors, with a form that will not submit or a menu that will not open. The order here is deliberate. Measure first, fix the biggest cause, test after each change, and only then move to the next one. You do not need a rebuild to get a fast site. You need to remove what is in the way, in the right order, and to leave alone the things that are already working.
This guide is written for a business owner, or for the person who looks after a business site, not for a server engineer. You will not need to edit code. You will need to be able to install a plugin, change a setting, and check a score, and to know when to ask for help. Where a fix can break something, this guide says so, and tells you what to test. By the end you should know your score, your biggest cause, and the next three things to do, in order.
Measure first: what LCP means in plain words
Before you change anything, measure. A feeling that the site is slow is not a diagnosis, and a single test on a fast office connection is not proof. Use Google PageSpeed Insights, which is free, and test both mobile and desktop, because the mobile score is usually the lower one, and most visitors arrive on a phone.
Largest Contentful Paint, usually shortened to LCP, is the plain English version of the most important number. It is the time until the largest thing on the page, usually the main heading or the main image, appears. If that takes more than two and a half seconds, visitors notice. If it takes more than four seconds, many of them leave.
- Test three times, at different times of day. Speed changes with traffic, and one test can be a bad day for the server.
- Write down the score, the LCP time, and the biggest file. That is your baseline, and the only way to know whether a fix helped.
- Test the page your visitors actually land on. Your home page may be fine, while a service page with a large image is the slow one.
- Ignore the score for a moment, and watch the page load. What appears first, what jumps, and what arrives last? That tells you what to fix first.
Do not start with a plugin, a new theme, or a new host. Start with a number, and a note of what you saw. Everything after this section is a fix for a specific cause, and you will know which one is yours.
The five fixes that move the score most
1. Caching: serve a ready page, not a fresh build
WordPress builds every page from scratch, every time someone visits, unless caching is on. Caching saves a finished copy of the page, and serves that copy to the next visitor, so the server does almost no work. A good caching plugin, like WP Rocket, LiteSpeed Cache, or W3 Total Cache, can cut a second or more from the first load. Turn it on, then test the site as a visitor: submit a form, use the menu, and check the cart if you have one. If a page shows old content, clear the cache and check the settings for logged-in users and forms.
2. Images and WebP: the biggest files are usually pictures
Images are usually the largest files on a page, and the easiest to shrink. Resize each image to the size it is actually shown at, not the size the camera produced. Convert images to WebP, which is smaller than JPEG or PNG at the same quality, and is supported by all modern browsers. Compress them, so a photo that was 800 kilobytes becomes 150 kilobytes, with no visible difference. Then check that images below the fold load only when the visitor scrolls to them. A page with ten large images will always be slow, however good the hosting is.
3. Plugin audit: remove what you do not use
Every plugin adds code, and some add code to every page, even when you only use them on one. Go through your plugins and ask, for each one, what it does, when you last used it, and whether WordPress, your theme, or another plugin already does it. Remove the ones you do not need, and replace a heavy plugin with a lighter one where you can. Do not judge by the number alone, twenty light plugins can be faster than five heavy ones, but a site with forty plugins is carrying a lot of code it does not need. Test after each removal, so you know which one mattered.
4. Fonts: load fewer, and load them properly
Fonts are small, but they block the first words from appearing. A site that loads five font families, each in three weights, is loading fifteen files before the text can show. Keep to one or two font families, and only the weights you actually use. Host the fonts on your own site, instead of loading them from Google Fonts on every visit, so there is no extra connection to make. Use font-display: swap, so the text appears in a system font first, then changes to your font when it arrives, instead of leaving a blank space where the words should be.
5. Render-blocking CSS and JS: stop the files that hold up the first words
Render-blocking files are stylesheets and scripts that the browser must load before it can show anything. The browser reads them first, and the visitor sees a blank page while it does. The fix is to delay the files that are not needed for the first screen, and to load the rest after the page appears. Most speed plugins have a setting for this, usually called defer, delay, or remove render-blocking resources. Use it carefully, and test after each change, because delaying the wrong script can break a form, a menu, or a slider. If something stops working, undo that one setting first.
Hosting and PHP: the foundation under every fix
Speed fixes work best on a good foundation. If the server is slow, every other fix is fighting it.
PHP version. WordPress runs on PHP, and newer versions are faster. A site on PHP 7.4 will be noticeably slower than the same site on PHP 8.1 or 8.2, for no other change. Ask your host which version you are on, and move to a supported version, then test the site, because a very old plugin may not work on new PHP.
Hosting. Shared hosting can be slow at busy times, when other sites on the same server are busy. A managed WordPress host, a VPS, or a cloud plan gives your site more room, and a faster first response. At itcroc LLC, Website Development starts from $1,300, and a WordPress Care Plan from $49 a month covers updates, backups, monitoring, and security, so speed does not drift back as plugins age.
Database. WordPress keeps every revision, every draft, and every trashed item. Cleaning those out, and removing old transient data, makes the database smaller and faster to search.
Keep WordPress, themes, and plugins updated. Updates often include speed improvements, as well as security fixes, and an old version can be slow for a reason that was fixed a year ago.
Your WordPress site does not have to feel slow.
Most slow WordPress sites have the same few causes, and they are fixable without a rebuild. Send us your site and we will find the biggest one first.
What to check, and what not to do
Three more fixes, then the warnings that matter most.
6. Lazy loading and video embeds. Load images and videos only when the visitor scrolls to them. A YouTube embed loads a lot of code before the visitor ever presses play, so replace it with a still image that loads the video only when it is clicked. That one change can cut a second from a page with a video.
7. Database and revision cleanup. Limit post revisions to five or fewer, empty the trash regularly, and clean old revisions, spam comments, and expired transients. A smaller database answers faster, and a backup takes less time too.
8. Reduce redirects and third-party scripts. Every redirect adds a round trip, so fix old links instead of redirecting them, and remove chat widgets, tracking scripts, and social feeds that you do not use. Each one is a file your visitor’s browser must fetch before the page can finish.
Test after each change, and keep a note of the score before and after. If a fix makes the score worse, undo it, and move to the next one. Speed is a series of small wins, not one big change.
Do you need a CDN?
A content delivery network, usually called a CDN, keeps copies of your site on servers around the world, and serves each visitor from the nearest one. It helps when your visitors are far from your host, and when your site has a lot of images and files to serve.
- You probably need one if your visitors are in several countries, or your host is on another continent.
- You probably do not need one if your visitors are all local, and your host is already fast. A CDN will not fix a slow server.
- Start free. Cloudflare has a free plan that is enough for most small businesses, and it also adds a basic firewall.
Turn it on, clear your cache, and test again. If the score does not move, the cause was somewhere else.
10. Keep the theme and page builder lean
The tenth fix is the one people resist most, because it means changing something they chose.
- A heavy theme adds code to every page. A theme with a built-in page builder, sliders, and animations will be slower than a light theme, however good the hosting is.
- Do not use two page builders. If you use Elementor, do not also load another builder, or a theme builder, on the same page.
- Remove unused sliders and animations. A slider with five large images is five images to load before the visitor sees anything.
You do not need a new theme to be fast, but you do need to know what your theme is loading, and to remove the parts you do not use.
What not to do
Speed work can break a site, and the break is usually silent, so test like a visitor, not like an owner.
- Do not delay every script at once. Delaying scripts can break forms, menus, and checkout. Delay one group at a time, and test each form and menu after each change.
- Do not minify everything aggressively. Combining and minifying CSS and JavaScript can break layout and scripts. If the site looks wrong after minification, turn that setting off first.
- Do not chase a perfect score. A score of 90 on mobile, with a fast LCP, is a good result. A score of 100, with a broken form, is not.
- Do not change five things at once. If the site breaks, you will not know which change did it.
If something stops working, undo the last change, clear the cache, and test again before you try the next one.
How to keep your site fast without a rebuild
- Check the score once a month. A new plugin, a new image, or a new embed can undo a month of speed work in a day.
- Compress every image before you upload it. Resize it, convert it to WebP, and check its size. A photo over 300 kilobytes is usually too large for a web page.
- Keep plugins to what you use. Remove a plugin when you stop using it, instead of leaving it deactivated.
- Keep WordPress, themes, and plugins updated. Updates include speed and security fixes, and a care plan can do this for you. A WordPress Care Plan from $49 a month at itcroc LLC covers updates, backups, monitoring, and security.
- Test after every change. A form, a menu, and a checkout, every time. Speed that breaks the site is not speed.
A worked example: a slow site, before and after
To make this concrete, here is a realistic before and after, for a small services business site with twelve pages, a blog, and a contact form.
- Before: PageSpeed mobile score 42, LCP 4.8 seconds. No caching, ten plugins, large JPEG images, a YouTube embed on the home page, and PHP 7.4 on shared hosting.
- Fixes, in order: caching on, images resized and converted to WebP, three unused plugins removed, fonts reduced to one family, render-blocking scripts delayed, video replaced with a click-to-play image, and PHP updated to 8.2.
- After: PageSpeed mobile score 88, LCP 1.9 seconds. No rebuild, no new theme, and no change to the design. The work took a day, and the biggest single gain came from caching and images, not from the host.
The point is not the exact score. A site that loads in under two and a half seconds feels fast, and a site that takes five seconds feels broken, even if the design is the same.
So what should you budget?
Do it yourself. A caching plugin and an image plugin are often free, and the work is a day of careful testing. The cost is your time, and the risk is breaking a form if you delay the wrong script.
Get help with the fixes. A speed review and fix, with testing, is usually a small project, not a rebuild. At itcroc LLC, Website Development starts from $1,300, and a WordPress Care Plan from $49 a month keeps the site updated, backed up, and monitored after the fixes.
Rebuild only if the theme is the cause. If the theme or the page builder is loading most of the code, a rebuild on a light theme may be cheaper than a year of fighting it. A rebuild is a decision to make after measuring, not before.
Keep a monthly check. A care plan from $49 a month, $169 a month for a busier site, or $339 a month for a shop, covers updates, backups, monitoring, and security, so speed does not drift back.
Our prices, in the open
At itcroc LLC, we publish our prices because we believe you should be able to budget before you ever talk to us. These are the services that sit around speed work:
- Website Development (WordPress or Framer) from $1,300
- UI/UX Design from $1,200
- Brand Identity from $600
- Motion Design from $320
- WordPress Care Plans from $49/month
Every project is a fixed price agreed before we start, 50% to begin, 50% on delivery. No hourly billing, and no surprise renewal price on our work.
Frequently asked questions
Why is my WordPress site slow?
Most slow WordPress sites have the same few causes: no caching, large images, too many plugins, heavy fonts, and render-blocking scripts. A slow host or an old PHP version can add to it. Measure first with PageSpeed Insights, then fix the biggest cause, and test after each change.
What is a good PageSpeed score?
A mobile score of 90 or more is good, and a score of 80 to 89 is still usable if the LCP time is under two and a half seconds. The score matters less than the LCP time and whether the page feels fast. A perfect score with a broken form is not a good result.
Does caching break my site?
It can, if it is set up badly. Caching can show old content, or break a form, a cart, or a logged-in page. Use a good caching plugin, exclude forms, carts, and logged-in pages, and test the site as a visitor after you turn it on. If something breaks, clear the cache and check the settings first.
Do I need a CDN?
You need a CDN if your visitors are far from your host, or in several countries. You probably do not need one if your visitors are all local and your host is already fast. A CDN will not fix a slow server, a large image, or a heavy plugin. Start with a free plan, and test whether the score moves.
How many plugins is too many?
There is no single number. Twenty light plugins can be faster than five heavy ones. A site with forty plugins is carrying a lot of code, and some of it will be running on every page. Remove the ones you do not use, replace heavy plugins with lighter ones, and test after each removal.
Will a faster site rank higher on Google?
Yes, a little. Google uses page speed as a ranking signal, and a fast site also keeps visitors longer, which helps in other ways. Speed alone will not rank a poor site, and useful content still matters most. A fast site with good content will do better than a slow site with the same content.
Not sure what your site actually needs?
Start with a free UX audit. Send us your current website and a senior designer will review it by hand and send you a clear report on what to fix first, including whether speed, the build, or both are holding it back. Get your free UX audit, or book a free 30-minute discovery call if you would rather talk it through first.
Keep reading
Build Better Digital Experiences.
itcroc helps businesses create modern websites, UI/UX design systems, Framer landing pages, and scalable WordPress solutions for optimal performance and growth.


