B. Numbers Every Frontend Engineer Should Know
These numbers are rounded for memorability and stated as of late 2026. Thresholds are official definitions; device and network figures are typical ranges, not guarantees — measure your own users (Chapter 17).
Frames
Section titled “Frames”| Refresh rate | Frame budget | Realistic main-thread budget |
|---|---|---|
| 60 Hz | 16.67 ms | ~10 ms |
| 90 Hz | 11.1 ms | ~7 ms |
| 120 Hz | 8.33 ms | ~5 ms |
- Long task: > 50 ms. Long animation frame: > 50 ms.
- “Instant” response: within ~100 ms. UI transitions: ~150–300 ms; beyond ~500 ms motion feels slow.
Core Web Vitals and friends (at p75, mobile and desktop separately)
Section titled “Core Web Vitals and friends (at p75, mobile and desktop separately)”| Metric | Good | Poor |
|---|---|---|
| LCP | ≤ 2.5 s | > 4.0 s |
| INP | ≤ 200 ms | > 500 ms |
| CLS | ≤ 0.1 | > 0.25 |
| FCP | ≤ 1.8 s | > 3.0 s |
| TTFB | ≤ 0.8 s | > 1.8 s |
| TBT (lab) | ≤ 200 ms | > 600 ms |
- CrUX window: 28 days. CLS session window: shifts < 1 s apart, max 5 s; shifts within 500 ms of input excluded.
Network
Section titled “Network”| Link | Typical RTT |
|---|---|
| Same city to a CDN PoP (fibre) | 5–20 ms |
| Good 4G | 40–80 ms |
| Congested 4G (evening) | 100–300+ ms |
| India ↔ US East origin | ~200–250 ms |
| India ↔ Europe | ~120–160 ms |
- TCP initial congestion window: 10 packets ≈ 14 KB of payload in the first round trip.
- New HTTPS connection: ~2 RTT over TCP + TLS 1.3, ~1 RTT over QUIC, 0 RTT on resumption.
- Typical packet size limit (MTU): ~1,500 bytes.
JavaScript and devices
Section titled “JavaScript and devices”- Budget/mid-range Android single-core performance: roughly ⅕ to ½ of a flagship or a developer laptop.
- Rule of thumb: a 40 ms task on a laptop ≈ 150–250 ms on a budget phone.
- Parsing + compiling + executing 1 MB of (uncompressed) JS on a mid-range phone: on the order of hundreds of ms to over a second. Budget ~150–200 KB compressed JS on the critical path for content sites.
navigator.deviceMemoryis capped and rounded (e.g. 0.25–8 GB).
Memory and graphics
Section titled “Memory and graphics”- Decoded image: width × height × 4 bytes (a 4000×3000 photo ≈ 48 MB).
- GPU texture: w × h × 4 bytes; +33% with mipmaps (2048² ≈ 21 MB with mips).
- Full-screen layer on a 1080×2400 phone ≈ 10 MB.
- Browsers cap active WebGL contexts per page (Chromium historically around 16).
Caching conventions
Section titled “Caching conventions”| Resource | Cache-Control |
|---|---|
| Hashed assets | public, max-age=31536000, immutable |
| HTML | no-cache (or max-age=0, must-revalidate); at the CDN s-maxage=60, stale-while-revalidate=600 |
| API (personal) | private, no-cache |
| Sensitive | no-store |
| robots.txt / sitemap | max-age=3600 |
Limits worth remembering
Section titled “Limits worth remembering”- Cookie: ~4 KB each. localStorage: ~5 MB per origin.
- Sitemap: 50,000 URLs / 50 MB per file.
- Lighthouse “excessive DOM” flag: roughly 1,400+ elements.
- WCAG contrast: 4.5:1 body text, 3:1 large text/UI; target size minimum 24×24 CSS px (aim 44–48).