Process
How a build runs
Four stages, a fixed price agreed before anything starts, and a published checklist run against the finished site in front of you. Nothing here is a surprise at the end.
Baseline
We measure what you have now and write it down with the date: load speed, accessibility failures, what is indexed, what third parties your pages talk to. Everything afterwards is compared against this, so improvement is demonstrable rather than asserted.
You get A dated baseline document.
Scope in writing
A fixed page count, a fixed price and a named delivery date, agreed before any work starts. If the scope changes, the price changes visibly and by agreement — it does not drift.
You get A signed scope and price.
Build
Content structure first, then design, then motion. Every page is correct, readable and fully operable with JavaScript switched off before a single animation is added, so a failed script degrades to a finished page rather than a blank one.
You get A staging URL you can review as it goes.
Prove it
The checklist below is run against the finished site and the results are published with you watching. The baseline measurements are re-run. If a number did not move, you see that too.
You get A dated results report, and the site.
The checklist
28 checks, run against every build and published with the results. This list is the real one — if a check is added or removed, this page changes with it.
Performance
- Lighthouse run on the production build, not the dev server
- Largest Contentful Paint measured and recorded with its date
- Every image sized, modern-format, and served with a responsive srcset
- No layout shift: images and pinned sections reserve their space before they load
- Layout shift measured across repeated runs, because it is intermittent and a single clean pass proves nothing
- Scroll-driven sections hold their frame budget — dropped frames counted, not assumed
Accessibility
- Every text colour measured against the background actually painted behind it, at WCAG 2.2 AA
- Text over video or photography measured against the pixels genuinely behind it, in both directions — light ink on bright artwork fails in a way an average never shows
- Non-text contrast: borders, controls and focus indicators at 3:1, not just the type
- Full keyboard pass: everything reachable, visible focus, nothing trapped
- Screen-reader pass over headings, landmarks, links and form labels
- Reduced-motion honoured as absent motion, not faster motion
- Anything that moves on its own can be paused, and scroll-driven media only ever scrubs — it never starts playing by itself
- Page readable and operable at 200% zoom
- One h1 per page, no skipped heading levels
Responsive
- Six real device profiles, not one desktop width
- Both iPhone heights — with the URL bar showing and collapsed, because layouts break between the two
- No horizontal overflow at any tested width
Search and AI visibility
- Unique title, description and h1 on every page
- Structured data validated: every reference resolves, nothing malformed
- Sitemap and robots agree with each other and with the pages' own directives
- Every internal link resolves — no 404 reaches production
- Definition-first opening passage on every page, so an answer engine can quote it
Privacy
- Third-party requests counted, and justified one by one if any exist
- Cookies enumerated; if none are set, no consent banner is imposed on your visitors
- Privacy notice describes your actual practices, not a template's
Resilience
- The page renders complete with JavaScript disabled — animation is something the page gains, never something it depends on
- No placeholder, draft or unfinished text reaches a live page, including inside structured data where nobody looks
Start with a baseline
Send a brief and you will get a fixed scope, a real price, and a dated measurement of whatever you have now.
Grab a slot