Performance budget: 158 to 184 kB on every route, over the 120 kB budget

Gzipped first-load JavaScript of the production build, every prerendered public route: all 140 are over the 120 kB budget. Home 179.9 kB, Pricing 163.6 kB, Start a project 178.9 kB, the research index 159.1 kB, this page 160.0 kB; the heaviest is /redline at 183.5 kB and the lightest 157.9 kB. The same pages fetched from the live site measure within half a kilobyte of the build. The shared framework and site code is most of it, so this is a site-wide failure rather than one heavy page, and it stays a failure until a later reading shows the routes inside the budget.

Fail·Measured on 19 October 2026·Our own audit, point 01

Target, not a result: Every route inside a performance budget

The whole auditRaw observations, 19 October 2026 (JSON)

Method

The production build (next build) of the code on the main branch the evening of the reading. This version of Next.js no longer prints a first-load column, so the figure is the gzip size of every script the prerendered HTML of a route loads at first paint, the legacy-browser polyfill excluded, summed per route; cross-checked by fetching the same scripts for seven routes from the live https://uxpro.ca

Limits of this reading

• A byte count, not a speed reading: how much JavaScript a phone downloads before the page is interactive, not how long it takes.
• Gzip is the yardstick the budget was set in; the live site can serve a smaller Brotli transfer, so the bytes on the wire are lower than these figures.
• Scripts a page loads later, on scroll or interaction, are not counted.
• A reading of the live uxpro.ca on this date, under its production configuration; a later deployment can differ.
• It stays on the ledger, marked as a failure, until a later dated record shows it fixed.