The front door works on a phone now ↗
The homepage looked like a serious tool on a laptop and felt heavy on a phone. Measured, not guessed. Mobile performance 68, a full second of blocked main thread, and six nav links a phone could not reach at all. The blocking was honest work in the wrong place. The hero demo hashed a real SHA-256 chain every two seconds from the moment the page loaded, below the fold, for nobody. Now it starts when you can see it, stops when you cannot, and checks only the record it adds. The real proof went on the front page too. Three numbers read live from the playground chain, the receipt count, the last anchor with its log entry, and the three witnesses, and the band shows nothing at all when the witness does not answer rather than a placeholder. One button instead of five. The copy went from 798 words to 655. After the release, mobile performance 94 and 96 on two runs, blocking time 150 and 80 ms from 1,030, zero console errors, 307 KiB from 498. One target still missed. The headline paints at 2.7 seconds on simulated 4G against a 2.5 target, and that cost is now the stylesheet and the font, which is the next lever. Two lessons for the ledger. A phone-width test that resizes after the page loads measures the desktop load, so set the viewport first. And a word count over the whole rendered page counted the nav twice and 93 words of screen-reader text from a diagram library, which is why the first number looked like nothing had been cut.