Core Web Vitals

ISR + static pre-rendering

High-traffic TCG/Pokedex pages use revalidate = 86400 and generateStaticParams, so the largest painted element is already in a CDN-cached HTML file before the first request arrives.

Code splitting + streaming SSR

next/dynamic with a ThoughtsSkeleton loading fallback splits each write-up into its own chunk. Suspense boundaries stream the skeleton immediately while data fetches resolve in parallel on the server.

Specific transitions + startTransition for non-urgent updates

Replaced transition-all with explicit property lists (transition-[opacity,transform] for entrance animations, transition-[border-color,box-shadow] for hover) so the browser only watches the properties that actually change. startTransition wraps state updates that kick off large re-renders so input events aren't blocked.

Pixel-matched skeletons per view, no unsized content

Each lazy-loaded calendar view (day, week, year) ships with a skeleton that mirrors the real view's exact row heights and grid structure, so the page doesn't shift when the JS chunk arrives. ThoughtsSkeleton mirrors the Summary article layout that thoughts pages open on, so it doesn't flash the chat view first.

Static landing page + CDN caching + connection pooling

The landing page is statically rendered at build time. NBA and TCG proxy routes set public, s-maxage=300/3600 for CDN caching. Railway Postgres uses a connection pool so there is no per-request handshake.