Field notes on static sites, caching and fast front ends
Short, practical write-ups from client work: what was slow, why, and what fixed it.
Cache-Control for static assets: the short version
Fingerprinted files get a year, HTML gets revalidation, and everything else is a judgement call.
Measure first: a 20-minute performance audit
A repeatable routine for finding the one thing that is actually slow.
Web fonts without the layout shift
Subsetting, preloading one file, and choosing a fallback that has similar metrics.
Images that fit the layout they are in
Width and height attributes, srcset with honest sizes, and when not to lazy-load.
Do you need a build step at all?
For a site of a dozen pages, a folder of HTML files is a legitimate architecture.
HTTP/2 did not end bundling
Multiplexing removed the connection limit, not the cost of a request.