Measured Local Benchmark

Can One Character Code
reduce storage & transfer size?

We measured real file sizes. Traditional self-contained HTML pages vs. OCC carrier pages with shared reader and registries. Here is what the numbers show.

"Measured local benchmark — not guaranteed global reduction"

13,591

Traditional page avg (bytes)

1,324

OCC carrier avg (bytes)

6,209

Registry avg (bytes)

4,817

Reader (shared once, bytes)

Break-even (pages)

43%

Reduction at 100 pages

90.3%

carrier reduction vs. traditional page

The OCC carrier for a utility app averages 1,324 bytes. The full traditional page it replaces averages 13,591 bytes. The carrier alone is 90% smaller — the reader and registry are loaded once and shared across all pages.

Benchmark Sets

Set A uses files measured from this local benchmark. Sets B and C are extrapolated from Set A averages. Set D uses the actual LAN Wikipedia OCC demo package files. Set E isolates a single page load.

Set	Pages	Traditional	OCC Total	Reduction	Note

Break-even point: 4 pages. After 4 pages, every additional OCC page costs ~7,533 bytes instead of ~13,591 bytes. Savings per additional page: ~6,058 bytes. The shared reader (4,817 bytes) and chain-nav (15,463 bytes) are paid once, then amortized across all pages.

Storage Reduction by Set

Each pair of bars shows total bytes for traditional pages vs. OCC pages (carriers + registries + shared reader). Green bars are OCC.

Traditional HTML

OCC Total

Savings vs. Page Count

As page count grows, the shared reader overhead is amortized across more pages and total OCC bytes grow more slowly than traditional.

First load includes the reader and chain-nav (20,280 bytes total). After they are cached, each new OCC carrier can be extremely small — averaging 1,324 bytes vs. 13,591 bytes for a traditional page.

Transfer Time by Connection Speed

Estimated transfer times for 10 pages (Set A) and the LAN Wikipedia package (Set D) at common connection speeds. Pre-compression byte counts.

Speed	Trad. (10 pages)	OCC (10 pages)	Trad. (LAN Wikipedia)	OCC (LAN Wikipedia)

Set D: LAN Wikipedia Proof

The LAN Wikipedia demo shows OCC applied to a known real-world page. The carrier for the full 284 KB Wikipedia article is just 3 bytes.

Item	Size	Notes
Wikipedia "Local area network" full page	284,000 bytes	Source: en.wikipedia.org
OCC carrier (◆ character)	3 bytes	Black Diamond Unicode character
OCC reader (shared)	4,817 bytes	Paid once, cached after first load
LAN article package (all 6 files)	35,251 bytes	Article HTML, CSS, manifest, attribution
OCC total (carrier + reader + package)		vs. 284,000 byte full page
Reduction	79%	Measured from actual files

Attribution: This demo adapts content from the Wikipedia article "Local area network." Source: en.wikipedia.org/wiki/Local_area_network. Licensed CC BY-SA 4.0. Not affiliated with or endorsed by Wikipedia or the Wikimedia Foundation.

Honest Conditions

These numbers represent a measured local benchmark. Real-world results depend on how many pages share the same reader and how often it is cached.

📈

Savings grow with page count

The shared reader is paid once. The more pages in the system, the more the overhead is amortized. Break-even: 4 pages.

📌

First load carries overhead

The first page load includes the reader (4,817 bytes) and chain-nav (15,463 bytes). After caching, subsequent pages are just carrier + registry.

📸

Images counted separately

This benchmark measures HTML, CSS, and JavaScript only. Dynamic assets and images are not included and still count against bandwidth.

📄

Pre-compression bytes

All byte counts are uncompressed file sizes. Gzip and Brotli compression reduce transfer sizes further for both traditional and OCC files.

🔢

Measured, not modeled

Traditional pages were generated locally. OCC carriers and registries were copied from the live staging environment. Sizes are actual.

🎯

Registry vs. reader distinction

The OCC registry (~6,209 bytes avg) holds the app logic. The reader (~4,817 bytes) renders it. Different from page to page; reader is constant.

Methodology

Full details on how this benchmark was conducted.

Measurement	Source	Bytes
10 traditional HTML pages	Generated locally — full nav, CSS, app, footer (self-contained)	13,591 avg
10 OCC carrier pages	Copied from live staging (calculator, clock, todo, etc.)	1,324 avg
10 OCC registries	Copied from live staging demos/ directory	6,209 avg
occ-reader.min.js	Copied from live staging js/	4,817
chain-nav.js	Copied from live staging root	15,463
LAN Wikipedia package	Actual lan-wikipedia-package/ files (6 files)	35,251

Script: OCC_STORAGE_PROOF/RUN_OCC_STORAGE_BENCHMARK.ps1 • Reports: OCC_STORAGE_PROOF/reports/ • Version 1.0.0 • Run date: 2026-04-27

First Load vs. Repeat Load

The shared reader (4,817 bytes) and chain-nav (15,463 bytes) are downloaded once and cached permanently. After that, each new OCC page delivers only its carrier and registry.

Load Type	Bytes	What's Transferred	Notes

After the first load: the reader and chain-nav live in the browser cache. Every subsequent OCC carrier page delivers only its carrier (~1,324 bytes) and registry (~6,209 bytes) — smaller than the traditional equivalent.

Full Bandwidth Table

Transfer time estimates for carrier alone, single cached page, 10 pages, 100 pages, and LAN Wikipedia at four connection speeds.

Speed	Carrier (9 B)	1 Page Cached	10 Pages (Set A)	100 Pages (Set C)	LAN Wikipedia (Set D)

All times are estimated from pre-compression byte counts. Gzip typically reduces HTML and JSON by 60–80%, meaning real transfer times would be shorter.

Download Benchmark Data

Full benchmark results as structured JSON. Includes all set measurements, methodology notes, and honest conditions. Run RUN_OCC_STORAGE_BENCHMARK.ps1 locally to regenerate.

Benchmark script: OCC_STORAGE_PROOF/RUN_OCC_STORAGE_BENCHMARK.ps1 • Run date: 2026-04-27 • Version: 1.0.0 • Platform: Windows 11 / PowerShell 5.1

See OCC in Action

Explore the live demo apps, the LAN Wikipedia proof, and the three-code install system.

View All 14 Demo Apps

Can One Character Codereduce storage & transfer size?