Performance
Work concentrated on what a first-time visitor on a slow connection experiences, not on a score.
Performance work drifts toward whatever is easiest to measure, which is usually a score out of a hundred produced by a tool on a fast machine. The question we optimize against is different and less flattering: how long before someone arriving cold on a phone with two bars can read the thing they came for.
The largest element above the fold is identified deliberately and given loading priority. Where that element is an image it is marked as such so the browser fetches it early instead of discovering it only once the page's styling has resolved.
Fonts are self-hosted, not requested from a third-party service. Serving typefaces from somebody else's network adds a lookup, a negotiation, and a connection outside the site's control, all of them in the path before any text appears. Self-hosting removes the origin from the critical path and removes a third party from the privacy posture at the same time.
Content is visible on arrival. There is no scroll-triggered reveal on the sites we build, because a reveal that depends on an intersection observer has a failure mode where the trigger never fires and the entire page renders invisibly while looking perfectly healthy underneath. A background tab, a prerender, or a headless preview will all produce it. The cheapest way to satisfy the requirement that content must never be hidden by a stalled animation is to not animate its arrival.
The amount of third-party software is itself a performance decision. Sites here rest on very little of it, which keeps what a visitor downloads small without any optimization exercise, because code that was never added does not need to be removed later.
Images are served at the size they render, in modern formats, with dimensions declared so layout does not shift as they load. Layout shift is the defect users describe as the page jumping when they try to tap something.
Pages are prepared in advance and served as finished documents instead of assembled on every visit. A page whose content changes when the business changes it, rather than when someone visits, does not need a server doing work on arrival, and removing that work removes a whole category of slow response nobody has to diagnose later.
Third-party scripts are treated as a budget with a hard limit, not a list that grows. Each one is a request to an origin outside the site's control, executing arbitrary code with full access to the page, and the cumulative cost of a tag manager nobody has audited in two years is usually larger than every optimization made to the site itself.
What this does not cover.
- Optimizing for a synthetic score at the expense of what a visitor experiences.
- Client-side rendering frameworks layered onto a site that does not need them.
- Third-party tag managers loading arbitrary scripts we cannot audit.
Web & Digital
Content in version control
Why the words on a site live under version control instead of in a content management system, and what that trade actually costs.
Information architecture
The route table is written and agreed before anything is designed, because page counts later become assertions the build enforces.
Campaign and landing pages
Single-purpose pages wired to measurement that reports what actually happened, not what a model inferred.
Accessibility
Contrast computed, not estimated, focus visible on every control, and keyboard navigation tested by using it.
Structured data
One business entity emitted once across the site, referenced by identifier everywhere else.
Indexing and canonicals
Four independent layers decide whether a site is indexable, and they have to agree.