Open your own site on your own phone, on mobile data, away from the office. Count the seconds. That number is what your customers experience.
How to measure it properly
The speed that matters is not what your laptop sees on office wifi. Google judges your site on the mobile render, on a mid-range device, on a normal connection. So should you.
The metric to watch is Largest Contentful Paint: how long until the main thing on the page appears. Under two and a half seconds is the threshold; under two is where we set our own build spec.
Field data beats lab tests. If you have enough traffic, the Core Web Vitals report in Search Console tells you what real visitors experienced rather than what a test tool simulated.
The four usual causes
- Images. A hero photo exported at 4000 pixels wide and 3 MB, scaled down in the browser. The single most common cause, and the easiest to fix.
- Page builders. Visual builders ship every feature to every page. The convenience is real; the weight is the price.
- Fonts. Four weights of two families, loaded before anything renders, each one a round trip.
- Third-party scripts. Chat widget, three analytics tags, a heatmap, two ad pixels. Each one is someone else\u2019s server deciding how fast your site is.
What it costs
The relationship between load time and conversion is one of the few things in this field with consistent evidence behind it: each additional second of delay measurably reduces the share of visitors who complete an action, and the effect is sharpest on mobile.
For a business running paid traffic the arithmetic is direct. You are buying the click either way. A slow page means a share of those clicks bounce before the page renders, which is the most expensive way to waste a marketing budget.
Fixing it without a rebuild
Most of the gain is in four jobs: resize and convert the images, cut the font loading to what the design actually uses, remove or defer the third-party scripts nobody checks, and enable proper caching and compression on the server.
On most sites that is days of work rather than a rebuild, and it is the first thing we look at before recommending anything more expensive. It is also part of every build we do, rather than an optimisation phase bolted on at the end.