What the page downloads
The client runtime has a ceiling per entry, and the honest number is the one that is bigger than all of them.
Goal
Ask what your shop actually sends to a browser, and find out which of your own decisions put each byte there.
You have added a signal, a live region and instant navigation. Each of those is a client entry, and each entry has a byte ceiling the build enforces. Now look at what the page you built downloads.
1 · Ask
npx weft build
pnpm bench budget| Entry | What put it there | Measured | Ceiling |
|---|---|---|---|
app-route | the quantity signal | 3,190 B brotli | 12,288 B |
channel-route | the live region | 4,121 B brotli | 4,608 B |
nav-route | instant navigation | 4,970 B brotli | 5,120 B |
runtime | everything, if a page used it all | 6,137 B brotli | 6,144 B |
Those are the entries this page reached for, at what the gate last measured them and against the ceiling it holds them to. They are read out of packages/bench/budgets.json — the file pnpm bench budget writes — rather than typed here, for the reason the whole of this tutorial has been making: a number somebody transcribed is a number that is wrong the next time it moves.
2 · Spend less by declaring less
| Take away | What stops shipping |
|---|---|
| The quantity signal | adopt — a page with no wiring gets no client at all |
live: true | channel — nothing subscribes, so nothing is sent |
| Nothing | the shell is markup, and markup has no runtime |
Every byte on that list is there because a declaration you made put it there, which means every byte is one you can remove by removing the declaration. What the page downloads has the ceilings and how they are held.