Website Builds
We build websites two ways. Hand coded when the site has to do something a page builder cannot, and Webflow when the client needs to run it themselves afterwards. That call gets made per project, before any design work starts, and we tell the client which one they are getting and why.
Four are live: a design build contractor, an exotic car rental brand, a hair studio and this site.
- ELG Services: hand coded, 28 pages, structured data on the homepage and 17 subpages
- Auto Plug Network: a scroll driven film of 971 frames, and a 30 vehicle fleet the owner updates from a single file
- Siij Hair: an editorial brand site built around booking
- ToAi Media: this site, a Webflow build carrying a cinematic control room entry
- 95 Performance, 100 Accessibility and 100 Best practices on toai.ca, desktop
- Self hosted typefaces on the hand coded builds, so they make no third party font request
- A baseline audit published with every launch, including our own
Two of these launched inside the last month, so their traffic numbers do not exist yet and we are not going to invent them. What we can put in writing today is the build standard.
On toai.ca, the site you are reading right now, Google PageSpeed Insights returns 95 Performance, 100 Accessibility and 100 Best practices on desktop. That is measured on a page carrying a full screen cinematic entry, which is the part most builders would tell you to cut. We publish a baseline audit with every launch and we publish our own.
The work that separates these from a template is usually invisible in a screenshot.
On Auto Plug, the hard part was making 971 frames of film move smoothly on a phone. The first version held every frame in memory as an image. A phone cannot do that, so the browser quietly discarded frames and had to decode them again mid scroll, which is what a stutter actually is. We rebuilt the engine to decode frames into a window that follows your thumb, keep only what is near, and release the rest under a memory budget.
On this site, the control room had to appear instantly without the page behind it stealing the largest paint. That meant hiding everything under the overlay from the first frame, inlining a subset of the typefaces, and pinning the video stream to one resolution so it never degrades when the loop wraps.
On ELG, 28 pages needed structured data, a frame by frame scroll hero, and a form that only reports a lead when a lead actually happened.
Different problems, one standard. Start here if you want one built.
