Every feature enters the page as a liability.
THE PAGE-
WEIGHT
LEDGER
WEIGHT
LEDGER
An Accountant’s Guide to Digital Infrastructure
A feature may earn its cost through conversion, utility, evidence, compliance, or operational control.
If nobody records the cost, the page accumulates liabilities without an owner.
Nothing is free because the plugin had no purchase price.
The Accounting Problem // A Cost With No Invoice
Digital Infrastructure Has a Balance Sheet
A website feature can create value.
It can also add transfer bytes, network requests, main-thread execution, privacy exposure, maintenance work, vendor dependence, layout instability, and failure points.
Most organizations record the subscription price and ignore everything else.
The Page-Weight Ledger treats each addition as an infrastructure decision with an expected return and a measurable carrying cost.
2025 Benchmark // What the Median Homepage Ships
The Typical Mobile Front Gate Is Already Heavy
The HTTP Archive’s 2025 Web Almanac measured a median mobile homepage of approximately 2.56 MB.
Images accounted for about 911 KB, JavaScript 632 KB, fonts 122 KB, CSS 77 KB, and HTML 22 KB.
Those numbers are descriptive, not targets.
A page does not become efficient merely because it is lighter than the median.
Images911 KB
JavaScript632 KB
Fonts122 KB
CSS77 KB
HTML22 KB
The median describes the market’s accumulated habits. It does not define the cost your customer should accept.
The Cost Classes // Five Ways a Component Can Slow the Page
File Size Is Only the First Account
JavaScript is especially deceptive because it is active weight.
The browser must download it and then spend processor time executing it.
A small script can therefore cost more than a larger static image on a slow phone.
Planning Ledger // Common Additions and Their Allowances
Estimate Before Installation. Measure After Installation.
The ranges below are Nova planning allowances for an initial budget conversation.
They are not universal measurements, vendor guarantees, or seconds of load time.
A specific implementation can fall below or far above them.
| Component | Planning transfer | Requests | CPU / render risk | Primary hidden account |
|---|---|---|---|---|
| One optimized hero image | 60–180 KB | 1 | Low | LCP discovery and dimensions |
| Image carousel / gallery | 250 KB–2 MB+ | 4–20+ | Medium | Offscreen media loaded too early |
| Background or embedded video | 1–10 MB+ | 2–12+ | High | Autoplay, decoding, and data use |
| Custom web-font family | 35–250 KB+ | 1–8+ | Medium | Every weight/style may be another file |
| Google Fonts stylesheet + files | 35–250 KB+ | 2–10+ | Medium | Third-party connection and font swap |
| Analytics + tag manager | 70–350 KB+ | 4–25+ | High | Tags can load more tags |
| Advertising / retargeting stack | 200 KB–1.5 MB+ | 15–100+ | Very high | Auctions, trackers, and third parties |
| Chat or support widget | 150 KB–1 MB+ | 8–40+ | High | Continuous scripts and connections |
| Embedded map | 300 KB–1.5 MB+ | 10–40+ | High | Tiles, interaction code, and APIs |
| Social feed / video embed | 250 KB–2 MB+ | 8–50+ | High | Player UI, tracking, and recommendations |
| Consent-management platform | 50–400 KB+ | 3–20+ | Medium–high | Blocking order and regional logic |
| Heatmap / session replay | 50–300 KB+ | 3–15+ | High | DOM observation and event capture |
| A/B testing / personalization | 50–400 KB+ | 3–20+ | High | Flicker control and decision latency |
| Calendar / scheduling embed | 150 KB–1 MB+ | 6–35+ | High | Third-party application inside the page |
| Page builder / plugin bundle | 200 KB–2 MB+ | 10–70+ | Very high | Unused code shipped sitewide |
A planning allowance creates a question. Only a before-and-after test creates the answer.
Planning Tool // Proposed Infrastructure Estimate
Build a Preliminary Page-Weight Reserve
Select the components being considered.
The estimate uses the midpoint of the planning ranges above and reports transfer and request exposure.
The network-time figure represents transfer time alone; it excludes latency, connection setup, server response, JavaScript execution, rendering, contention, caching, and compression differences.
Mbps
Planning estimate only. Run the proposed component on the actual page, test a cold mobile visit, inspect its request chain and main-thread work, then replace every allowance with observed data.
Font Accounting // The Quiet Liability
A Typeface Is Not One File
Web fonts can affect both load time and rendering time.
A family may require separate files for regular, bold, italic, condensed, and language variants.
The 2025 Web Almanac reported a median individual font file in the mid-30 KB range and roughly four font requests on the median page.
At the 90th percentile, individual font files were approximately 115 KB.
External font services can also add third-party connection setup before the browser retrieves the font.
01Prefer system fonts when brand value does not justify the transfer.
02Load only the weights and character sets actually used.
03Use WOFF2, subset carefully, and define an intentional font-display policy.
04Preload only fonts required for visible first-screen text.
05Measure layout shift when the fallback and final font exchange.
Capital Approval // The Feature Intake Form
No Component Without an Owner and a Return
- What commercial or operational job does it perform?Name the decision, conversion, compliance duty, or workflow it improves.
- What does it add?Record transferred bytes, request count, domains, main-thread time, layout movement, permissions, and ongoing fees.
- Where does it load?Do not charge every visitor for a feature needed on one page or after one interaction.
- What is the performance budget?Define the maximum cost before development begins and reject the component if it cannot remain inside it.
- How will value be verified?Measure the intended outcome and the performance guardrails before and after deployment.
- When will it be removed?Set an owner, review date, failure threshold, and deletion rule.
A component without an owner becomes permanent. A component without a measurement becomes innocent.
The Performance Budget // A Policy Before a Preference
Set the Ceiling Before Creative Work Begins
A practical budget assigns limits to total transfer, critical-path transfer, JavaScript, fonts, third-party requests, LCP, interaction latency, and layout shift.
The limits should be tested on representative mobile hardware and network conditions.
When a new feature breaks the budget, the owner has four choices:
Optimize it.Delay it.Replace it.Remove it.
“Keep it and accept the loss without measurement” is not an accounting decision.
Conclusion // Infrastructure With a Price
Make Every Addition Earn Its Place
A font can strengthen a brand.
A video can demonstrate what words cannot.
A chat tool can create a customer conversation.
An analytics system can reveal where revenue is being lost.
Each can also slow the page, obstruct the message, expose data, add maintenance, and create another vendor dependency.
The purpose of the ledger is not to prohibit useful infrastructure.
It is to stop useful-sounding infrastructure from entering without a price.
Record the cost. Name the return. Test the result. Remove what does not pay.
Documented Sources // Measurement and Guidance
Evidence Behind the Ledger
Continue the Nova Research Series
White Paper 15
Technical Alpha
→