Skip to content
← Journal

Journal · Journal

The web got loud because loud worked on people

Countdown timers, popups and interstitials were all built for one reader: a distracted person with a scroll wheel. That reader now arrives second. What the machine needs from a page turns out to be what a person needed all along.

Yvonne Boustany6 min read

The web got loud on purpose.

The countdown timer. The popup that catches you on the way out. The chat bubble pulsing in the corner. The bar that slides up over the paragraph you were in the middle of reading. None of it is an accident, and none of it is bad taste. Every one of those was tested against a version of the page without it, and every one of them won.

That is worth sitting with before deciding how you feel about it. Loud won its arguments. It is still winning some of them.

What all of it was built for

Every one of those devices was designed for the same reader: a distracted person with a scroll wheel and an impulse.

Interrupt them before they go. Manufacture a reason to act today. Make the exit a little harder to find than the button. It is a coherent philosophy, and aimed at that reader it works.

Then the first reader changed

Increasingly, the first thing that reads your website is not a person. It is a model, reading on their behalf, which then tells them what is there.

Someone asks an assistant who does this near me, or what is the best option for X, or is this place any good. The answer comes back with names in it. Yours is in that answer or it is not, and the person may never open your page at all.

None of the loud repertoire works on that reader.

A model does not feel urgency. It cannot be interrupted into buying. It has no fear of missing out, and it will never see an exit-intent popup because it never intended to leave. Fifteen years of technique, aimed at a reader who now arrives second, if at all.

Where the two readers want the same thing

Here is the part that surprised me, and it is the actual argument.

What a machine needs in order to understand a page is, almost item for item, what makes a page restful for a person.

A real heading structure. A parser needs to know what the page is about and how it is organised. A tired person needs to find the part they came for. Same requirement.

One clear next action. A model extracts one answer. A person given one obvious door does not have to choose. Six competing buttons confuse both.

Nothing that interrupts. Modals and interstitials can sit between a crawler and the content. They also put a person on guard. Both readers get less of what they came for.

Plain declarative sentences. These are what an assistant lifts and quotes. They are also what someone can absorb at the end of a long day.

Light, fast pages. Quicker to crawl, quicker to paint, less waiting either way.

No manufactured urgency. It moves a machine not at all, and it moves fewer people every year, most of whom have watched the same timer reset.

I do not think the overlap is a coincidence. Both readers are doing the same thing: working out what this is and whether it is for them. Everything built to stop someone leaving gets in the way of that.

If you are reading this and recognising your own site in it, so does nearly every site. This is the ordinary condition of a website that was built well five years ago by people who were right at the time. Nothing has broken. Nothing needs deciding today. It is worth knowing, and it will keep.

When loud is still right

Calm is not always the answer, and any argument that says otherwise is selling something.

We built a site for a dance and fitness studio in Houston that is deliberately loud. A countdown, a forty-nine dollar offer, an email-to-win. That was the correct build. Someone deciding whether to walk into a first class is not conducting research. They need a push and a reason to go this week, and the site's job is to hand them one.

So the claim is narrower than quiet always wins, and more useful:

Calm is the correct default now. Loud is a deliberate exception, and you should be able to say why you are making it.

Most loud sites cannot say why. They are loud because loud was the house style of an era, not because anyone matched the register to the person arriving.

Where I got this

My father teaches yoga in Houston. He studied physics at Rice, and he brought the physics with him. When he explains a pose he explains the load path, the leverage, the reason a joint wants what it wants.

I grew up watching people let go of something the moment the explanation arrived. The physics is what keeps it from being mysticism. It is also what makes it calming: you stop bracing once you understand why.

I think this is the same thing moved to a different subject. Calm on a website is not a mood applied at the end. It is what a page feels like when someone has done the structural work and left nothing extra on it.

What we will not build

No countdown on anything that is not actually ending.

No popup over the thing you came to read.

No interstitial between a question and its answer.

No chat window pretending a person is typing.

No scarcity we cannot demonstrate.

One door per page.

Motion that respects a reduced-motion setting.

The list is short on purpose, and every line of it is checkable. You can hold a page against it and see.

The short version

The web got loud because loud worked on people. It is quieting down because the next reader cannot hear it — and it turns out the people could not stand it much either.

Occasional email. Cancel anytime.

Related Reading