What does Thumb Zones and the First Screen conclude, in numbers, about “Above the Fold: Pixel Allocation, the Arithmetic of Three Web Metrics, the Evidence on Skeleton Screens and a Hero Byte Budget”?
Answer: The first screen is fixed land. On the visible height with browser bars expanded, Nightamber's layout B cannot fit a square hero and the in-flow price together; the price stays on the first screen only through the persistent action bar. Of LCP's four segments, A's most expensive is the time before the hero is discovered: compressing the image alone brings the 75th percentile from 4.72 s to 3.65 s, and only the new discovery path brings it to 1.71 s. The hero budget from p61's simulation is 185 KB with headroom; a twice-density AVIF needs only 96.0 KB, a three-times one 216.0 KB. Most of the CLS comes from one unsized hero, 0.5971 in a single shift; most of the INP from third-party long tasks during the first screen. Whether skeleton screens shorten perceived waiting cannot be settled on present evidence, and Nightamber treats it as a hypothesis to test rather than a default.
Scope of the numbers: All brands and figures are invented samples computed by the book's programs; laws on privacy consent and accessibility are described only in general terms and are not legal advice.
Data table
The numbers below are printed verbatim by the chapter's Python program and can be reproduced by running it. standard-library Python onlyprinted values that match the answer: 1.71, 185, 3.65, 4.72, 75
| segments in seconds: TTFB + load delay + load duration + render delay = LCP | |
| slow ( 1.6 Mbit/s, 0.150 s) A | 0.80 + 2.25 + 2.75 + 0.15 = 5.95 s poor |
| slow ( 1.6 Mbit/s, 0.150 s) B | 0.80 + 0.00 + 1.13 + 0.02 = 1.95 s good |
| typical ( 9.0 Mbit/s, 0.060 s) A | 0.44 + 0.66 + 0.52 + 0.15 = 1.77 s good |
| typical ( 9.0 Mbit/s, 0.060 s) B | 0.44 + 0.00 + 0.23 + 0.02 = 0.69 s good |
| simulated layout A: p75 LCP 4.72 s; share < | 2.5 s 0.223; share > 4.0 s 0.373 |
| simulated layout B: p75 LCP 1.71 s; share < | 2.5 s 0.943; share > 4.0 s 0.007 |
| layout B pipeline: largest hero with simulated p75 LCP < | 2.5 s: 335 KB |
| layout B pipeline: largest hero keeping 0.5 s spare (p75 < | 2.0 s): 185 KB |
| layout A pipeline carrying B's 96 KB file: p75 LCP 3.65 s (needs work) |
Show the full program
# Chapter 6. p61: LCP of the Nightamber hero in four segments, a simulated p75, and a hero byte budget.
# LCP = time to first byte + resource load delay + resource load duration + element render delay.
# All page and network numbers are assumptions for the book's sample, not measurements (KB = 1000 bytes):
# TTFB = 3 round trips to open the connection + 1 for the HTML + 0.20 s of server time.
# A: the hero is a slide of a carousel script (300 KB) on a separate image host; the browser learns of it
# only after the script arrives and runs (0.15 s) and a new connection opens (3 round trips);
# 1200 x 1500 JPEG of 420 KB; 0.15 s from arrival to paint while the carousel lays itself out.
# B: the hero is an <img> in the HTML with width, height and fetchpriority="high", same host, 1:1,
# 780 x 780 AVIF of 96 KB; 0.02 s from arrival to paint.
# Both: 100 KB of CSS and fonts download alongside the hero and share the line.
# Population: 20,000 simulated visits; round trip log-normal around 0.12 s (sigma 0.5), bandwidth log-normal
# around 4 Mbit/s (sigma 0.8); seed 6161. A synthetic population, not field data.
# Thresholds (good / poor) as published by Google at the time of writing: 2.5 s and 4.0 s at the 75th
# percentile; always check the current official Web Vitals documentation.
import math
import random
GOOD, POOR = 2.5, 4.0
SERVER, SHARED = 0.20, 100
PAGES = {"A": dict(hero=420, script=300, run=0.15, new_host=3, render=0.15),
"B": dict(hero=96, script=0, run=0.0, new_host=0, render=0.02)}
PROFILES = [("slow", 1.6, 0.150), ("typical", 9.0, 0.060)] # name, Mbit/s, round trip s
def secs(kb, mbps):
return kb * 8 / 1000 / mbps
def lcp(page, mbps, rtt, hero=None):
p = PAGES[page]
ttfb = 4 * rtt + SERVER
delay = (rtt + secs(p["script"], mbps) + p["run"] if p["script"] else 0.0) + p["new_host"] * rtt
load = rtt + secs((p["hero"] if hero is None else hero) + SHARED, mbps)
return ttfb, delay, load, p["render"]
def grade(t):
return "good" if t <= GOOD else ("poor" if t > POOR else "needs work")
def p75(values):
v = sorted(values)
return v[math.ceil(0.75 * len(v)) - 1]
print("segments in seconds: TTFB + load delay + load duration + render delay = LCP")
for name, mbps, rtt in PROFILES:
for page in PAGES:
parts = lcp(page, mbps, rtt)
print(" {:<7} ({:4.1f} Mbit/s, {:.3f} s) {}: {:.2f} + {:.2f} + {:.2f} + {:.2f} = {:5.2f} s {}"
.format(name, mbps, rtt, page, *parts, math.fsum(parts), grade(math.fsum(parts))))
rng = random.Random(6161)
visits = [(4.0 * math.exp(rng.gauss(0, 0.8)), 0.120 * math.exp(rng.gauss(0, 0.5))) for _ in range(20000)]
for page in PAGES:
t = [math.fsum(lcp(page, m, r)) for m, r in visits]
print("simulated layout {}: p75 LCP {:.2f} s; share <= {} s {:.3f}; share > {} s {:.3f}".format(
page, p75(t), GOOD, sum(1 for x in t if x <= GOOD) / len(t), POOR,
sum(1 for x in t if x > POOR) / len(t)))
def budget(limit):
lo, hi = 0, 3000
while lo < hi:
mid = (lo + hi + 1) // 2
if p75([math.fsum(lcp("B", m, r, mid)) for m, r in visits]) <= limit:
lo = mid
else:
hi = mid - 1
return lo
print("layout B pipeline: largest hero with simulated p75 LCP <= {} s: {} KB".format(GOOD, budget(GOOD)))
print("layout B pipeline: largest hero keeping 0.5 s spare (p75 <= {:.1f} s): {} KB".format(
GOOD - 0.5, budget(GOOD - 0.5)))
t = [math.fsum(lcp("A", m, r, 96)) for m, r in visits]
print("layout A pipeline carrying B's 96 KB file: p75 LCP {:.2f} s ({})".format(p75(t), grade(p75(t))))Single source and citation
Fan, Y. (2026). Mobile Thumb-Zone Kinetics, Dark-Luxury Micro-Interactions and Above-the-Fold Visual Retention Engineering (Version 0.1.0), Chapter 6: Above the Fold: Pixel Allocation, the Arithmetic of Three Web Metrics, the Evidence on Skeleton Screens and a Hero Byte Budget. 5D Library. DOI pending
DOI pending · monograph page goes live after publication · 5DL-B-137 · v0.1.0 · CC-BY-NC-ND-4.0
BibTeX
@book{fan2026137,
author = {Fan, Yafu},
title = {Mobile Thumb-Zone Kinetics, Dark-Luxury Micro-Interactions and Above-the-Fold Visual Retention Engineering},
year = {2026},
publisher = {5D Library},
edition = {0.1.0},
note = {DOI pending}
}Other chapter answers in this book
- Chapter 1 · Method: Four Measurable Losses, the Book's Sample, Evidence Grades and A/B Design
- Chapter 2 · The Thumb Zone: the Geometry of What a Finger Can Reach
- Chapter 3 · The Sticky-Header Tax: Browser Bars, Safe Areas, Stacked Banners and Floating Widgets
- Chapter 4 · The Arithmetic of Gold on Black: Display Polarity, Halation, Contrast Floors and Ceilings, and Price Numerals
- Chapter 7 · The Boutique Playbook: Product Page, Checkout, Private-Message Entry, Membership Page and the Distillation Spec
- Chapter 8 · Practice: The Nightamber Product Page from Diagnosis and Redesign to a Pre-Registered A/B Test