DISCLAIMER AND LIMITS.

Nothing on this site is legal, financial, security or compliance advice. Where a decision carries real risk, get a qualified professional in your jurisdiction.

//The writing is experience, not instruction#

The journal describes approaches that worked on particular projects, with particular constraints, on particular hardware. Your stack, your traffic and your users are different. Treat any technique here as a starting hypothesis to measure in your own context, not a recommendation that generalises.

Web platform behaviour changes. Browser quirks get fixed, APIs get deprecated, framework advice ages badly. Anything written more than a year ago may be stale, and I do not systematically revisit old posts.

//Performance numbers are specific#

Figures in the case studies — frame times, Lighthouse scores, conversion changes — were measured on those projects, on defined devices, at a point in time. They are not benchmarks, not averages, and not a forecast of what your project will achieve. Anyone promising you a specific conversion lift before seeing your code is guessing.

//Code is provided as-is#

Snippets are stripped down for clarity, which means error handling, accessibility affordances and edge cases are often left out. They are not audited, not security-reviewed and not suitable for copying into production untouched. Review and test anything before it goes near real users.

//External links#

Links to other sites are for reference. I do not control them, I do not vet them on an ongoing basis, and a link is not an endorsement of everything that site says now or later.

//Availability#

Stated availability and response times are intentions, not commitments. Capacity changes, and an enquiry does not reserve a slot until there is something signed.