The Passive Voice Tax on Comprehension

Consider two sentences that mean the same thing. “We deleted your data.” “Your data has been deleted.” A reader understands both. But they don’t understand them at the same cost, and the difference in cost is what I want to talk about, because on a website those small differences get charged on every sentence, to every visitor, forever.

The grammar itself is simple. In an active sentence, the doer comes first: someone does something. In a passive sentence, the thing done-to comes first, and the doer moves to the end or disappears entirely. “The form was submitted.” Submitted by whom? The sentence doesn’t say, and grammatically it doesn’t have to. That’s the whole trick of the passive: it makes the actor optional.

Why does this cost the reader anything? Because the human default for understanding events is actor, action, result, in that order. That’s how we narrate the world to ourselves. When a sentence delivers its pieces in that order, comprehension feels instant; the words pour into slots that are already waiting. When a sentence arrives backwards, result first, actor last or missing, the reader has to hold the result in suspense, wait for the action, and then either find the actor or invent one. It’s a tiny reversal, done in a fraction of a second. Nobody consciously notices it. But it’s work, and it’s work the writer offloaded onto the reader. I think of it as a tax: small per transaction, invisible on any single sentence, ruinous in aggregate.

The aggregate is what matters on the web, because of who your reader is. They’re on a phone. They’re giving you partial attention. They’re skimming at a pace that leaves no slack for re-reading. Print readers in an armchair can absorb a passive-heavy paragraph; they have attention to spare. Your visitor doesn’t. Every unit of effort your sentences demand is subtracted from a budget that’s nearly empty, and when the budget hits zero, they don’t struggle on. They leave. The passive voice tax doesn’t get paid in complaints. It gets paid in the silent departures your analytics record as a bounce.

But comprehension speed is only half the problem, and maybe the smaller half. The more interesting cost is what the passive does to trust. Because the passive makes the actor optional, it is the natural grammar of dodged responsibility. “Mistakes were made” is the canonical example for a reason. Nobody made them; they simply occurred, like weather. Now look at where websites reach for the passive most: exactly the places where responsibility is in question. “Your payment could not be processed.” “Your account has been suspended.” “An error was encountered.” Each one describes something an actor did, ours or yours, while carefully declining to say which. And that missing information isn’t stylistic garnish. It’s the very thing the reader needs next. Could not be processed by whom, for what reason, and who should act now? “We couldn’t charge your card. Please check the number and try again” is active, and notice that going active forced the sentence to become useful. The passive version wasn’t just slower. It was hiding the fact that it had nothing to say.

That’s the general pattern I’ve come to believe: passive voice doesn’t merely obscure agency, it lets vagueness survive that active phrasing would kill. To write the active sentence you must know who does what. Sometimes writers reach for the passive precisely because they don’t know, or don’t want to say. The grammar isn’t the disease. It’s the symptom that lets you find the disease. When I review text on the sites GazeSite audits, passive clusters are where I look first, because that’s where the writer stopped being sure of the facts.

I should be fair to the passive, because it has honest uses, and advice that says “never” is advice people rightly ignore. The passive is correct when the actor is genuinely unknown or genuinely irrelevant, and the acted-upon thing is the real topic. “This site was built in 2019” is fine; nobody needs the contractor’s name. It’s also correct when you’re keeping a consistent subject across sentences: if a paragraph is about your data, then “your data is encrypted, backed up nightly, and never sold” keeps the spotlight where it belongs, even though the middle of that is passive. The test isn’t grammatical, it’s informational: does the sentence still deliver everything the reader needs? A passive that omits nothing important is harmless. A passive that omits the one thing the reader came for is the tax at its steepest.

The practical method, if you want one, doesn’t require parsing grammar. Read your page and, at each sentence, ask one question: who is doing this? If the sentence answers instantly, move on, whatever its voice. If you have to think, or the answer is “well, the system, sort of, or maybe the user,” you’ve found a sentence that’s billing your reader for work you skipped. Do the work. Name the actor. You’ll find, as I keep finding, that the sentence doesn’t just get faster. It gets truer, because it finally says who’s responsible. And on a website, where every sentence is a small promise from you to a stranger, saying who’s responsible is most of what trust is made of.