Performance & SEO Engineering

Structured data describes the business, not just the page

This site ships a JSON-LD graph describing the person, the website, the service offering, the portfolio items, and a FAQ block — all typed as real schema.org entities, not a flat meta-description. Search engines (and increasingly, AI answer engines) can parse that graph directly instead of inferring it from prose, which is a meaningfully different bar to clear than 'has a title tag'.

This journal you're reading is itself part of that strategy: each entry is a real, indexable page about one specific technology, linked from a real navigation path — topical depth a single all-purpose homepage can't provide on its own.

Performance budgets around the fun parts

A WebGL-heavy homepage is exactly the kind of page that can quietly fail a Core Web Vitals audit if nobody's watching — a render loop that never yields, a synchronous asset load blocking first paint. Building with that constraint in mind from the start (async asset loading with a visible fallback, effects that degrade gracefully rather than freeze under load) is what keeps the 'impressive to look at' version of a site from being the 'ranks lower because it's slow' version too.