Website Speed Is a Business Metric, Not a Technical One
Site speed gets filed under “technical”, which is why it rarely gets fixed. It belongs on the same page as your conversion rate. A visitor who leaves before your page renders is indistinguishable, commercially, from a visitor who never came — except that you probably paid to bring them.
The pattern is consistent: as load time climbs from one second toward five or six, the share of people who abandon rises steeply. And this hits hardest exactly where it hurts most — mobile visitors on ordinary connections, who are often the majority.
What Google actually measures
Google’s Core Web Vitals reduce this to three numbers, and they are worth knowing because they map to things a real person feels:
- LCP (Largest Contentful Paint) — how long until the main content appears. The target is 2.5 seconds or less. This is the “is this thing working?” moment.
- INP (Interaction to Next Paint) — how quickly the page responds when someone taps or clicks. The target is 200 milliseconds or less. This is the “did that button do anything?” moment.
- CLS (Cumulative Layout Shift) — how much the page jumps around while loading. The target is 0.1 or less. This is why you tapped the wrong thing when an advert loaded late.
These feed into search ranking, but ranking is the smaller prize. The bigger one is that fast sites convert better, and the effect is measurable long before Google notices.
What usually causes slowness
In practice it is nearly always the same short list:
- Enormous images. A 4 MB photo straight off a phone, scaled down in the browser rather than on the server. This is the single most common cause and the easiest to fix — resize properly and serve modern formats like WebP.
- Too much JavaScript. Every plugin, tracker, chat widget and A/B testing script has to be downloaded and executed before the page settles.
- Third-party embeds. Analytics, ad pixels, social feeds, font services. Each adds a connection to a server you do not control, and your page waits for the slowest one.
- Server-rendered pages with no caching. Rebuilding the same page from a database on every request, when it has not changed in a month.
- Images and ads without reserved space. The main driver of layout shift — fixed by declaring width and height so the browser leaves the right gap.
Fixes, in order of return
Start with images: resize them, compress them, serve WebP, and lazy-load anything below the fold. This alone resolves a large share of failing sites.
Then audit your third-party scripts and remove what nobody looks at — most sites carry at least one tracker installed for a campaign that ended years ago. Self-host your fonts. Declare image dimensions. And if pages are being generated per-request for content that rarely changes, consider whether they should be static at all, which is the core of static sites vs WordPress.
Measure it yourself, today
Run your homepage through Google’s PageSpeed Insights, then do the honest test: open your site on your phone, on mobile data, not office wifi. That is the experience most of your visitors are having.
Speed is also a trust signal. A site that responds instantly reads as a business that has its act together — part of the broader digital identity picture.
Want us to look at why yours is slow? Get in touch — the diagnosis is usually quick, and the fixes are often smaller than expected.