The weight of every page, measured

How to read a budget

“Own JS” is what a route adds on top of the lightest route's file set, which is 690.1 KB in this build, and “Total” is everything it loads. The two columns answer different questions: own tells you what a page brought with it, total tells you what a reader downloads on a cold visit. The bundle-splitting page shows the layout import that changed that arithmetic for pages which render no demo at all.

Every page in this section

One item in this section is not a page: #412 puts the measured size change on every changelog entry from 2026-09-10 onward, including the entry that describes the fix itself — see the changelog.

• Font loading#401Two subsets instead of nine, both preloaded — before and after numbers.
• Zero-JS showcase#402What the site looks like with JavaScript switched off, read from its own HTML.
• Lazy mounting#403Demos mount when you scroll near them, and the trade-off that creates.
• No images#404Why there is no image pipeline, and what would break the rule.
• Cache headers#405Every rule this build serves, in order, plus the invalidation plan for a CMS.
• Bundle splitting#406What ships where, and the layout import that put 485 KB on every page.
• Blur budget#407Every backdrop-blur in the project, classified by how much surface it covers.
• Layer inspector#408Mount a demo and read every property it animates, classified by what the compositor can take.
• Prefetch strategy#409Why catalog cards wait for intent, with the payload of one prefetch measured.
• Timers & listeners#410Registrations against cleanups, file by file, from the source.
• Device matrix#411The three device classes this site is tested against — and what has not been run.
• Build report#413What the production build compiles in: routes, chunks, fonts, HTML.
• Service worker plan#414Offline for the catalog after the API lands, and why it is not shipped yet.