# Architecture vs performance

ARCHITECTURE
Client HARs demonstrate worker/WASM startup, seven sideload requests and finalize. Server runs use normal WP-CLI media import and are explicitly `SERVER PROCESSING ONLY — NETWORK EXCLUDED`.

BROWSER PROCESSING COST
Cold worker load: 26.118915 s and 4,561,631 transferred bytes. Warm median avoids that cold load but remains 84.289461 s end-to-finalize.

NETWORK COST
Client original request content-length: 5,636,291 bytes; sideload total: 1,282,111 bytes; finalize: 1,008 bytes; total media upload bytes: 6,919,410. This is approximately 22.8% above source bytes.

SERVER PROCESSING COST
Measured server-only median: 11.120 s. CPU and memory deltas are NON DÉMONTRÉ.

STORAGE
Client estimated total stored: 6,915,070 bytes. Server total stored: 1,719,883 bytes; server generated derivative bytes excluding original: 985,084 vs client derivative bytes 1,279,181.

USER EXPERIENCE
No end-to-end client/server superiority claim is valid because server runs exclude user network transfer.