Changelog · updated continuously
Everything it changed, including the mistakes.
Each entry records the hypothesis before the change shipped, so the result can be judged against what was actually predicted. Reverts are published with the same prominence as wins, because a log that only contains successes is marketing.
- Entries
- 5
- Unattended
- 0
- Reverted
- 0
-
Added visitor tracking, and what it cost
Hypothesis · We cannot honestly claim to measure results without measuring visitors. Loading the tag only after the page is usable should give us the data without slowing anything down.
Code sent to the browser went from 2.2KB to 4.6KB. Google's own tag loads afterwards, once the page is already usable, so nothing waits on it.
-
Baseline captured before any change
Hypothesis · Publishing the starting numbers before doing any work removes the option of quietly picking a flattering start date later. If this experiment fails, it should fail where people can see it.
In the 90 days to 2 September 2026 this site was shown in Google 18,001 times and got 26 visits from it, sitting on average around page four. Taken from Google's own figures for the site, before a single change was made.
-
Rebuilt for speed, with a weight limit
Hypothesis · The old site loaded several hundred kilobytes of extra code from a page builder before it could show anything. Removing it entirely should put the site comfortably inside Google's speed standards permanently, rather than needing tuning.
-
Published the limits as a public table
Hypothesis · People hesitate to let anything automatic change their website because the limits are usually vague. Publishing exactly what is and is not allowed should settle more of that hesitation than any amount of reassurance.
-
Made the site easier for AI to read
Hypothesis · Describing the business consistently, and giving AI assistants a simple map of the useful pages, should improve the odds of being quoted on maintenance and website questions this site already gets shown for.
Machine-readable: RSS feed
Want this log for your own site?
Every plan produces one. It can be public like this, or private to your team.