WebWeb Design and Engineering
Next.js, React, modern CSS, performance, immersive web, frontend architecture.
Web
WebWeb font performance: one WOFF2 file, zero layout shift
An unoptimised family adds 500KB and delays readable text. Subset to WOFF2, self-host it, tune the fallback with size-adjust so nothing moves on swap.
Web6 frontend mistakes that tank your Lighthouse score in 2026
Total Blocking Time is 30% of the Lighthouse score, yet most teams fix the wrong metric. The six production mistakes that crater it, and how to fix each.
WebType-safe RPC with Next.js Server Actions: skip the API layer
A Server Action is already an RPC. Here is how to make it type-safe end to end and validated at runtime, with no API route or response type to maintain.
WebWebsite architecture in 2026: SPA homepage, static for the rest
Most marketing sites overengineer every page. We treat the homepage like an app and ship the other 95% as static docs, splitting the build target by intent.
WebCore Web Vitals on Next.js in 2026: how to ship green
Concrete steps to hit Good on LCP under 2.5s, INP under 200ms, and CLS under 0.1 on a Next.js 16 SaaS, plus how to read field data when Lighthouse lies.
WebImmersive web stack in 2026: Lenis, GSAP, and what to skip
Lenis (3 kB), GSAP free since April 2025, ScrollTrigger for scroll math, and native CSS scroll-driven animations. The 2026 stack we ship in production.
WebTypeScript strict mode: the 9 settings we never turn off
strict: true turns on 9 checks, and since TypeScript 6.0 it is the default. What each flag catches in production, plus the 3 flags outside the bundle we add.
WebNext.js development agency vs in-house: when each one wins in 2026
A US senior Next.js hire costs $195,000 fully loaded and takes six weeks to find. Agency rates run $60 to $250 per hour. Here is how each one wins.
WebNext.js Server Actions security: 13 advisories and 2026 fixes
Next.js shipped 13 security advisories in 2026: middleware bypass, cache poisoning, and SSRF. What changed and how to ship Server Actions safely now.
WebEdge runtime vs Node runtime: Next.js 16 moved the default
Next.js 16 moved middleware to the Node runtime and renamed it proxy.ts. Where Edge still wins on latency, where Node wins on packages and long tasks.
Web