Matthew Sim

Architectural exploration and reference build of an executive consulting showcase: edge-native Astro v6 delivery, sub-second mobile LCP, zero client JavaScript, and unified technical stance publishing.

view the live build

client: Matthew Sim
service: Executive Portfolio & Stance Platform
sector: Executive Advisory / Fractional CTO
year: 2026

the brief

An engineering executive's personal platform is their primary proof of technical judgment. Before any portfolio document, any reference call, or any consulting proposal, a prospective client opens the URL and forms a verdict in the first three seconds: how fast does it render, how clean is the code underneath, and does the infrastructure reflect the discipline they are being hired to install in their own organisation? Matthew Sim's platform had to make that verdict pass on the first load.

built with

Astro · Cloudflare Workers · Tailwind CSS · TypeScript

what changed

Sub-second mobile delivery and zero runtime JavaScript establish immediate technical credibility

The platform scores 100/100 on Lighthouse mobile performance while shipping exactly 0 KB of runtime JavaScript. Every page is pre-rendered at build time and served from Cloudflare's edge cache, so the entire executive positioning renders in 0.45 seconds on throttled mobile 4G.

Global Time to First Byte holds at roughly 40ms across Cloudflare edge POPs, because the request never touches an origin server during normal traffic. For an audience that audits technology vendors for a living, those numbers are the strongest first-page reference letter available.

inside the build

the proof of craft

A fractional CTO’s website is a technical artifact that gets reviewed the way a pull request gets reviewed. Enterprise buyers who engage an engineering executive for org buildout or platform strategy already know how to read a stack. They check the page source. They watch the network waterfall. They note whether the hero image is optimised or a six-megabyte JPEG served from a shared host.

The platform is built to survive that inspection. Every layer, from the build pipeline to the delivery edge, is chosen for the same reason the client would choose it in a client engagement: correctness first, then simplicity, then cost.

zero runtime javascript for editorial authority

The site carries no client-side framework, no hydration layer, and no JavaScript runtime of any kind. The capability pillars, the long-form technical writing, and the advisory intake flow are all static HTML and CSS compiled at build time.

This is the same stance the client advocates to engineering leadership teams: interactivity only where it earns its bandwidth, and never in the critical rendering path. When a prospect reads a paragraph on eliminating framework bloat and the page delivering it ships zero runtime JS, the argument lands before it finishes.

edge-cached delivery across global pops

Pages are compiled once and distributed to Cloudflare’s global edge network. A board member in Tallinn, a procurement lead in London, and a founder on a train all hit the nearest POP and receive identical bytes in roughly 40ms, with the origin server effectively out of the request path.

Because nothing is generated per request, traffic surges are invisible: a viral technical article or a conference announcement changes nothing about latency or infrastructure spend. The delivery model scales flat.

a content model for publishing

The executive publishes long-form analysis through Astro’s content collections. Typed frontmatter keeps the editorial index, reading views, and search index in sync on each build.

the numbers

Metric	Legacy Executive CMS	Edge Architecture
Mobile LCP (throttled 4G)	4.2s	0.45s
Initial client JavaScript	480 KB	0 KB
Lighthouse mobile score	48 / 100	100 / 100
Global TTFB	380ms	28ms

in the details

02 views

Matthew Sim long-form engineering writing and editorial insights index

Matthew Sim strategic advisory consultation intake and contact section

the result

With every runtime framework eliminated from the critical path, prospective enterprise clients get an instant reading experience: the full positioning, capability pillars, and engagement model render in under half a second on a throttled mobile connection, with nothing to hydrate, nothing to bundle, and nothing to debug after launch.

The same elimination removes the maintenance overhead that quietly consumes executive time. There is no framework version churn, no dependency audit cadence, and no build pipeline to babysit. Content publishes through a static build and the edge cache does the rest, leaving the executive's calendar entirely free for the advisory work that pays for it.

credits

Two Shells

Systems Engineering

building something similar?

talk to 2sh