Someone told you your website is slow. Maybe it was a customer, maybe your nephew, maybe a red number on Google’s PageSpeed test that made your stomach drop. Now you are wondering whether this is something you can fix on a Saturday afternoon or something you need to pay a developer for.
The honest answer is: some of both. A handful of fixes are well within reach of anyone who can log in to WordPress. Others need someone who can read code and server logs without guessing.
This guide walks you through how to measure your site properly (most people skip this and waste hours), the fixes that give beginners the biggest payoff, the jobs that usually need a pro, and a short checklist you can start on today.
Step one: measure before you touch anything
It is tempting to install a speed plugin and hope. Resist that. If you do not know what is slow, you cannot tell whether your change helped, hurt, or did nothing at all.
Start with Google’s PageSpeed Insights. Paste in a page address and look at the results for mobile first, because that is where most sites struggle and where many of your visitors are.
Field data and lab score are not the same thing
PageSpeed Insights shows you two different kinds of results, and mixing them up causes a lot of panic.
- Field data (the section about what real users are experiencing) comes from actual Chrome visitors to your site over recent weeks. This is what Google uses when it judges page experience. Smaller sites may not have enough traffic to show it.
- The lab score (the big number out of 100) is a single simulated test run on Google’s machines. It is useful for spotting problems, but it can swing noticeably between runs on a page that has not changed.
We have seen lab scores disagree with what real visitors experience, which is why we also test pages in real browsers before deciding what to fix. Treat the score as a guide, not the goal.
Test the pages that actually matter
Your home page is a good start, but it is not the whole story. Test the pages people land on most: your top service pages, any page your ads point to, your contact or booking page, and for a store, a product page and the cart.
Then pull out your own phone, turn off Wi-Fi, and load those pages over mobile data. Watch what appears first, what jumps around, and how long it takes before you can tap something. That five-minute test tells you a lot.
Core Web Vitals in plain words
Google measures page experience with three numbers called Core Web Vitals. The names are jargon, but the ideas are simple. Google’s own explainer on Web Vitals goes deeper if you want it.
| Metric | What it means | Google’s “good” threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | How long until the main thing on the page shows up | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How quickly the page responds when someone taps or clicks | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much the page jumps around while loading | 0.1 or less |
The culprit is often not what you would guess. Before fixing anything, look at which element PageSpeed Insights reports as the largest one on the page. Sometimes it is a hero image, but it can just as easily be a block of text, a slider or even a cookie banner. Compressing images will not help if the slow part is something else.
Measure first. The thing slowing your page down is often not what you would guess.
PageSpeed Insights names your LCP element in its diagnostics. Find it before deciding where to spend your time.
Five fixes a beginner can make, in order of payoff
These are the changes that most often make a real difference on small business WordPress sites, roughly in the order we would tackle them. Take a backup before you start, and change one thing at a time so you know what helped.
1. Shrink oversized images and use modern formats
This is the classic problem. A photo straight off a phone or from a stock site can be several times larger than any screen will ever display, and WordPress happily serves it to every visitor.
- Resize images before uploading. A full-width banner rarely needs to be wider than about 2,000 pixels, and most in-content images can be much smaller.
- Use an image optimization plugin that compresses images and converts them to WebP or AVIF. Both formats are much lighter than old JPEGs and PNGs at the same visual quality, and modern browsers support them.
- Lazy loading (images loading only as you scroll toward them) is built into WordPress. One catch: the main image at the top of the page should not be lazy loaded, or it arrives late and hurts your LCP.
2. Turn on page caching
Without caching, WordPress builds every page from scratch for every visitor: running PHP, querying the database, assembling the result. A page cache saves the finished page and hands it straight out next time, which is much faster.
Check with your host first. Many WordPress hosts already cache pages at the server level, and adding a caching plugin on top can cause conflicts. If your host does not, a reputable caching plugin with its default settings is a sensible start.
One trap to know about: after you change a page, the cache can keep serving the old, slow (or even broken) version until it is cleared. We have run into this ourselves. Whenever you make a speed fix, purge the cache and then re-test, or you may be measuring yesterday’s page.
3. Cut plugins and third-party scripts you do not need
Every chat widget, tracking pixel, social feed, review carousel and slider adds code that every visitor has to download. Some of it loads on every page, even pages that never use it.
Go through your plugin list and your marketing tags and ask of each one: do we still use this, and is it worth what it costs in speed? Common candidates for removal:
- Old tracking codes for tools nobody logs in to anymore
- Sliders and carousels at the top of the home page (they are heavy, and they push your main message further down the page)
- Chat widgets that load instantly when they could load after a delay or on a click
- Plugins that duplicate each other, such as two SEO plugins or two form plugins
- Deactivated plugins sitting around (delete them, they are a security risk even when inactive)
4. Be careful with fonts
Fonts are easy to overdo. Each font family and each weight (regular, bold, italic and so on) is a separate file. A theme that loads three families in six weights can quietly add a lot of weight before any text appears.
Stick to one or two families and only the weights you actually use. If your theme or page builder has a setting to load fonts locally rather than from an outside service, it is usually worth turning on.
5. Check your hosting
If your pages take a long time before anything starts arriving at all (PageSpeed calls this server response time), no amount of image compression will save you. The bottleneck is the server.
Cheap shared hosting puts your site on a server with many others, so your speed depends on what your neighbors are doing. Signs you have outgrown your host: slow admin dashboard, slow response even on simple pages, and trouble during busy periods. A good managed WordPress host gives your site its own resources and people who understand WordPress. If you are weighing a move, here is how we approach fast managed WordPress hosting.
What usually needs a developer
Once you have done the basics, the remaining problems tend to live deeper in the site. These are the jobs where a confident beginner can do real damage, or spend days without moving the needle.
- Heavy page builders. Page builders make editing easy but can produce a lot of extra code, nested layout containers and styles for every page. Slimming that down without breaking the design takes experience.
- Theme bloat. Multipurpose themes often load features you do not use on every page. Fixing it can mean selectively unloading files or moving to a lighter setup.
- Render-blocking scripts and styles. Some files stop the page from showing anything until they finish loading. Deferring or trimming them helps a lot, but done carelessly it breaks menus, forms and checkouts.
- Database clutter. Years of revisions, expired temporary data and leftovers from removed plugins can slow the site down. Cleaning it is worth doing, with a backup first, because a wrong deletion is hard to undo.
- Server configuration. PHP versions, server caching layers and similar settings can make a big difference, and they are rarely something you can change from the WordPress dashboard.
Your “do this today” checklist
If you only have an hour, this is where to spend it.
- Run your home page and your two or three most visited pages through PageSpeed Insights on mobile. Write down the LCP, INP and CLS numbers, and note which element is your LCP element.
- Load the same pages on your phone over mobile data and note what feels slow.
- Take a full backup of your site.
- Find the biggest images on those pages and replace them with properly sized, compressed versions, ideally in WebP or AVIF.
- Ask your host whether page caching is on. If not, set up a caching plugin.
- Delete plugins you no longer use and remove tracking codes for tools you have abandoned.
- Purge your cache, then re-test the same pages the same way and compare.
Keeping it fast after you fix it
Speed is not a one-time job. Sites drift slower as new plugins get added, new images get uploaded at full size and new marketing scripts get pasted in.
A good habit is to re-run your tests every few months and after any big change, like a new plugin or a redesigned page. If you would rather have someone keep an eye on it, a website care plan keeps your site updated, monitored and fast month after month.
When DIY is enough, and when to get help
If your site is mostly slow because of big images, no caching and a few plugins you forgot about, you can likely fix it yourself with this guide. Plenty of sites get noticeably faster from the beginner fixes alone.
It is time to get help when you have done the basics and the numbers barely moved, when the problem is in the theme, page builder or server, when you run a store and cannot risk breaking checkout, or when your ads are sending paid clicks to a slow landing page.
That is the work our WordPress speed optimization service does. We test your key pages in a real browser on a slow phone connection, find what is actually slowing them down, fix it by hand with a backup first, and then run the same tests again so you get a clear before-and-after report. Most of the time that happens on the site you already have, without a rebuild.
Not sure which camp you are in? Send us the pages that feel slow and we will tell you honestly what we would fix.
