A Seattle website redesign, judged in milliseconds rather than mood boards

Three hours up I-5, one timezone, no office

Seattle is the nearest US market to our studio — about 230 km, I-5 most of the way, border queue permitting. Same Pacific clock, so a 9am stand-up is 9am for both of us. Same blunt commercial culture too: quietly impatient with a pitch carrying no numbers.

What we do not have is a Seattle address, phone number or Google listing — inventing one is both a lie and a Google violation. Everything is delivered remotely; when a workshop needs a room, somebody drives.

What the Seattle numbers cost, next to everywhere else

Live Google figures; the last column is keyword difficulty.

Google reports that 1,000 across several near-identical phrases at once, so it is the whole design-buying cluster here, not a thousand people shopping for a rebuild. Difficulty 77 is a score, not a reading of page one — read it as "expect entrenched incumbents". Row four is the one worth noting: $46.45 a click on a fifth of the traffic, a phrase attracting buyers rather than browsers.

And for its size, Seattle is cheap:

Same volume as Los Angeles at half the click price, and cheaper than Calgary on a far larger market.

Where a redesign quietly loses its speed

Rarely in the design. It goes into what gets attached to it — a hero video, a typeface at six weights, a chat widget, a heatmap and an unaudited tag container.

The trap is the reporting. Search Console's Core Web Vitals are field data on a rolling 28-day window: a launch that regressed on day one reads healthy for a fortnight, then turns red three weeks later, when nobody connects the chart to the cause. So we measure on staging against the outgoing site, then watch that window through a full cycle before calling the work done.

Accessibility priced as risk, not ticked as a box

WCAG 2.1 AA is the standard everyone cites, and US federal courts have applied ADA Title III to websites for years. We are not lawyers. The commercial point is timing: retrofitting focus states, contrast and semantic structure into a finished build costs several times what including them costs from the start.

Sell to Washington state agencies, King County or the universities and procurement will ask for a conformance report — an automated scan will not survive the follow-up. Scanners catch a minority of real barriers; the rest is keyboard navigation and reading order, checked by a person.

None of it is charity work. Visible focus rings, real labels and 4.5:1 contrast are also what let someone finish your form one-handed on a bus — accessibility and conversion are the same fix.

Live builds you can open and inspect

Running sites, not screenshots — open DevTools on them. Canadian clients, not Seattle ones.

Straight answers, Seattle specific