There's a particular feeling, increasingly common, of opening a website and feeling vaguely lied to. The headline doesn't quite mean what it says. The button promises something it won't deliver. A modal interrupts you before you've read a sentence, asking for your email in exchange for nothing. Three weeks later your inbox is full of "exclusive offers." The site loaded slowly, looked beautiful, and somehow left you a little worse off than before.
This isn't a recent phenomenon, but it's accelerating. The web has been quietly optimised for extraction — clicks, conversions, retention, scroll depth — and along the way it's misplaced something it can't easily get back. Trust.
We've been building websites since 1999. Twenty-six years. In that time we've watched the medium grow up, mature, and slowly become something most of our clients are a little embarrassed to participate in. They want a website. They don't want to feel like they're that kind of business.
What an honest website looks like
An honest website tells you what it is in the first paragraph. It doesn't withhold pricing to harvest your contact details. It doesn't trigger a popup the moment your mouse approaches the close button. It doesn't claim to "respect your privacy" while loading 47 third-party trackers. It loads quickly because it doesn't carry weight it doesn't need.
It says, simply: here's what we do, here's what it costs, here's how to start, here's why people trust us. And then it gets out of the way.
The strongest signal a website can send is competence quietly demonstrated.
— Studio principle, internal doc · 2024
This isn't a stylistic preference. It's a commercial position. Every dark pattern we've ever measured on a client site has converted slightly higher in the short term and significantly lower in the long term. Lifetime value drops. Refund rates climb. Word-of-mouth — the cheapest channel that exists — quietly disappears.
Five signals we look for
When we audit a website — ours or anyone else's — we look for five things. Not as a checklist, exactly, but as a temperature reading.
1. Time-to-real-content
How long after the page loads can you read a sentence that actually tells you something? On many sites, the answer is "never" — the first viewport is hero illustrations, navigation, and a vague headline. On the best sites, the first sentence is doing real work.
2. Pricing visibility
"Contact us for pricing" is a tax on your prospect's time and a signal that you don't trust them with information. Some businesses genuinely can't price publicly. Most can, and choose not to, because hiding price feels like leverage. It isn't.
3. Page weight
The median web page in 2026 is over 4MB. Most of that is unused JavaScript, oversized images, and tracking. A focused brochure site can be done in 200KB. The difference is rarely visible to designers and almost always visible to customers — especially on mobile, especially on poor connections.
Hiding the price feels like leverage. It isn't.
4. Modal frequency
The popup asking for your email. The cookie banner. The chat widget waving. The "you forgot something in your cart!" overlay. Every one of these is, in isolation, defensible. Stacked together — and they almost always are — they communicate that the site doesn't quite want you, the visitor, in charge of your own visit.
5. The footer test
Read the footer. Is there a real address? A phone number? Names of real people? A footer is, weirdly, the most honest part of most websites — because nobody designs it for conversion. It's where the truth lives.
What we're trying to do, in practice
None of this is a moral position. It's a practical one. Honest websites convert as well or better than dishonest ones, hold up over time, and produce clients who refer their friends. We've measured it on enough projects to be quietly confident.
So when a new project starts, we ask a small set of questions before we sketch anything: What can we say plainly that competitors are saying vaguely? Where are we tempted to hide information, and why? What's the smallest version of this site that would actually do its job?
The answers aren't always comfortable, but the resulting websites tend to last longer, perform better, and need less constant tweaking than the alternative. Which is, in the end, the only argument we've ever found that holds up.
It's a quieter way to build for the web. It's also, we think, a better one.