Speed is a feature your client will never ask for

The brief that never mentions it

I’ve read hundreds of project briefs. I can count on one hand the ones that asked for the site to be fast. Clients ask for beautiful, for on-brand, for a hero video, for a parallax effect that felt great in the pitch deck. Almost no one asks for speed, because speed is invisible when you have it. You only notice it by its absence, and by then it’s your problem.

And yet speed is the one feature every visitor feels on every visit, long after the launch buzz has faded and the hero video has stopped impressing anyone.

Slow is a tax nobody sees on the invoice

A heavy site doesn’t announce itself. It just quietly loses people. The visitor who bounces before the hero finishes loading. The search ranking that slips because the page is sluggish on a mid-range phone on mobile data, which is how most of the world actually browses. The conversion that never happens because a form took one beat too long and attention moved on. None of it shows up as a line item, but you pay it every single day.

• That autoplay hero video the client loved often costs more attention than it earns.
• Every unused script, every oversized image, every heavy font is weight that someone’s phone has to carry over a patchy connection.
• The fastest page isn’t the cleverest one. It’s the one that simply doesn’t load the things it doesn’t need.

Performance is invisible when you get it right, and unforgivable when you get it wrong.

Who feels it most

The cruel part is that the people a slow site punishes hardest are the ones you most want to keep. New visitors landing cold, with no reason to be patient yet, exactly the cold-landing audience I wrote about in the homepage isn’t the front door you think it is. People on older phones and slower networks, often the majority. Search engines, which now bake real-world loading behavior into how they rank you. You aren’t optimizing for a benchmark. You’re respecting the actual conditions your visitors live in.

The good news is that most of the fix is subtraction, not cleverness. Compress and right-size the images. Serve modern formats. Question the flashy effect that adds two seconds. Cut the third analytics script nobody reads. Measure on a real, mid-range phone rather than your fast laptop on office wifi. Google’s Core Web Vitals are a good, honest scorecard for whether you’re actually there. Choosing a lean, proven foundation helps too, which is part of why I argue for boring technology.

What this means for your build

Treat speed as a requirement even though no one wrote it down, because the person who will feel it is not in the meeting. Your client will never thank you for the milliseconds. But their customers will quietly reward the site that respects their time, and punish the one that does not, in bounces and abandoned carts you’ll never see explained. Fast is a feature. It’s just the one you have to care about on everyone’s behalf. It’s a good part of what I sweat over on the sites we build.