Service
Fast is a feature nobody thanks you for
Nobody praises a site for loading quickly. They just stay — which is the only part that matters.
The test that matters is a phone on a bad connection
The real audience is on a phone, on cellular, possibly outdoors, often on a device several years old. That is where the gap between a light page and a heavy one stops being a number and becomes whether somebody waits.
Which is why speed is measured on the hardware and the connection people actually have, rather than on the machine that produced the site.
A site is not fast because it opens instantly on the laptop it was built on. That is the one device it was guaranteed to be fast on.
Weight is a design decision before it is a technical one
Most slow sites are not badly coded. They are heavy by accumulation: a theme that ships code for every business that might buy it, a hero video, four font weights, a chat widget, an analytics tag, a heatmap tool, a booking embed and a cookie banner — each added by somebody reasonable, none removed.
So the fix usually starts with subtraction rather than optimization. Building custom means the page ships what it uses; images are sized and encoded for the slot they occupy; fonts are subset and self-hosted; and every third-party script has to justify the delay it adds to everybody's visit.
Core Web Vitals, in plain terms
Google measures three things, and they map onto complaints an ordinary person would actually voice. They also feed ranking, so the same work serves two purposes.
- 01
"Nothing appeared" — LCP
How long until the main thing on screen is there. Usually decided by image weight and by whether the page holds content hidden until a script runs.
- 02
"It jumped as I tapped" — CLS
Content shifting after it appears, because space was never reserved for an image, a font swap or a late-loading banner. Cheap to prevent, infuriating to experience.
- 03
"It froze for a second" — INP
The delay between tapping and the page responding, usually caused by scripts occupying the main thread at the moment somebody tries to use the page.
- 04
And then it drifts back
This is the part a one-off audit cannot fix. A new gallery, a tracking pixel, an unoptimized upload — speed is lost gradually, which is why it is checked as part of the monthly care rather than once at launch.
Measured on this page, in your browser
This page, right now
- —
- —
- —
- —
These are read from your browser as you look at this, not typed in by us. Open devtools and check them — that is rather the point.