Digital transformation baseline
We have done this, on ourselves
The proposition a consultancy makes is usually a claim. JSHW guides digital transformation and digital presence optimisation — an ordinary thing for a firm in this category to say. What's less ordinary is what happened when that got applied to the one property this company controls completely and has no excuse to get wrong: its own website.
The site was audited properly, every finding logged with an ID, fixed in a defined order — and now that work is published, not just the result. Each article follows one rule without exception: nothing goes live before its corresponding fix has actually shipped. An article about a gap that's still open isn't thought leadership; it's an excuse.
The articles
-
Article 1
The JSHW Rebuild
A consultancy that sells digital transformation had a website built by a page builder — 1.5 MB of mostly dead code, a dead primary call-to-action, and a leaked hosting hostname in the logo's alt text. This is what replacing it measured, re-verified against the actual production build rather than repeated from an earlier snapshot.
-
Article 2
The Sheet Is the Database
A consultation request now reaches a Google Sheet through a plain server-side form post, not client-side JavaScript holding a write endpoint in page source. That change was correct in design — and it still shipped with a real gap for one day, found and closed the same day it was found.
-
Article 3
The Neighbours' Reputation
Nobody visiting a site can see a DNS record, a shared server's sending history, or a machine-readable identity claim in a script tag. All three decide, before a human ever forms an opinion, whether the site or its mail gets treated as legitimate at all. Both are now resolved for the production domain — done early, and done deliberately, not as a last-minute scramble.
-
Article 4
What Our Own Audit Tooling Found
A single Lighthouse score is a snapshot, not a fact. Building a second, independent way to check our own work — rather than trusting one tool's number — surfaced a page nobody meant to leave live, still branded under our own name, and a hard lesson about how much one score can move for reasons that have nothing to do with the site.
-
Article 5
Your Alt Text Is Your Hosting Provider's Name
A screen reader announces a logo by its alt text. On the old site, a visitor using one wouldn't have heard this company's name at all — they'd have heard the hosting provider's own auto-generated server address, word for word. It was reported fixed once. It wasn't. Here's what actually closed it.
-
Article 6
The Button That Goes Nowhere
A website's primary call to action has one job — convert a visitor's interest into contact. On the old site, that button — and six others behind it — pointed at a placeholder anchor the page builder leaves behind by default. Not a broken link. A link to nowhere, sitting in the one spot on the page every visitor is invited to click.
-
Article 7
Three Menus, One Navigation
Responsive design usually means one navigation that looks different at different sizes. The old site built three separate navigations instead — one per breakpoint — and left all three sitting in the page at once, visible to nothing but a screen reader, which read every single one.
-
Article 8
Bright Future Way, New World
“Bright Future Way, New World” is not a real place. It's the kind of placeholder a page-builder template ships with, meant to be replaced before anything goes live — and on the old site, it never was. It sat in the footer and the legal notice of a real, trading business for as long as the site was live.
-
Article 9
60% of Your Website Is Code Nobody Wrote on Purpose
The working title undersold it. Measured across all five templates, matched instrument on both hosts, roughly 70% of every page on the old site was code that page loaded, parsed, and never used — not once, on any visit. The rebuild's figure, on all five templates, both mobile and desktop, ten separate measurements — exactly zero. This is what that gap actually costs, and why closing it is a sustainability question as much as a technical one.
-
Article 10
One Site, Three Addresses
The slate for this piece was written before the site had even moved to its current domain, when the finding was one set of duplicate builder pages on an old .xyz family. That finding no longer applies — the project doesn't run that infrastructure any more. What replaced it is a plainer, more current question — how many addresses answer for this brand right now, and does each one do the right thing? Checked one by one, the count was five, not three, and four of them needed fixing.
-
Article 11
Trusted by Nobody
A testimonial with no name attached and a logo that never loads are the same failure wearing two outfits — something claiming to be evidence of trust that nobody can actually check. Both were found on the site this project inherited, logged the same day, and cut rather than rewritten to look better. What eventually filled the gap wasn't a nicer version of the same trick. It was a page of real names, doing real work, each one a link a reader can click today.
-
Article 12
What Lighthouse Does Not Tell You
Every article in this series has said the same careful thing about its own accessibility score — that 100 out of 100 is a floor, not a certificate. This is the piece that finally pays for that sentence. Nineteen manual sessions on macOS across three browsers and six templates, VoiceOver throughout, plus a real-device pass on an iPhone and an Android handset. The automated number did not move, because it was already zero and stayed zero. A person found three things anyway, and none of the three are things a tool has a rule for.
This is the first instalment of a longer slate, not the whole thing. The remaining findings are real, already logged, and each is waiting on its own fix landing before it's written up — not withheld for effect, just not ready to publish honestly yet.