Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallA slow web application is a symptom, not a diagnosis. First separate DNS lookup, TCP connection setup, TLS negotiation, time to first byte (TTFB) and total transfer time; then compare cache and origin behavior and instrument backend work. That sequence helps distinguish a network delay from slow application or database processing—and points to a fix that addresses the measured cause.
Start by separating request timings
A page-load score or one total-duration number cannot tell you which part of the request is slow. Measure a representative URL during normal traffic and at high load, and compare results from relevant user locations if geography may matter. For a basic HTTPS request, curl can report the major timing milestones:
As an Amazon Associate I earn from qualifying purchases.
curl -sS -o /dev/null -w 'DNS lookup: %{time_namelookup}snTCP connected: %{time_connect}snTLS complete: %{time_appconnect}snFirst byte: %{time_starttransfer}snTotal: %{time_total}sn' https://example.com/Replace https://example.com/ with the URL you are investigating. These are cumulative milestones from the start of the request, not five independent durations: for an ordinary fresh HTTPS connection, estimate TCP setup by subtracting DNS time from TCP-connected time, TLS setup by subtracting TCP-connected time from TLS-complete time, and time from TLS completion to the first byte by subtracting TLS-complete time from first-byte time. Total time includes receiving the response body. Redirects, proxies, reused connections and the client’s network can change what a measurement represents, so use the same setup when comparing requests and do not treat one curl result as a complete browser page-load diagnosis.
| Milestone | What it helps locate | What to check next |
|---|---|---|
| DNS lookup | Name resolution before the connection is established. | Compare repeated requests and the affected networks or locations. |
| TCP connected | Time to establish the transport connection, including the preceding DNS phase in this cumulative value. | Look at connection reuse, network path and distance to the endpoint. |
| TLS complete | Connection setup through TLS negotiation, including earlier phases. | Compare the incremental TLS time and check whether connections are being reopened. |
| First byte (TTFB) | Time until the first response byte, including earlier request phases and time waiting for a response. | Separate network setup from edge, origin and backend processing. |
| Total | Time until the response body has been received. | If TTFB is acceptable but total time is long, inspect response size and transfer conditions. |
TTFB is not a synonym for application execution time: it can include DNS, connection setup, network travel, cache behavior and server-side work. A high TTFB alone does not identify which one is responsible.
#1 Best Overall
- GIGABIT ETHERNET PORTS: Features 5 x 1.0Gbps Ethernet ports for high-speed connectivity. Auto-negotiating ports detect the optimal speed for connected devices and work with existing Cat5e or Cat6 Ethernet cables.
- PLUG-AND-PLAY UNMANAGED NETWORK SWITCH: Simple plug-and-play setup with no software to install or configuration required.
- FLEXIBLE MOUNTING OPTIONS: Compact metal design supports desktop or wall-mount placement for versatile installation.
- SILENT & ENERGY-EFFICIENT OPERATION: Fanless design ensures silent performance, while IEEE 802.3az Energy Efficient Ethernet reduces power consumption without compromising high-speed network performance.
- REGIONAL COMPATIBILITY: Made for use in U.S. & CA only
1. DNS resolution can delay the start of a request
DNS lookup is its own request phase. If it is slow, the browser may wait before it can connect, even when the application responds quickly once reached. Compare lookup time across repeated requests and affected networks before attributing initial delay to the origin server. Check whether the delay is limited to first requests or appears consistently; do not infer a backend problem from DNS time alone.
2. Distance between users and the origin adds round-trip time
Requests that must travel from a user to a distant origin incur more network round trips than requests served nearby. A CDN can reduce this penalty when it serves a cacheable response from a nearby edge location. A cache miss still needs the origin, and dynamic requests that cannot be served from cache remain dependent on the route to that origin. Compare performance by geography and by cache status rather than assuming that a CDN removes origin distance from every request.
Rank #2
- 𝗢𝗻𝗲 𝗦𝘄𝗶𝘁𝗰𝗵 𝗠𝗮𝗱𝗲 𝘁𝗼 𝗘𝘅𝗽𝗮𝗻𝗱 𝗡𝗲𝘁𝘄𝗼𝗿𝗸: 5× 10/100/1000Mbps RJ45 Ports supporting Auto Negotiation and Auto MDI/MDIX.
- 𝗚𝗶𝗴𝗮𝗯𝗶𝘁 𝘁𝗵𝗮𝘁 𝗦𝗮𝘃𝗲𝘀 𝗘𝗻𝗲𝗿𝗴𝘆: Latest innovative energy-efficient technology greatly expands your network capacity with much less power consumption and helps save money.
- 𝗥𝗲𝗹𝗶𝗮𝗯𝗹𝗲 𝗮𝗻𝗱 𝗤𝘂𝗶𝗲𝘁: IEEE 802.3X flow control provides reliable data transfer and Fanless design ensures quiet operation.
- 𝗣𝗹𝘂𝗴 𝗮𝗻𝗱 𝗣𝗹𝗮𝘆: Easy setup with no software installation or configuration needed.
- 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗙𝗲𝗮𝘁𝘂𝗿𝗲𝘀: Prioritize your traffic and guarantee high quality of video or voice data transmission with Port-based 802.1p/DSCP QoS and IGMP Snooping.
3. Routing and congestion affect the path to the server
The route a request takes—and congestion along it—can add latency even when the application and CDN configuration have not changed. This is especially relevant when uncached requests are slow: investigate the path between the edge and origin, as well as origin distance, rather than treating every delay as application processing. Compare measurements from different locations and times to see whether the problem follows a route, a region or the backend.
4. TCP connection setup costs time on a new connection
A new TCP connection must be established before data can be exchanged. That setup is visible in connection timing and can matter more when a page or client makes several requests without reusing connections. Compare the initial request with later requests, and check whether the client, proxy and server keep eligible connections open. Connection reuse helps avoid repeated setup; it will not make a slow database query faster.
Rank #3
- GIGABIT ETHERNET PORTS: Features 8 x 1.0Gbps Ethernet ports for high-speed connectivity. Auto-negotiating ports detect the optimal speed for connected devices and work with existing Cat5e or Cat6 Ethernet cables.
- PLUG-AND-PLAY UNMANAGED NETWORK SWITCH: Simple plug-and-play setup with no software to install or configuration required.
- FLEXIBLE MOUNTING OPTIONS: Compact metal design supports desktop or wall-mount placement for versatile installation.
- SILENT & ENERGY-EFFICIENT OPERATION: Fanless design ensures silent performance, while IEEE 802.3az Energy Efficient Ethernet reduces power consumption without compromising high-speed network performance.
- REGIONAL COMPATIBILITY: Made for use in U.S. & CA only
5. TLS negotiation is another connection phase
HTTPS requests also need TLS negotiation. Measure the interval between TCP connection and TLS completion rather than folding both into one vague “connect” number. Reopening TLS connections repeats that work; persistent connections can avoid it on subsequent requests. Modern TLS, including TLS 1.3, is designed to reduce negotiation time, but the actual benefit depends on the connection pattern and path. Check reuse and protocol behavior before changing application capacity to address a delay that occurs before the request reaches it.
6. Too many hostnames or poor connection reuse multiply setup work
When a page requests resources from many hostnames, clients may need additional DNS lookups and connections. If connections are not reused where appropriate, TCP and TLS setup can recur. Review the hostnames involved and whether the request path supports reuse or connection coalescing; consolidate origins only when it makes sense for the application’s security and operational boundaries.
Rank #4
- 【One Switch Made to Expand Network】Features 5 RJ45 ports with 10/100/1000Mbps speeds, supporting Auto-Negotiation and Auto MDI/MDIX for hassle-free setup. Ideal for expanding your network, with 1 uplink (input) port and 4 output ports to split your Ethernet connection to multiple devices.
- 【Gigabit that Saves Energy】Latest innovative energy-efficient technology greatly expands your network capacity with much less power consumption and helps save money
- 【Reliable and Quiet】IEEE 802.3X flow control provides reliable data transfer and Fanless design ensures quiet operation
- 【Plug and Play】Easy setup with no software installation or configuration needed
- 【Ethernet Splitter】Connect to your router or modem for additional wired connections (laptop, gaming console, printer, etc)
Cloudflare reported in 2023 that its modeling and analysis of ORIGIN Frame connection coalescing indicated a potential reduction of more than 60% at the median in browser DNS queries and TLS connections. That figure describes the modeled effect of that mechanism, not a universal reduction in latency or a result every site should expect.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
7. Low cache hit ratios send more work to the origin
A CDN cache hit serves an eligible response from cache instead of forwarding that request to the origin. A higher hit ratio for suitable content can reduce origin requests and load; a miss still depends on the origin path. Compare hit and miss behavior, cache policy and origin response times to establish whether caching could address the observed delay.
Best Value
- 𝗘𝗶𝗴𝗵𝘁 𝟮.𝟱 𝗚𝗯𝗽𝘀 𝗣𝗼𝗿𝘁𝘀 𝗳𝗼𝗿 𝗦𝘂𝗽𝗲𝗿-𝗙𝗮𝘀𝘁 𝗖𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻𝘀: 8× 2.5-Gigabit ports unlock the highest performance of your Multi-Gig bandwidth and devices, and provide up to 40 Gbps of switching capacity.
- 𝗔𝘂𝘁𝗼-𝗡𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗶𝗼𝗻: Auto-negotiation intelligently senses the link speeds and adjusts between 3-speeds (100Mb/1G/2.5G) for compatibility and optimal performance for all your devices, including 2.5G WiFi 6 AP, 2.5G NAS, 2.5G PCIe Adapter, 2.5G Server, gaming computer, 4K video, and more.
- 𝗜𝗱𝗲𝗮𝗹 𝗳𝗼𝗿 𝗩𝗮𝗿𝗶𝗼𝘂𝘀 𝗦𝗰𝗲𝗻𝗮𝗿𝗶𝗼𝘀: Built for LAN parties, home entertainment, small and home offices, and instant transfer for workstations.
- 𝗛𝗮𝘀𝘀𝗹𝗲-𝗙𝗿𝗲𝗲 𝗖𝗮𝗯𝗹𝗶𝗻𝗴: Instantly upgrade to 2.5 Gbps without the need to upgrade to Cat6 wiring, reducing wiring costs and hassle. *
- 𝗦𝗶𝗹𝗲𝗻𝘁 𝗢𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻: Industry-leading fanless design ensures silent operation, ideal for any home or business.
Cache only responses that are safe to share. Private, personalized or user-specific responses should not be made publicly reusable merely to improve a hit ratio. For suitable content, review cache lifetime and variation rules so that the edge can reuse responses without serving one user another user’s data. An additional cache layer such as Origin Shield can consolidate requests for the same object on misses and reduce simultaneous origin requests, but it does not make uncacheable responses cacheable.
8. An overloaded or undersized origin may respond slowly
High origin response time can point to resource pressure, but confirm it with origin analytics and measurements under representative and high load. If CPU or memory is constrained, adding capacity may help; if the bottleneck lies elsewhere, scaling those resources may add cost without fixing the delay. Check the origin’s resource use and request volume alongside its response times before changing instance size or hosting capacity.
9. Slow database queries and backend calls extend TTFB
Database queries and API calls can consume the time between receiving a request and producing its response. Instrument those operations and compare their durations with the request’s TTFB; tune queries for the request volume and identify slow upstream calls. A gateway or CDN timeout set higher may allow a slow request to wait longer, but it does not make the database or API return sooner.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →10. Application logic and middleware can add processing time
Application code, middleware, edge workers and other intermediary processing can all add time. Use server-side timing to locate the slow segment, and separate upstream connection time from origin response time when those measurements are available. Isolate a slow route or processing step before changing infrastructure: replacing a server or moving a CDN setting will not necessarily fix work performed in application logic.
Quick Recap
Use the evidence to choose the next fix
- Measure representative requests. Record DNS, connection, TLS, TTFB and total time under normal and high load; compare like-for-like URLs and locations.
- Verify the path. Confirm that the request actually passes through the CDN or proxy whose behavior you are analyzing. For a Cloudflare path, check for its response header before attributing the request to that service.
- Compare cache and origin data. Examine hits, misses, origin response times and geography. Determine whether slow responses are served at the edge, forwarded to origin or limited to particular locations.
- Instrument server-side work. Measure database queries, API calls, application processing and edge work. Where available, distinguish upstream connection timing from origin response time.
- Apply the fix to the measured phase. Improve safe cache coverage for eligible responses, connection reuse for repeated requests, query or application performance for backend delays, routing or origin placement for path-related delays, and capacity when resource measurements show pressure.
- Adjust timeouts last. After addressing performance and latency issues, set gateway or CDN timeouts to suit the required behavior. A longer timeout alone changes how long a request is allowed to wait, not how quickly it completes.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
