5 ms·

For Google it makes sense. The faster you resolve DNS, the more webpages with ads you visit. Small price to pay to increase impressions.

• chipperyman573 8y ago
  DNS is not the bottleneck for page load speeds, especially now that 99% of the internet has images or video (even if the images are not a main focus of the webpage, such as a news article's image header)
  • T-hawk 8y ago
    Bandwidth bottleneck, no. Latency, time to first usable content on screen, absolutely.
    • gsich 8y ago
      Also consider that every shitty webpage needs to load ressources from a dozen other domains.
    • stock_toaster 8y ago
      > time to first /usable/ content on screen If we are going by time to first /usable content/, then I would blame javascript for most of the it.
• mdellabitta 8y ago
  DNS over HTTPS is actually a lot slower to resolve than traditional UDP DNS.
  • gsich 8y ago
    Yes, but only because of TCP and TLS connection overhead. Once the connection is established, response time is similar to UDP.
    • yjftsjthsd-h 8y ago
      Does the connection get reused?
      • cbsmith 8y ago
        Yes.
        • gsich 8y ago
          Not for long.
          • tracker1 8y ago
            If the browser is controlling the resolver in question, there's no reason not to hold long-running connections, or reconnecting on disconnect.