Home
/Performance
Accessibility
Best practices
SEO
- Largest paint
- –
- Layout shift
- –
- Blocking time
- –
- Download
- –
Performance over recent releases
// under the hood
The numbers behind this site
We say we build software properly. This page is the proof for the site you're on. Every release is built, checked and measured by the same pipeline, and these are its figures for the release that's live right now, not a screenshot from a good day.
// lighthouse
Measured on the live site
Google's Lighthouse, run on its phone setting against the public site after each release ships: three runs per page, middle result kept. That is the setting most sites score worst on.
Voicebots
/voicebots/Performance
Accessibility
Best practices
SEO
- Largest paint
- –
- Layout shift
- –
- Blocking time
- –
- Download
- –
Performance over recent releases
Blog
/blog/Performance
Accessibility
Best practices
SEO
- Largest paint
- –
- Layout shift
- –
- Blocking time
- –
- Download
- –
Performance over recent releases
About
/about-us/Performance
Accessibility
Best practices
SEO
- Largest paint
- –
- Layout shift
- –
- Blocking time
- –
- Download
- –
Performance over recent releases
// the build
What ships
Counted from the finished build itself, the same files the server sends. Pages are plain HTML with their styles inlined, so a visit is one request before anything renders.
- Pages
- –
- every one a real HTML file
- Blog posts
- –
- written in MDX
- Pages in search
- –
- indexed at build time
- Home page HTML
- –
- compressed
- Typical page HTML
- –
- compressed, median
- Script files
- –
- both for the voice demo, the larger only once you press call
- Image files
- –
- each photo cut to the sizes screens need
- Font files
- –
- self-hosted, no font service
// every release
What a change goes through
From the moment a change is pushed to the moment it's live, every step runs on its own. If one fails, everything after it stops, and nobody has to remember to look. The one step a person takes is deciding to release.
01
Every push
- Posts checked: frontmatter, heading structure, spacing, terminology
- Type-checked across the whole project
- Built, with the search index made from public pages only
- Every link resolves, and every post links to and from another
02
Staging
- Shipped to a private copy of the site and checked there first
03
Releaseby a person
- Started by a person, for one exact commit already on the main branch
- Every check above, run again on that commit
- The upload refuses to start unless it’s pointed at the live site’s own folder
04
Verify
- Every built file fetched back from the live site, every page compared byte for byte
- The contact form and the voice demo’s call endpoint answer exactly as they should
- All five security headers are present
05
Measure
- Lighthouse on the live site, the numbers on this page. Doesn’t block a release
06
Assistant
- The chat assistant’s knowledge base resynced, and it must pass its tests before going live
- Builds passed
- –
- of the last 30 pushes
- Push to staging
- –
- median, every check included
- Production releases
- –
- since November 2026
- Releases measured
- –
- the history the trend lines show
// security headers
What every page tells the browser
Five instructions sent with every page, read from the live site when it was last measured. A release that lost any of them would have failed its checks.
strict-transport-securitynot measuredBrowsers only ever connect over HTTPS
x-content-type-optionsnot measuredFiles are only used as the type they declare
x-frame-optionsnot measuredOther sites can’t embed these pages in a frame
referrer-policynot measuredOther sites see where a visitor came from, never the full address
permissions-policynot measuredCamera, location and payments are switched off; the microphone works only for the voice demo
Want your tools built this way?
The same habits go into the agents and software we build for contractors: tested on every change, measured in production, and fixed by the people who built them.