# Vercel — Latency numbers every frontend developer should know

- Company: Vercel (vercel.com)
- Announced: 2024-04-23T13:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://vercel.com/blog/latency-numbers-every-web-developer-should-know
- Record: https://forck.live/items/20989-latency-numbers-every-frontend-developer-should-know
- Subject: v0 / AI SDK / AI Gateway

Vercel published a reference table of network and browser latencies relevant to frontend developers, covering metrics from WiFi (1–4ms) to worst-case intercontinental round trips (300ms). The post explains how these numbers compound in network waterfalls and notes that technologies like React Server Components can move such waterfalls to the server, where the same request pattern may be 100 times faster.

## Evidence

Verbatim from https://vercel.com/blog/latency-numbers-every-web-developer-should-know:

> A frontend take on Jeff Dean's "Latency Numbers Every Programmer Should Know".
> 
> Web page load times and responsiveness to user action in web apps is a primary driver of user satisfaction–and both are often dominated by network latency.

---

Record: https://forck.live/items/20989-latency-numbers-every-frontend-developer-should-know
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md