platform support01
The compound return of Core Web Vitals
Small technical choices that keep earning after the launch meeting.
/ 3 min
The journal
Useful ideas for
the next chapter.
Core Web Vitals, accessibility, security and the compounding value of work nobody notices.
About this topic
Why we keep
writing about it.
2 articles · Platform & support
Value decays quietly. Dependencies age, performance drifts a hundred milliseconds at a time, accessibility regressions creep back in with each release, and nobody notices until a metric moves or a letter arrives.
These pieces are about the work that stops that happening: Core Web Vitals treated as an engineering budget rather than a score, accessibility built in instead of retrofitted, security hygiene that assumes a bad week will eventually come, and the maintenance rhythm that keeps a good build good.
Browse by topic
Five things we
write about.
Each topic collects the arguments we find ourselves repeating in first meetings, written down properly so you can read them instead.
Web development
3 piecesBriefs, structure, platform choices and why accurate websites so often fail to persuade anyone.
App development
1 pieceRetention, states, release engineering and the decisions that separate an app people keep from one they delete.
E-commerce
2 piecesPlatform decisions, replatforming risk, checkout friction and where merchandising velocity actually comes from.
Platform & support
2 piecesCore Web Vitals, accessibility, security and the compounding value of work nobody notices.
Agency practice
2 piecesHow we work, what we refuse, and the arguments we would rather have in week two than week ten.
Editorial policy
Why there is no
posting schedule.
We publish when we have learned something worth another team’s ten minutes, which works out at roughly one piece a month. There is no content calendar, no keyword-led brief and no ghostwriter, because articles written to fill a slot read exactly like articles written to fill a slot.
Everything here is written by the people doing the work, and every recommendation has been tested on a real engagement — including the ones where we got it wrong first. Where a claim is contested, we say so rather than presenting a preference as a finding.
Nothing is gated. If a guide is useful, it should be useful before you speak to us.
A better brief starts here
Ready to make the next move obvious?
Bring us the hard thing. We will bring a point of view, a senior team and a clear next step.