TinkerThe slowest page: Wen in Farhaven, 2,060 ms.8,000 km · 14 trips to the shop · 1 resent · 2,060 ms
Chapter 7 of 7
Make the page fast for everyone
Everything is on the bench: the DNS TTL, the HTTP version and resumption. The owner has set a budget for every customer.
This chapter: Which settings get every customer’s page in on time, and let a move be found?
About this chapter
You will learn
- How the round trips add up per customer
- Why the farthest customer decides
- Why more than one setting can work
Words you’ll meet
- Budget
- The longest the owner lets any customer’s page take.
Step 1 of 2
The owner’s : every page within 1,500 ms on lossy lines, and a moved shop found within 60 minutes.
Find settings that meet both.
2,060 ms slowest page OVER 1,500 MS
| Customer | Distance | Page |
|---|---|---|
| Ines, Millbrook | 40 km | 149 ms |
| Tomas, Eastport | 1,200 km | 244 ms |
| Dara, Northgate | 2,500 km | 460 ms |
| Wen, Farhaven | 8,000 km | 2,060 ms |
| A moved shop found within | 60 min | 1 hour |
Every customer’s page, the hinge photo included, must be in within 1.5 seconds, even on a line that loses a packet. When the shop moves to a new address, every customer must find it within an hour.
A copy near each customer shortens the road itself: see Caching & CDNs.
Simulated: Larkspur’s own customers and planning numbers, not a measurement of any real network or browser.