solobuild
A slow website costs you visitors before they read a single word, and if you are not a developer, the usual advice can feel like a wall of jargon. You do not need to understand server code to fix most speed problems. Most slow sites for one-person businesses come from a short list of causes: oversized images, no caching, too many plugins, and hosting that was picked on price alone. This guide walks through how to measure the problem, fix the biggest causes in order, and decide when the fix is really a hosting change.
Start by measuring, not guessing
Before you change anything, get a baseline. Open Google PageSpeed Insights, which is free, paste in your homepage URL, and run the test for mobile. The big colored score at the top is a lab estimate and it moves around from run to run, so treat it as a rough guide rather than a verdict. The numbers underneath it, called Core Web Vitals, are the ones Google actually uses as a ranking signal.
There are three of them. Largest Contentful Paint (LCP) measures how long the main content takes to appear, and a good score is under 2.5 seconds. Interaction to Next Paint (INP) measures how quickly the page responds when someone taps or clicks, and good is under 200 milliseconds. Cumulative Layout Shift (CLS) measures how much the page jumps around while loading, and good is under 0.1. Google judges these using real visitor data, and at least 75 percent of visits need a good result for a page to pass.
Write down your three numbers and the page you tested. Test your homepage, one blog post, and your most important sales or signup page, because they often have different problems. If your site is new and has little traffic, PageSpeed Insights may only show lab data, which is fine for tracking improvement even if it is not the official verdict.
Fix your images first
Images are the most common reason a small business site is slow, and they are also the easiest fix. A photo straight from a phone or camera can be 3 to 6 megabytes, while the same image at the size it appears on your page needs closer to 100 to 300 kilobytes. If your homepage has a large hero image at full camera resolution, that single file can push your LCP score into the red.
The fix has three parts. First, resize images to the largest size they will actually display, which is rarely wider than 1600 pixels. Second, compress them and save them in a modern format such as WebP, which is smaller than JPEG at similar quality. Third, turn on lazy loading, which tells the browser to wait on images further down the page until a visitor scrolls near them. WordPress does lazy loading by default now, but check that your main hero image is not lazy loaded, since that one should load first.
Free tools handle the resizing and compression well. Squoosh, a browser tool from Google, lets you drag in an image and see the size drop in real time. If you run WordPress, a plugin can convert your whole media library in bulk, and many caching plugins include this feature. Do this once for your existing images and then make it a habit for new uploads, since a single forgotten large file can undo the work.
Turn on caching
Caching means your server saves a ready-made copy of each page instead of building it from scratch for every visitor. Without it, WordPress has to run code and query a database each time someone lands on your site, which is slow even for small pages. With it, the visitor gets a finished page almost instantly. For most non-developers, this is the single biggest speed gain after images.
You do not need to configure this by hand. Many hosts include caching, and there are plugins for the rest. SiteGround, for example, ships with its own optimization plugin and a three-level caching system called SuperCacher, so a lot of this is a matter of switching on the right options in the dashboard. Reviewers of the plugin generally say it handles caching well but is less strong on Core Web Vitals fine-tuning, and some people pair it with a dedicated performance plugin such as LiteSpeed Cache or FlyingPress if they need more. That is a reasonable second step, not a first one.
Whatever tool you use, change one setting at a time and check your site afterward. Aggressive options like combining or delaying JavaScript files can break menus, forms, or checkout buttons on some sites. If something looks wrong after a change, turn that one option off again, and you will know exactly what caused it.
Cut the plugins and scripts you do not need
Every plugin adds code, and many add extra files that load on every page even when the feature is only used on one. A site with 30 plugins is usually slower than one with 10, though the number matters less than what each plugin does. A heavy page builder, a slider, and a social feed plugin can each add more weight than ten small utilities combined.
Go through your plugin list and remove anything you have not used in the last few months. Deactivating is not enough, so delete the plugin entirely, and back up your site first in case you remove something that turns out to be needed. Then look at third-party scripts, which are the snippets from outside services such as chat widgets, analytics, ad pixels, and font libraries. Each one makes your visitor's browser talk to another server, and a slow external service can drag down your whole page.
A useful rule is to keep a script only if you can name the decision you made because of it. If you have three analytics tools and only look at one, remove the other two. Fonts deserve a check too, since loading four font weights from an outside service is a common hidden cost, and one or two weights is usually enough for a clean design.
Look at your hosting
If you have fixed images, turned on caching, and trimmed plugins and the site is still slow, the problem is probably your hosting. Cheap shared hosting puts many sites on one server, and when a neighbor gets busy, your site slows down. The clearest sign is a long wait before anything starts to load, which PageSpeed Insights reports as a slow server response time, sometimes called time to first byte.
Hosting is also where entry-level plans can mislead you. SiteGround's StartUp plan, for instance, has been listed at a promotional price of about $2.99 per month, but renewal rates reported in 2026 run much higher, around $17.99 per month, so check the renewal price before you commit. The entry plan is aimed at one low-traffic site, and reviewers note it has tighter server resources than higher tiers. The GrowBig plan adds staging, more resources, and the full caching stack, which is why many people who outgrow StartUp move up rather than switching hosts entirely.
If you do decide a hosting change is needed, SiteGround is one option worth looking at, since managed WordPress hosting with built-in caching removes several of the steps above. You can see current plans on the SiteGround site. Whichever host you pick, read the renewal price, ask whether they will migrate your site for you, and take a full backup before any move.
Tools compared
| Tool | Best For | Free Tier | Starting Price |
|---|---|---|---|
| Google PageSpeed Insights | Measuring Core Web Vitals | Yes, fully free | Free |
| Squoosh | Compressing single images | Yes, fully free | Free |
| SiteGround SG Optimizer | Caching and image tweaks on SiteGround hosting | Plugin is free with a SiteGround plan | Hosting from about $2.99 per month promo, higher at renewal |
| LiteSpeed Cache | Deeper Core Web Vitals tuning | Free plugin, works best on LiteSpeed servers | Free |
A simple order of work
Because these fixes overlap, the order matters. Start with images since they help every page and carry almost no risk. Move to caching next, then remove unneeded plugins and scripts, and only then consider a hosting change. Test with PageSpeed Insights after each step and write the numbers down, so you can see which change did the work and stop when you reach good scores.
A realistic goal for a solo business site is passing all three Core Web Vitals on your key pages, not a perfect 100 score. Once you pass, speed becomes a maintenance task. Check your homepage once a month, compress new images before uploading, and review your plugin list every quarter.
FAQ
Why is my website so slow?
The most common causes are oversized images, missing caching, too many plugins, and slow shared hosting. Run your page through PageSpeed Insights and look at which metric is poor, since a slow LCP usually points to images or server response, while a poor CLS points to elements that load late and push content around.
How fast should my website load?
Aim for a Largest Contentful Paint under 2.5 seconds, an Interaction to Next Paint under 200 milliseconds, and a Cumulative Layout Shift under 0.1. These are the thresholds Google treats as good, and they apply to both mobile and desktop, though mobile is harder to pass.
Does website speed affect SEO?
Yes, Core Web Vitals are a ranking signal, though content relevance still matters more. A slow site also loses visitors directly, since people leave pages that take too long, which hurts conversions regardless of rankings.
Can I speed up my site without coding?
Yes. Image compression, a caching setting or plugin, removing unused plugins, and choosing better hosting all work without touching code. Change one thing at a time and retest, so you can undo anything that breaks a page.
Will changing hosts make my website faster?
It can, especially if your server response time is slow or you are on an overcrowded shared plan. If your images are huge or your site runs many heavy plugins, a new host will help less than fixing those first.
Where to go from here
Speed work rewards patience and a simple routine. Measure first, fix images, turn on caching, remove what you do not use, and move hosting only when the earlier steps have not been enough. Most one-person sites get to good scores with the first three steps alone, and the numbers you record along the way will show you exactly when to stop.