Behind the Scenes
A portfolio that practices what it preaches — every claim this site makes about DevOps and performance is applied to the site itself.
This site is more than a list of skills — it is the proof. The performance numbers, rendering strategy, and monitoring practices described on this page are the same ones I apply to client work, applied first to my own portfolio.
React Server Components, static prerendering, and route-level metadata for SEO.
Full bilingual routing — every page exists in English and Indonesian with proper hreflang alternates.
Utility-first styling on top of CSS variables for the dark theme and orange accent.
Scroll-triggered reveals and page transitions, kept lightweight and once-only.
Edge CDN delivery of prerendered pages, with analytics for real-user data.
Almost every request stops at the CDN. The origin is only involved when the site is built — not when you visit it.
Everything is statically prerendered at build time — no per-request server rendering.
The client i18n payload is stripped down to 76 KB instead of shipping every blog post's text on every page.
Blog content is re-injected per page — each post only carries its own content.
ISR is used only where data is live; static stays static.
106 kB of shared first-load JavaScript — and it is guarded, not just measured.
The animated footer is hand-written WebGL (~4 kB) instead of pulling in three.js.
Images are compressed with sharp before they ever reach the repository.
Static assets ship with immutable cache headers so repeat visits skip the network.
This architecture is not theoretical — it exists because this site once blew through its Vercel bandwidth quota. Fixing that meant profiling, static rendering, payload stripping, and image recompression, cutting origin transfer by more than 90%.
Read the full case studyThe production servers behind my client work are watched by a self-hosted Grafana, Prometheus, and Loki stack — dashboards, logs, and alerting with escalation. This site itself runs on Vercel and is observed through Vercel analytics.