tag
performance
5 entries.
-
Most Websites Are Documents. Stop Shipping Them as Applications.
A phone downloads 486 KB of this site's home page, and 24 KB of it is what the generator wrote. The rest is choices. The case for static sites, measured.
-
What Breaks If I Change This?
We built an incremental build for 1.8.60. It made a five-thousand-page site five per cent faster. Here is why we shipped it anyway, and what it is actually for.
-
I Went Looking for CPU Tricks and Found a Quadratic Loop
The plan was SIMD and PGO. The profiler said two thirds of the build was syscalls from listing one directory per post. Fixing that made it 5.25x faster.
-
The Build Got Parallel — and the Caches Nobody Told You About
Page rendering and WebP conversion now run in parallel, one worker per CPU — plus three speed features that were already working and never written down.
-
Your hero image is your LCP score
Largest Contentful Paint is usually one photograph. A tour of the build-time image pipeline — srcset, crops, cache keys — and an honest note about AVIF.