Connection Time
The DNS lookup plus the secure connection (TCP/SSL), before the request even reaches your server — entirely the user carrier's territory, not your code.
Updated: Dec 2025
Computational logic
Built from two stages, DNS and the secure connection (TCP/SSL), both of which happen before the request reaches your server; Shahin adds the two stages per visit and shows P75 as the card's basis. To see the exact split between DNS and the secure connection, check the "Connection time by carrier" box plot with its three-way DNS / secure connection / combined switch — only visits on a fresh connection count, because on a reused connection these two stages are zero.
Use-case narrative & business value
Because this number happens entirely before the request even reaches your server, it being high has nothing to do with your code or database. The card's main use is separating responsibility: if this is high while server response time is low, the problem sits with the CDN or the user's carrier, not your back-end team — and once that split is clear, engineering time doesn't get wasted auditing code that was never at fault.
Was this page helpful?