Website Speed for Non-Engineers: The 20% That Gives 80%

Website speed advice tends to come in two flavours: engineering jargon you cannot act on, or plugin marketing that promises miracles. This guide is neither. It is the short list of things that actually move the needle for a normal site — a blog, a small business page, a portfolio — ranked by how much they matter, in language that assumes nothing.

Why speed matters at all

Two reasons, one human and one algorithmic.

Humans leave. Visitors on phones, on mobile data, mid-distraction, give a slow page a few seconds before hitting back. Google's own research on mobile behaviour found that the probability of a visitor abandoning a page climbs sharply as load time stretches from one second toward three. Every second of delay is paid in readers who never saw your content.

Google measures it. Since 2021, Google folds real-user speed metrics — the Core Web Vitals — into ranking. The headline metric is LCP (Largest Contentful Paint): how long until the main content of the page is visible. Google's threshold for "good" is 2.5 seconds. Speed will not rescue weak content, but between two comparable pages, the faster one has the edge — and the slow one frustrates the visitors it does win.

Measure before you touch anything

The single biggest mistake is optimizing blind: installing plugins and toggling settings without knowing what is actually slow. Do not guess. Run your site through PageSpeed Insights (pagespeed.web.dev) — Google's free testing tool. Paste your URL and it returns a mobile and desktop score plus, far more usefully, a list of your specific problems: "Properly size images", "Reduce unused JavaScript", "Reduce initial server response time", each with the exact files responsible and the estimated savings.

That list is your to-do list. If images dominate it, fix images. If server response time is flagged, no image plugin will help you. Test the homepage and one typical content page — they often have different problems.

The big four, in order of impact

1. Images — usually about half of your page weight

On a typical site, images account for roughly half of everything the browser downloads, which makes them the highest-leverage fix by far. The failure mode is always the same: a photo goes straight from a phone or camera to the page — 4,000 pixels wide and 4 MB — to be displayed in a 700-pixel column. One such photo outweighs the rest of the page combined; five of them is 20 MB, when the properly prepared versions would total well under 1 MB.

The fix is three steps: resize to roughly the display width (1,200–1,600 px covers most layouts), compress (JPEG quality around 80 is visually indistinguishable for photos), and use the right format — JPEG or WebP for photos, PNG only for graphics that need it. A 4 MB camera photo routinely lands under 150 KB after this treatment with no visible difference. Our image optimization guide walks through the full workflow; the Image Resizer handles resizing and WebP/JPEG export in your browser, and the PNG to JPG converter fixes the classic "photo saved as PNG" weight problem. If you want to understand why files balloon in the first place, see image file size, explained.

2. Too many plugins and scripts

Every widget has a price. A social share bar, a chat bubble, a fancy slider, an emoji library, an analytics tag you stopped reading in 2024 — each one loads its own scripts and styles, and each adds weight and delay to every page, whether the visitor uses it or not. Sites rarely get slow from one big mistake; they get slow from twelve small conveniences stacked over three years.

The fix is an audit, not a tool. List your plugins and embedded widgets and ask of each: has this earned its cost in the last month? Deactivate anything that has not, then retest. Removing five unused plugins routinely does more than any optimization plugin adds.

3. Caching — the free speed you may already have

Caching means saving the result of work so it is not redone. Without it, a WordPress-style site rebuilds every page from scratch — running code, querying a database — for every single visitor, then makes returning visitors re-download files they already have. With it, the server hands out a ready-made copy of the page (server-side caching), and the visitor's browser keeps your logo, styles and scripts locally so repeat visits skip the download (browser caching). Same site, fraction of the work.

The practical part: this is usually a toggle, not a project. Many hosts have server caching built in — check your hosting panel first. If not, one well-regarded caching plugin with default settings gets most of the benefit. One. (More on that below.)

4. Hosting quality — the ceiling on everything else

Everything above happens after the server answers, so a slow server caps your site no matter how lean the pages are. The number to watch is server response time (PageSpeed Insights flags it as "Reduce initial server response time"): consistently over 600 ms means the server itself is your bottleneck. Signs you have outgrown cheap shared hosting: the site is slow at peak hours but fine at 3 a.m. (you are sharing a strained machine), even simple pages are sluggish, resource-limit warnings appear in your hosting dashboard, or your images and caching are already sorted and the site is still slow. Moving from bargain shared hosting to a decent tier typically costs a few euros more per month and lifts every page at once.

How fast is fast enough?

Honest non-advice: do not chase 100/100. The last 20 points of a PageSpeed score cost more effort than the first 80 and deliver differences no visitor can feel. Scores are diagnostic tools, not trophies. The target worth having is "fast enough that nobody notices the wait": main content visible in under about 2.5 seconds on a phone — Google's own "good" LCP threshold. A site scoring 85 with a 2-second LCP has no meaningful problem. Fix the big four, hit that bar, then go write something worth loading.

Symptom → first thing to check

What NOT to do

• Do not stack optimization plugins. Two or three caching/optimization plugins do not add up — they collide. Each rewrites pages assuming it works alone; combined, you get double-cached pages, stale content that will not update, and bugs that are miserable to trace. Pick one and remove the rest.
• Do not flip every "minify / combine / defer" switch. These settings rewrite your site's code, and aggressive combinations are the classic cause of "my layout broke" and "my contact form stopped working" — often only on some pages, so you find out from a visitor. Enable one option at a time and click through the site after each.
• Do not optimize blind. Buying a CDN or a premium plugin before running PageSpeed Insights is buying medicine before the diagnosis. Measure, fix the flagged problem, measure again.

The bottom line

Measure with PageSpeed Insights, then work the list in order: images first, because they are usually half the weight; prune the plugins and widgets; switch on caching once; upgrade hosting if the server itself is slow. Stop when real pages feel instant on a real phone. Speed is part of what makes a site feel trustworthy and finished — the same reason the structural pages every site needs are worth getting right.