How This Site Is Built
We sell engineering. That makes this site part of the portfolio — the first work sample you interact with. Here is exactly how it’s put together, and the standard it’s held to.
The stack
Next.js App Router, statically generated — every page is prerendered HTML, no client-side rendering for content. TypeScript in strict mode. Tailwind CSS for the design system, Motion for the (deliberately few) animations. Deployed on Vercel; every push to main is a production deploy that has passed build, lint, and a verification gate.
The typography
Headlines are set in Instrument Serif — a single-weight editorial serif whose italic carries the accent phrases. Everything else is Geist Sans, with Geist Mono for labels and code. Both are subset and self-hosted; the serif costs about 32KB total. No icon libraries — every icon on this site is an inline SVG drawn for the place it sits.
The performance budget
The rule: the largest thing on any page is text, not a script or an image. No pre-consent third-party scripts, no WebGL, no scroll-jacking; decorative visuals are server-rendered SVG animated with CSS alone, and every animation honors your reduced-motion preference.
The measured numbers, on the record: on an unthrottled connection the largest paint — the headline text — lands in about a third of a second (344ms on the homepage, 218ms on a service page). Layout shift is effectively zero and total blocking time is 20ms. Under Lighthouse’s slow-4G mobile simulation the score is 90+, and the gap to a perfect score is our typography: roughly 70KB of self-hosted fonts. We consider that a good trade, and we’d rather tell you about it than quietly ship uglier pages.
Accessibility
WCAG 2.1 AA is the floor: every text color is verified to at least 4.5:1 contrast on every surface it appears on, every interactive element has a visible focus ring, touch targets meet minimum sizes, and the whole site works with motion turned off.
Privacy
Analytics are cookieless by default; anything that sets a cookie loads only after you accept it. The contact form writes to our CRM and nowhere else. The same privacy-by-default posture ships with every system we build.
What this means for your project
Every discipline on this page — documented decisions, measured budgets, security and accessibility as defaults, restraint over spectacle — is the same discipline your engagement gets. This page exists so that promise is checkable.
Curious what the same standard looks like on your problem?