A slow website loses visitors and rankings. This is a plain-English, do-it-yourself guide to making yours faster — no code, no jargon. It explains what Google measures, how to test where you stand, and the actual steps to fix the things that slow most websites down. Work through it in order and you’ll make real, measurable improvements.
People are impatient. A page that takes more than a couple of seconds to appear loses a chunk of its visitors before they’ve seen anything — and the slower it gets, the more leave. Google knows this, so page speed is a confirmed ranking factor: faster sites tend to rank higher, and slow ones get held back. Speeding up your site therefore does two jobs at once — it keeps visitors, and it helps you climb the results.
Google grades your page on three measurements, together called Core Web Vitals. It judges them on real visitors’ experiences, and to “pass” at least 75% of your visits need a good score:
You don’t need to memorise the numbers. Just remember: appear fast, react fast, don’t jump.
Never guess at speed — measure it, so you fix the real problems and can prove the fixes worked. Put your page’s web address into the Core Web Vitals check. It scores your loading, responsiveness and stability and tells you in plain English which ones need work. For a fuller picture of what’s slowing the page, also run the Page Speed test. Write down your starting scores so you can compare after each fix.
For most websites, oversized images are the number-one cause of slowness. A photo straight from a phone or camera can be 5–10 megabytes, when a web page rarely needs more than a few hundred kilobytes. Fixing this alone often transforms a page’s loading score. Do these three things:
If you’re on WordPress, an image-optimisation plugin can resize, compress and convert your images automatically, including ones you’ve already uploaded.
That annoying jump where text shifts down as an image pops in is bad for your stability score (CLS) and irritating for visitors. The cause is the browser not knowing how big something will be until it loads, so the page re-arranges itself. The fix is to tell it the dimensions in advance: every image, video, advert and embedded box should have its width and height set, so the browser reserves the space before the content arrives. On most website builders this happens automatically; if you add images by hand, make sure they include width and height.
Before your page can even start loading, your web host’s server has to respond. On cheap, overcrowded shared hosting that first response can take over a second — pushing you past the loading threshold before a single image downloads. If your test shows a slow “server response time” (sometimes called TTFB), the fix is better hosting: a faster or less crowded plan, or a host with servers nearer your customers. A content delivery network (CDN), which stores copies of your site around the world and serves each visitor from the nearest one, also helps a lot and many are inexpensive or free.
Every theme, plugin, tracking script and chat widget adds weight the browser must download and run, which hurts both loading and responsiveness. Trim it: remove plugins and scripts you don’t actually use, choose a lightweight theme rather than a bloated “does-everything” one, and avoid stacking multiple analytics or social widgets. If you’re comfortable with your platform’s settings, enabling caching (which saves a ready-made copy of each page so it doesn’t get rebuilt every visit) and “minifying” CSS and JavaScript (stripping out spare characters) gives a further lift. Most WordPress caching plugins do both with a couple of clicks.
After each change, run the Core Web Vitals check again and compare to the starting scores you noted. Fixing things one at a time and re-testing tells you what actually worked. Bear in mind Google’s official scores are based on real visitor data gathered over time, so after a fix the lab test improves immediately but the “official” pass can take a few weeks to catch up as new visitor data comes in.
Take a small business homepage that feels sluggish. The owner runs the Core Web Vitals check and sees a poor loading score and a lot of layout shift. They discover the hero photo is a 6 MB image straight off a camera, so they resize it to the width it’s shown at and compress it with a free tool — it drops to under 200 KB. They set width and height on every image so the page stops jumping. They remove three plugins they no longer use and turn on caching. They re-test: loading is now under 2.5 seconds and the jumping is gone. None of it required writing code — just resizing pictures, a setting or two, and removing clutter.
A few habits keep sites slow. Uploading full-size images straight from a camera. Adding every plugin and widget that looks useful and never removing the ones you stop using. Choosing the cheapest possible hosting and wondering why the server is slow. Adding images by hand without width and height, so the page jumps. And changing lots of things at once, so you can’t tell what helped. Avoid these and you’ll keep the gains you make.
Aim for your main content to appear in under 2.5 seconds, the page to react to taps in under 200 milliseconds, and almost no layout jumping. These are Google’s Core Web Vitals “good” thresholds.
For most sites it’s oversized images, followed by slow hosting, too much code from themes and plugins, and layouts that shift as they load.
No. The biggest wins — resizing and compressing images, setting image dimensions, removing unused plugins, enabling caching, and improving hosting — need no coding.
Put your page’s address into the Core Web Vitals check and the Page Speed test. They score your speed and tell you in plain English what to fix. Re-test after each change.
Google’s official scores use real visitor data collected over time, so a fix shows instantly in a lab test but can take a few weeks to appear in Google’s assessment as new data comes in.
Yes. Core Web Vitals are a confirmed ranking factor, and faster pages also keep more visitors, so speed helps both your rankings and your conversions.