Render galleries that exceed 4MB unoptimised
Render and drawing galleries where a single hero image often exceeds 4MB before optimisation, which is the main reason architecture sites fail Core Web Vitals.
Everything below is ours and on our servers. Nothing follows you to another site.
Who
How we work
Rebuild
ARCHITECTURE · WEBSITE DEVELOPMENT
The work is the portfolio, and the portfolio is what makes the site unusable on a phone. A gallery built for a desktop review meeting is not a gallery a client opens on a phone in a taxi, and most architecture sites never test for the second case.
WHAT ACTUALLY BREAKS
Render and drawing galleries where a single hero image often exceeds 4MB before optimisation, which is the main reason architecture sites fail Core Web Vitals.
So a project page opens in under a second and the full-resolution render arrives after, instead of a white screen while 12MB downloads.
Project case structure that carries client, scale in square metres, completion year and discipline as filterable data rather than as text in a paragraph.
Without loading the third-party player until the visitor asks for it.
For firms that want to know who is taking their documents.
WHAT WE BUILD
A render uploaded once for the portfolio is the same render the project archive indexes and the same render a practice profile links to. Four components that share one data model, not four separate tools stitched together after the fact.
PROOF
Not a portfolio piece. A consultancy we co-founded and still run through the same studio.
An engineering and architectural consultancy we co-founded, delivering through the same studio process as this build.
Running through Varmont right now, in the same Virtual Studio every client project uses.
The consultancy we co-founded, not a client reference.
WHAT IT COSTS
Depending on gallery size and archive complexity.
From brief to launch.
Code, server and data, from handover.
STRAIGHT ANSWERS
Images load progressively. A project page opens in under a second with a compressed preview, and the full-resolution render loads in behind it, instead of a visitor staring at a white screen while a 4MB hero image downloads. This is the specific fix for the failure that costs most architecture sites their Core Web Vitals score.
Yes. Each project carries client, scale in square metres, completion year and discipline as structured data, not as text buried in a paragraph. A visitor can filter the archive by discipline or size directly, and the same structure is what lets search engines understand and surface individual projects rather than one long portfolio page.
Yes. Drawing and specification files sit behind a short form, so a download is tied to a name and an email address rather than an anonymous link anyone can share. You see who requested the document, which matters when what you are sharing is unbuilt work.
Two days, no charge, and you keep the report.
Architecture sits alongside engineering consultancy and interior design, two industries we build for on the same premise: technical credibility has to survive a fast look on a phone.
One tap, then your app opens with it written.