Browsers can now cache our static assets for a full year

Our static asset chunks — JavaScript bundles, web fonts, optimized images — were being served without cache headers. Browsers were revalidating every file on every navigation, paying a round-trip even for content-hashed files that literally never change.

All three static asset paths now ship with public, max-age=31536000, immutable. A returning visitor's browser keeps the entire cached bundle, only fetching what's genuinely new in a deploy.

The cumulative effect for repeat visitors is significant: the second page load on your blog is now almost entirely served from cache.