Building for the Slow Connection
Performance is not a technical concern hiding in the basement of a project. It's a design decision, an ethical one, and the truest measure of whether you respect the people on the other end.
There is a version of the web that exists only on the machines of the people who build it: fast laptop, fast connection, the assets already warm in the cache, the device new enough that nothing ever stutters. It is a beautiful web, responsive and instant, and it is a lie. The real web is being read on a three-year-old phone, on a train, on a connection that drops to a crawl between tunnels, by someone who has thirty seconds and is already a little impatient. If your site only works on the first web, you did not build a website. You built a demo.
Performance is a design decision wearing an engineer’s coat
We have agreed, as an industry, to file performance under engineering, which means it shows up late, gets measured against a budget that is already spent, and loses every fight with a marketing requirement. This is backwards. Every heavy decision is made early, in the design, long before an engineer can do anything about it. The hero video, the eight custom fonts, the carousel of full-resolution photographs, the analytics scripts that arrive in a convoy — these are not implementation details. They are the design, and the design decided the page would be slow before a single line of it was written.
Which means performance is a thing you design, not a thing you optimise. The optimisation at the end is real and worth doing, but it is rearranging furniture in a house with the wrong foundation. The fast site was decided in the wireframe, when someone chose to say one thing clearly instead of five things at once.
The cost is paid by someone who isn’t in the room
Here is the part that makes it an ethical question and not just a craft one. The cost of a heavy page is never paid by the team that shipped it. It is paid by a stranger, on a worse device, on a worse connection, often in a place where data is metered and expensive. A three-megabyte page is, to that person, a small toll — battery, time, actual money — collected so that someone else could avoid the work of restraint.
When you frame it that way, a lot of decisions get easier. The autoplaying background video stops being a nice-to-have and starts being a thing you are charging strangers for. The font you could not quite bring yourself to cut becomes a hundred kilobytes you are asking a stranger to download to read a sentence they could have read in the system font. Restraint stops feeling like a limitation and starts feeling like manners.
Fast is a feeling, and the feeling is respect
The thing about a fast site is that users do not experience it as “fast.” They experience it as working. The tap that responds instantly, the page that is simply there, the interaction that does not make them wait — none of it registers as performance. It registers as competence, as care, as the quiet sense that the people who made this thing thought about you.
That is the whole reward, and it is enough. You will never get a thank-you for the video you did not autoplay, the fonts you subset, the script you deferred. The reader will never know about the work you did to make their thirty seconds feel like enough time. They will only know that they got what they came for and left a little less annoyed than usual — which, on the web, is close to the highest praise there is.