Page weight is one of the clearest indicators of how a site behaves on a weak mobile connection, and it is easy to measure without guesswork. When I shipped v2.0 of my studio site (theronradley.vercel.app), I wrote a build script to count every first-party request each route makes, sum the exact bytes on disk, and run gzip -9 over every asset. None of the numbers below are estimates.
Key findings
- The studio home page makes 21 first-party requests and transfers 167.3 KB raw, or 80.6 KB after gzip.
- Text routes like
/about/and/faq/make 5 requests and ship 61 to 65 KB gzipped, with 8.2 KB of JavaScript and no UI framework runtime. - Self-hosted fonts are the single largest fixed cost (45.9 KB on an uncached visit).
- Using four palette-tinted SVGs on
/services/instead of raster photos kept all four illustrations combined to 70.5 KB (17.6 KB on average) at any screen density.
Route-by-route totals
Every page shares the same 45.9 KB font files and 40.3 KB stylesheet, so differences across routes come down to HTML length, interactive scripts, and SVG artwork:
| Route | Req | HTML | JS | Raw | Gzip |
|---|---|---|---|---|---|
/ | 21 | 31.2 KB | 27.3 KB | 167.3 KB | 80.6 KB |
/about/ | 5 | 25.4 KB | 8.2 KB | 119.8 KB | 63.3 KB |
/faq/ | 5 | 43.0 KB | 8.2 KB | 137.4 KB | 65.0 KB |
/research/ | 5 | 18.4 KB | 8.2 KB | 112.8 KB | 61.7 KB |
/research/site-weight/ | 5 | 26.9 KB | 8.2 KB | 121.3 KB | 63.7 KB |
/services/ | 9 | 23.1 KB | 8.2 KB | 188.0 KB | 84.0 KB |
/work/ | 7 | 15.6 KB | 27.3 KB | 129.0 KB | 67.3 KB |
Method and limits
After npm run build, a script parses each generated HTML file, resolves linked stylesheets, scripts, preloaded fonts, and SVGs, and writes raw plus gzip -9 byte totals to JSON in the repo. Live CDN responses use Brotli, which compresses a bit smaller, so gzip gives a conservative upper bound.
Transfer size also has clear limits: a build-time byte count does not measure server tail latency (which is what Wiremark tests), browser layout time, or warm-cache navigation. Still, keeping exact byte budgets in version control is one of the practical reasons I stick to hand-coded websites over page builders.