A Studio Site That Scores Itself While You Read ItA Studio Site That Scores Itself While You Read It

The brief

nileBlu sells websites to research groups and early-stage startups, and most of the people who reach a studio site have been sold a website before. By the time they arrive they have read that somebody is fast, custom and easy to work with roughly forty times, and they have stopped reading it.

What existed was a practice and no site to point at. So the site was built against a single constraint: it may not make a claim it cannot let the reader check on the page making it.

What it had to do

The claims a studio makes about itself are the hardest ones to evidence. Speed, ownership and “you can edit it afterwards” are all invisible from outside — a fast site and a slow one arrive the same way, as a page that is simply there.

There was a second and worse failure available. A site that sells a build practice and then breaks it — a hardcoded colour, a stock photograph, four analytics scripts loading ahead of the headline — is evidence against the studio that shipped it. Nobody audits a studio site, but the smell of one carries.

How it's built

Three rules, held by the codebase rather than by discipline. No value is written into a component: every colour, size, radius and breakpoint resolves from one token layer, so the site can be re-themed from three files and no component can quietly invent its own shade of grey.

No copy is written into a component either. Every sentence here, this one included, lives in a content file a non-engineer can open and edit — which is the same handover a client gets, tested on ourselves first.

And no photography. Ten drawn motifs replace the stock library, each depicting the system the work actually changed, which a photograph of a laptop on a desk cannot do.

Then the part that does the arguing. The home page measures its own Core Web Vitals in the visitor's browser and prints the four numbers as they arrive. It is the only speed claim on the site, and it is not a claim.

What went live

Twenty-six pages, every one prerendered at build, so the first byte of any page is a finished document rather than the start of a render. Six runtime dependencies. No third-party script runs anywhere on the site — the one inline script in the document is ours and fetches nothing — and the contact form posts to a server action, so a visitor's browser never talks to a form vendor.

The parts that are not finished are marked as unfinished rather than dressed up. Seven invented project write-ups used to sit underneath this one; they are gone, and this page carries the gap instead of filling it. That is the same standard applied in the other direction.