{"id":22359,"date":"2026-11-18T09:00:00","date_gmt":"2026-11-18T08:00:00","guid":{"rendered":"https:\/\/webhosting.de\/?p=22359"},"modified":"2026-11-13T16:27:23","modified_gmt":"2026-11-13T15:27:23","slug":"dns-tcp-tls-load-time-phases","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/dns-tcp-tls-ladezeit-phasen\/","title":{"rendered":"DNS Lookup, TCP Connect, and TLS Handshake: Breaking Down Load Time Correctly"},"content":{"rendered":"<div class=\"wh-article\" data-wh-layout=\"2.1.2\" style=\"width:100%;max-width:820px;margin:0 auto;color:#263b4b;font-family:inherit;font-size:18px;line-height:1.8;text-align:start;overflow-wrap:break-word;box-sizing:border-box\"><p class=\"wh-lead\" style=\"font-size:20px;line-height:1.7;color:#233746;margin:0 0 1.1em\">A look at the individual request phases reveals whether a website loses time while establishing a connection, waiting for a response, or downloading. The <strong style=\"font-weight:700;color:inherit\">Website Waterfall<\/strong> It classifies them in relation to other resources; curl provides additional timestamps for a single request. The protocol, cache, and connection status are crucial here: An existing connection can skip setup phases, and with HTTP\/3, the TCP model does not apply. No single phase, on its own, proves a specific cause.   <\/p>\n<nav class=\"wh-toc\" aria-label=\"Contents of this article\" style=\"display:block;margin:28px 0 38px;padding:22px;border:1px solid #d9e4e8;border-radius:14px;background:#f4f8f8\"><p class=\"wh-toc-title\" style=\"font-size:13px;font-weight:700;letter-spacing:.08em;color:#49656b;margin:0 0 14px\">Go directly to the section<\/p><div class=\"wh-toc-grid\" style=\"display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,280px),1fr));gap:10px\"><div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#request-phasen\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">An HTTPS Request in Stages<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#dns-connect-tls\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Understanding DNS, TCP, and TLS<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#antwort-download\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Waiting for a response and the download<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#waterfall-praxis\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Reading the Website Waterfall<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#curl-zeitpunkte\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Calculating curl Timestamps Correctly<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#verbindungen-protokolle\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Detecting Reuse and HTTP\/3<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#messung-vergleichen\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Comparing Measurements in a Reproducible Manner<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#resource-timing\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Resource Timing and Backend Telemetry<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#diagnose-optimierung\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Identify and Resolve Bottlenecks<\/a><\/div>\n<\/div><\/nav><section class=\"wh-section\" aria-labelledby=\"request-phasen\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"request-phasen\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">An HTTPS Request in Stages<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A new HTTPS request via HTTP\/1.1 or HTTP\/2 can initially be viewed as a sequence: The client determines a destination address, establishes a TCP connection, and negotiates TLS. Only then does it send the request and receive the response. This simplified model describes a new connection via TCP, not every subsequent request. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">At <strong style=\"font-weight:700;color:inherit\">DNS Lookup<\/strong> The domain name is resolved into an address that can be used to establish a connection. The TCP handshake then establishes the transport connection to the selected endpoint. The times visible during this process are recorded on the client side and therefore also depend on the network path taken. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The TLS handshake then lays the foundation for secure HTTPS communication: the client and the remote system negotiate cryptographic parameters, and the client verifies the server\u2019s identity. When establishing a new connection, both the processing required on the involved systems and message propagation times can be significant factors.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">After sending the request, the client waits for the first response byte and then receives the response body. The observed time therefore includes not only operations on the server but also the time it takes for data to travel between the client and the remote system. This sequence alone does not reveal exactly what work is involved in a given wait time. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A document request typically returns the HTML document, but it is not the same as the entire page load. The document may trigger additional resources, such as stylesheets, scripts, and images. The retrieval of these resources may overlap in time; therefore, their individual durations cannot simply be added to the page load time. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"dns-connect-tls\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"dns-connect-tls\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Understanding DNS, TCP, and TLS<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The visible DNS time describes how long the name resolution took from the client's perspective. It is not necessarily the response time of the authoritative DNS server: browsers, operating systems, and resolvers may use cached responses. A fast lookup therefore does not prove that the entire DNS path is equally fast for other clients. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">If DNS issues occur repeatedly, it\u2019s worth conducting a comparison under documented conditions: Which client and which resolver are being used? Is a cache hit likely? And is the same domain being queried? This helps determine whether the issue lies more with the local state or further down the resolution path.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The time required to establish a TCP connection depends, among other things, on the <strong style=\"font-weight:700;color:inherit\">Network latency<\/strong> to the actual endpoint being accessed. In the case of a CDN, this may be an edge server rather than the origin server. Repeated attempts to establish a connection can also extend the visible segment; therefore, a comparison of different locations should take the respective destination into account. <\/p>\n<figure class=\"wp-block-image size-large wh-figure\" aria-describedby=\"wh-caption-detail1\" style=\"display:block;float:none;clear:both;width:100%;max-width:760px;margin:34px auto 40px;border:1px solid #dae5e9;border-radius:14px;overflow:hidden;background:#f5f8fa;box-shadow:0 10px 28px -17px rgba(24,47,60,.28);box-sizing:border-box\"><div class=\"wh-figure-media\" style=\"display:block;background:#eef3f5;line-height:0\"><img loading=\"lazy\" width=\"800\" height=\"534\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/netzwerkanschluss-connect-zeit-a0f7489e-detail1-0b86997004-1024x683.webp\" class=\"wp-image-22362\" alt=\"AI-generated stock image of an Ethernet cable plugged into a network device, shown in a close-up side view\" decoding=\"async\" srcset=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/netzwerkanschluss-connect-zeit-a0f7489e-detail1-0b86997004-1024x683.webp 1024w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/netzwerkanschluss-connect-zeit-a0f7489e-detail1-0b86997004-300x200.webp 300w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/netzwerkanschluss-connect-zeit-a0f7489e-detail1-0b86997004-768x512.webp 768w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/netzwerkanschluss-connect-zeit-a0f7489e-detail1-0b86997004-18x12.webp 18w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/netzwerkanschluss-connect-zeit-a0f7489e-detail1-0b86997004.webp 1536w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" ><\/div><figcaption class=\"wh-caption\" id=\"wh-caption-detail1\" style=\"display:block;margin:0;padding:12px 18px 15px;border-top:1px solid #dce5e9;color:#506575;background:#f5f8fa;font-size:14px;line-height:1.55;text-align:start\">AI-generated illustrative image: The network path to the destination affects the time it takes to establish a connection.<\/figcaption><\/figure><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">TLS involves more than just computation time: Messages are exchanged between the client and the remote end for authentication and negotiation. A resumed TLS session can shorten the time required for a new handshake compared to a full handshake. However, it is not the same as using an existing connection without establishing a new one.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The article on explains how to resume a session and what operating conditions play a role in this process. <a href=\"https:\/\/webhosting.de\/en\/tls-handshake-resumption-session-caching-https-performance-optimizer\/\">TLS Handshake Resumption and Session Caching<\/a>. For the diagnosis, the first thing that matters is whether the requests in question even had the same connection state: A short response time alone does not necessarily indicate a fast TLS infrastructure.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"antwort-download\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"antwort-download\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Waiting for a response and the download<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">After building and sending the request, Chrome displays the section <strong style=\"font-weight:700;color:inherit\">Waiting (TTFB)<\/strong> until the first response byte. According to the DevTools documentation, it includes a round-trip network delay and the time the server takes to prepare the response. A high value is therefore neither pure network time nor a direct measurement of application runtime. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Suppose that, for a document request, the \"Waiting\" phase is particularly long, while the subsequent \"Receiving\" phase is short. In that case, the peak occurs before the first byte arrives. The waterfall chart alone does not reveal whether a long round-trip time, processing at the remote end, or both are responsible.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In particular, TTFB does not indicate the duration of a single database query. Preparing the response may involve multiple processing steps; furthermore, the network component is part of the observed wait time. Available server timings or logs can help narrow down the server-side components, but they must correspond to the request and time period under investigation. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The first byte is followed by the <strong style=\"font-weight:700;color:inherit\">Receiving the response body<\/strong>. A long download time may be due to factors such as the amount of data being transferred or the connection conditions. Chrome also notes that a browser that is under heavy load may not be able to read data immediately; therefore, this section is not an exclusive measure of connection speed. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">When troubleshooting, you should consider both sections separately: A smaller file can primarily affect reception, but it doesn't automatically resolve a long wait before the first byte. Conversely, a faster response time doesn't necessarily shorten the subsequent download. Only a comparable repeat request will show whether a change helps.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"waterfall-praxis\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"waterfall-praxis\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Reading the Website Waterfall<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Open the Developer Tools in Chrome and go to the Network panel. Check to see if recording is active, and then reload the page. Select the document request and open its \u201eTiming\u201c section: There you\u2019ll see the time intervals that Chrome reports for this specific request. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The <strong style=\"font-weight:700;color:inherit\">Waterfall View<\/strong> It also organizes the requests on a shared timeline. For example, if one stylesheet starts loading while another request is still in progress, their durations overlap. This helps you identify which resources start early and which are requested later; however, the timeline alone does not explain every dependency.<\/p>\n<figure class=\"wp-block-image size-large wh-figure\" aria-describedby=\"wh-caption-detail2\" style=\"display:block;float:none;clear:both;width:100%;max-width:760px;margin:34px auto 40px;border:1px solid #dae5e9;border-radius:14px;overflow:hidden;background:#f5f8fa;box-shadow:0 10px 28px -17px rgba(24,47,60,.28);box-sizing:border-box\"><div class=\"wh-figure-media\" style=\"display:block;background:#eef3f5;line-height:0\"><img loading=\"lazy\" width=\"800\" height=\"534\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/waterfall-parallele-requests-a0f7489e-detail2-e15d38491a-1024x683.webp\" class=\"wp-image-22363\" alt=\"AI-generated illustration of staggered and overlapping shapes as a metaphor for parallel resource access\" decoding=\"async\" srcset=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/waterfall-parallele-requests-a0f7489e-detail2-e15d38491a-1024x683.webp 1024w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/waterfall-parallele-requests-a0f7489e-detail2-e15d38491a-300x200.webp 300w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/waterfall-parallele-requests-a0f7489e-detail2-e15d38491a-768x512.webp 768w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/waterfall-parallele-requests-a0f7489e-detail2-e15d38491a-18x12.webp 18w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/11\/waterfall-parallele-requests-a0f7489e-detail2-e15d38491a.webp 1536w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" ><\/div><figcaption class=\"wh-caption\" id=\"wh-caption-detail2\" style=\"display:block;margin:0;padding:12px 18px 15px;border-top:1px solid #dce5e9;color:#506575;background:#f5f8fa;font-size:14px;line-height:1.55;text-align:start\">AI-generated illustration: Overlapping requests cannot be combined into the page load time by adding their durations together.<\/figcaption><\/figure><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Pay particular attention to how the connection is represented: Chrome includes the SSL negotiation in the total \u201eInitial connection\u201c time. Therefore, you must not add a separately displayed SSL time to the total initial connection time. \u201eQueueing\u201c and \u201eStalled,\u201c on the other hand, can occur before data is sent and do not automatically represent DNS or server wait times. <\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"Organizing Timing Sections in the Browser\" style=\"width:100%;max-width:100%;overflow-x:auto;margin:28px 0;border:1px solid #dce5e9;border-radius:14px;background:#fff;box-shadow:0 10px 28px -16px rgba(24,47,60,.32);box-sizing:border-box\"><table style=\"width:100%;min-width:580px;border-collapse:separate;border-spacing:0;border:0;margin:0;font-size:15px;line-height:1.6;background:#fff\"><caption style=\"padding:20px;text-align:start;font-size:17px;line-height:1.5;font-weight:700;color:#173246;background:#fff\">Organizing Timing Sections in the Browser<\/caption><thead><tr><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Section<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Observation<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Possible Factors<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Detection Limit<\/th><\/tr><\/thead><tbody><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">DNS Lookup<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Time for name resolution from the client's perspective<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Caches and Resolver Path<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Not an isolated measurement from the authoritative DNS server<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">TCP Connect<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Establishing a New TCP Connection<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Latency to the endpoint, repetitions<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">The endpoint can be a CDN edge<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">TLS\/SSL<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Establishing a Secure Connection<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Message Transit Times and Handshake Status<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Do not add this to the total initial connection<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Queued\/Stalled<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Waiting before the actual retrieval<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Priority, Connection Limits, Cache Operations<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">No Evidence of Slow DNA<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Waiting (TTFB)<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Wait until the first response byte is received<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Networking and Preparing Responses<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Not just database or server time<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Download Content<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Receiving the response body<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Browser Transmission and Reading Behavior<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Not just a measure of bandwidth<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">HTTP\/3<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Establishing a Connection via QUIC<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">UDP Reachability and Protocol Selection<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">No separate TCP handshake<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">When making a diagnosis, don't just look at the longest bar; also consider its position: Is it delaying a required resource, or is it running alongside other requests? Repeat the test under documented conditions before drawing a general conclusion from a single waterfall chart.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"curl-zeitpunkte\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"curl-zeitpunkte\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Calculating curl Timestamps Correctly<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">With <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">curl<\/code> allows you to examine a single request in detail. The following command is intended for a terminal with curl installed. It actually retrieves the sample page via HTTPS, requests HTTP\/1.1, does not follow any redirects, and discards the response body; certificate validation remains active. <\/p>\n<div class=\"wh-code-window\" data-wh-code style=\"margin:28px 0 34px;border:1px solid #2c4656;border-radius:12px;overflow:hidden;background:#132a3b;box-shadow:0 9px 25px -13px rgba(15,35,55,.2)\"><div class=\"wh-code-toolbar\" style=\"display:flex;flex-wrap:wrap;align-items:center;justify-content:space-between;gap:10px;padding:11px 16px;background:#223e50;color:#edf5fa;font-size:13px;line-height:1.5;font-weight:600\"><span>Terminal<\/span><button type=\"button\" class=\"wh-code-copy\" data-wh-copy hidden style=\"padding:6px 11px;border:1px solid #7893a1;border-radius:6px;background:transparent;color:#fff;font-size:12px;line-height:1.5;font-weight:600;cursor:pointer\">Copy code<\/button><span class=\"wh-copy-status\" aria-live=\"polite\"><\/span><span data-wh-copy-success hidden>Copied<\/span><span data-wh-copy-fallback hidden>Code highlighted\u2014please copy<\/span><\/div><pre class=\"wh-code\" data-no-translation translate=\"no\" style=\"display:block;margin:0;padding:20px;max-width:100%;overflow-x:auto;color:#edf5fa;background:#132a3b;font:14px\/1.75 ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;white-space:pre;direction:ltr;text-align:left\"><code class=\"language-bash\" style=\"font:inherit;color:inherit;background:transparent;padding:0;border:0;white-space:inherit\">curl --http1.1 -sS -o \/dev\/null -w &#039;DNS: %{time_namelookup}s\\nConnect: %{time_connect}s\\nTLS: %{time_appconnect}s\\nErstes Byte: %{time_starttransfer}s\\nGesamt: %{time_total}s\\nHTTP: %{http_code}\\n&#039; https:\/\/example.com\/<\/code><\/pre><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The values printed are <strong style=\"font-weight:700;color:inherit\">cumulative dates<\/strong> in seconds from the start of the transfer; these are not fixed individual durations. The value labeled \u201eTLS\u201c therefore refers to the point in time after the TLS handshake is complete, not exclusively to its duration. If you add these values together, you\u2019ll be counting previous segments multiple times. <\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"curl timestamps during a direct HTTPS reconnection\" style=\"width:100%;max-width:100%;overflow-x:auto;margin:28px 0;border:1px solid #dce5e9;border-radius:14px;background:#fff;box-shadow:0 10px 28px -16px rgba(24,47,60,.32);box-sizing:border-box\"><table style=\"width:100%;min-width:580px;border-collapse:separate;border-spacing:0;border:0;margin:0;font-size:15px;line-height:1.6;background:#fff\"><caption style=\"padding:20px;text-align:start;font-size:17px;line-height:1.5;font-weight:700;color:#173246;background:#fff\">curl timestamps during a direct HTTPS reconnection<\/caption><thead><tr><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Section Sought<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Calculation<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Classification<\/th><\/tr><\/thead><tbody><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">DNS<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">time_name_lookup<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Time remaining until the name resolution is complete<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">TCP<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">time_connect \u2212 time_namelookup<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Approximate time between termination and establishment of a TCP connection<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">TLS<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">time_appconnect \u2212 time_connect<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Approximate time for the subsequent TLS connection establishment<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">After TLS until the first byte<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">time_starttransfer \u2212 time_appconnect<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Includes request transmission, networking, and response preparation<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">These differences roughly correspond to a successful direct HTTPS request using a new TCP connection, without a proxy and without redirection. Check the HTTP status and any error messages before interpreting the numbers. Although a redirection response is returned here, its destination is not automatically retrieved.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">With a proxy, you can <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">time_connect<\/code> Describe the flow to the proxy rather than to the destination server. Redirects, reused connections, and QUIC also require a different classification. In particular, the time elapsed until the first byte after TLS is not just the server's processing time: the request must be transmitted, and the response must reach the client. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A terminal request does not replace a full page load in a browser. It is useful for repeatedly comparing the same endpoint under conditions that are as consistent as possible; however, the output alone does not reveal the cause of a delay or provide information about all visitor locations.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"verbindungen-protokolle\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"verbindungen-protokolle\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Detecting Reuse and HTTP\/3<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A fast follow-up request may not show its own DNS, Connect, or TLS segments in the timing. One possible explanation is <strong style=\"font-weight:700;color:inherit\">Connection Reuse<\/strong>: The browser uses a connection that has already been established. The missing sections do not mean that the initial connection was free or that the tool is measuring incorrectly. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">With HTTP\/2, multiple requests can travel over the same connection. Therefore, a document and a stylesheet do not each have to go through their own TCP and TLS handshakes. Look for the earlier connection establishment in the waterfall chart and examine the relationship between the requests, rather than expecting the same phases for every file.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The shared timeline is also important for the total duration: parallel requests overlap. Therefore, adding up their individual durations does not equal the page load time. A long download may run simultaneously with other resources; what matters is when the respective resources are actually available.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">At <strong style=\"font-weight:700;color:inherit\">HTTP\/3<\/strong> The architecture changes: HTTP\/3 uses QUIC over UDP instead of TCP. QUIC combines the transport layer with a TLS-based cryptographic handshake. Therefore, the sequence \u201efirst TCP, then TLS\u201c is not an appropriate template in this case.   <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Check the network details to see which protocol is actually being used before comparing connection times. If UDP isn't working on a network path, a client may fall back to a TCP-based version of HTTP. As a result, two requests to the same website may show different connection paths even though the content hasn't changed. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">To ensure a fair comparison, also note whether this is an initial request or a subsequent request. An HTTP\/3 request with an existing connection and a new HTTP\/2 connection establishment address different issues. First, compare similar scenarios, and then specifically examine the difference that connection reuse makes.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"messung-vergleichen\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"messung-vergleichen\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Comparing Measurements in a Reproducible Manner<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A single time measurement is just a snapshot. Repeat the same test and note the location and network you\u2019re using to take the measurement. Also document the browser or curl version, the target address, the protocol used, and any proxy that may be in use. This will help you determine whether the testing conditions have changed or if a suspicious value is recurring.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Also make a note of the <strong style=\"font-weight:700;color:inherit\">Cache and Connection Status<\/strong>: Was it an initial request or a subsequent request, and was an existing connection used? The option to disable the cache in the Network panel applies to the browser cache. It does not guarantee that DNS caches, the state of the operating system, or TLS session information will be completely cleared. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">First, compare repeated requests for the same document under conditions that are as similar as possible. Next, you can deliberately change a variable, such as the network or location. If the connect time changes as a result, this provides a starting point for investigating the network path to the actual endpoint being accessed, but it is not yet proof of a specific cause.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A retrieval with <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">curl<\/code> It is suitable for the controlled comparison of individual URLs. However, unlike a browser, it does not automatically load the entire page along with its dependent resources, and it does not necessarily reflect the same cache, proxy, or connection status. If the times differ, check these differences first instead of assuming the tool is faulty. <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"resource-timing\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"resource-timing\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Resource Timing and Backend Telemetry<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The <strong style=\"font-weight:700;color:inherit\">Resource Timing API<\/strong> Provides timestamps for individual resources in the browser. Differences can be calculated from appropriate time points for automated analysis. Unlike with a single terminal request, the data comes from the context of the page; however, on its own, it does not explain what happened internally on the server. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For resources from a different origin, detailed timing values cannot be obtained without a matching <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">Timing-Allow-Origin<\/code>-The \"Response\" header must be set to zero. A zero does not necessarily mean that establishing the connection actually took no time. Therefore, first check whether the resource allows access to the relevant timing information. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Cache hits and reused connections also affect the interpretation: Not every resource request triggers a new DNS lookup or connection establishment. Therefore, do not blindly compare API timestamps with sections in DevTools that appear to have the same name. What matters in each case is which operation is being recorded and whether it actually took place for this request.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">If the TTFB is unusually high, available server timings or logs can supplement the client\u2019s perspective. They can help narrow down the cause of the response delay; however, they do not fully capture the network components along the path to the browser. For a correlation to be valid, the time period and the requested resource must match, though this does not automatically imply a single cause.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">When collecting data for analysis, you should only log the data that is necessary for the diagnosis. URL parameters may contain personally identifiable or confidential information. For example, limit your analysis to controlled test pages and selected time intervals, and verify which information is actually being transmitted before saving it.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"diagnose-optimierung\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"diagnose-optimierung\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Identify and Resolve Bottlenecks<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Start with the phase that stands out consistently under comparable conditions. If the DNS value is high, examine the <strong style=\"font-weight:700;color:inherit\">Resolver Path<\/strong> and the client's probable cache state. A short response time during a subsequent request may be due to the cache; it does not prove that name resolution is fast for all locations.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">If the Connect setup is particularly slow, compare measurements from different locations and check the target endpoint. With a CDN, this may be an edge server, not the origin server. Network latency and potential retries affect the connection establishment; the waterfall chart alone does not show which section of the network path is responsible. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">When high <strong style=\"font-weight:700;color:inherit\">TTFB<\/strong> Examine both the network portion and the response preparation. Additional server timings or logs can provide insights into backend processing. The \u201eWaiting\u201c section in DevTools covers a round-trip over the network and the preparation of the response; therefore, it is neither pure server time nor a direct measurement of a database query. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Depending on the findings, options may include fewer distinct origins, the reuse of connections, or a closer edge endpoint. Targeted <a href=\"https:\/\/webhosting.de\/en\/dns-prefetching-preconnect-optimize-loading-time-performance-boost\/\">DNS Prefetching and Preconnect<\/a> may prioritize the allocation of resources for important tasks. However, such indications do not in and of themselves prove a benefit: Prepared connections also consume resources and may be unnecessary.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">After making a change, compare the same processes again\u2014ideally with documented location, log, and cache status. Make sure that not only an isolated phase but also the relevant page view improves. Repeat the comparison before rolling out a change on a large scale; a single waterfall chart proves neither the cause nor the lasting benefit.<\/p>\n<\/section><section class=\"wh-sources\" style=\"margin:40px 0 0;padding:24px 0 0;border-top:1px solid #dce5e9;color:#596b7b;font-size:14px;line-height:1.65\"><h2 style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Sources and Current State of Knowledge<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Status of the research: <time datetime=\"2026-11-13\">2026-11-13<\/time><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Research and source status: November 13, 2026. Source identifiers correspond to the provided source register; no chart is included due to a lack of reliable measurement data.<\/p><div class=\"wh-source-urls\"><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/developer.chrome.com\/docs\/devtools\/network\/reference<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/curl.se\/docs\/manpage.html?previewMode=true<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/www.rfc-editor.org\/rfc\/rfc9114.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/www.rfc-editor.org\/rfc\/rfc9000.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/www.rfc-editor.org\/rfc\/rfc9001.html<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/API\/PerformanceResourceTiming\/connectStart<\/span><\/p><\/div><\/section><\/div>","protected":false},"excerpt":{"rendered":"<p>Examine DNS, connection establishment, TLS, response, and download separately: Here's how to read the website waterfall chart and interpret curl timestamps under appropriate testing conditions.<\/p>","protected":false},"author":1,"featured_media":22361,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[674],"tags":[],"class_list":["post-22359","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web_hosting"],"acf":[],"_links":{"self":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/22359","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/comments?post=22359"}],"version-history":[{"count":2,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/22359\/revisions"}],"predecessor-version":[{"id":22364,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/22359\/revisions\/22364"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media\/22361"}],"wp:attachment":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media?parent=22359"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/categories?post=22359"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/tags?post=22359"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}