Network latency is the delay between a visitor’s browser requesting a resource and receiving a response. It is usually discussed as round-trip time (RTT), not as the amount of data a connection can carry. A site can have abundant bandwidth yet feel slow when the visitor is far from the server, connection setup takes several round trips, the origin is busy, or the page triggers dozens of requests.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
Reducing latency means finding which part of the request is waiting—DNS, connection setup, routing, origin processing, transfer, or browser rendering—and then removing avoidable trips. Edge caching, geographically appropriate hosting, fewer requests, smaller assets, and faster application responses address different parts of that delay.
As an Amazon Associate I earn from qualifying purchases.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteLatency is delay, not bandwidth
Bandwidth is transfer capacity: how much data a connection can move per second. Latency is the time before and during delivery. A high-bandwidth connection can download a large file quickly once data starts flowing, but a high-latency path still makes every new request wait.
MDN defines latency as “the time it takes for a packet of data to travel from source to a destination.” For websites, engineers commonly observe round-trip time because a browser sends a request and waits for the server’s response. The first request to an origin normally includes several setup stages; later requests may reuse an established connection.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
This distinction explains why a website can feel slow even when a visitor’s internet speed test reports hundreds of megabits per second. If the page requires 40 separate CSS, JavaScript, image, font, analytics, and API requests, each request creates another opportunity for distance, queuing, setup, or server wait to show up. Browser parsing, layout, and painting then add non-network time after bytes arrive.
What happens during a web request
A browser waterfall separates the delay into stages. Knowing what each stage means prevents you from treating every slow page as a bandwidth problem.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →| Stage | What happens | Typical latency risk |
|---|---|---|
| DNS lookup | The browser resolves the hostname to an IP address. | Slow or uncached DNS, distant resolvers, or a new hostname can delay the first request. |
| TCP connection | The browser establishes a TCP connection with the server. | A round trip is required before application data can be sent. AWS cites TCP handshake overhead of 10%–30% of request-serving latency in the example discussed in its static-site whitepaper; that is an example, not a universal percentage. |
| TLS negotiation | HTTPS keys and certificates are negotiated. | Another setup exchange can be significant on a long-distance or lossy path. |
| Request transmission | The browser sends the HTTP request and headers. | Congestion, packet loss, and inefficient routing can force retransmissions or extra waiting. |
| Origin processing | A cache, web server, application, database, or API creates the response. | Slow queries, cold starts, overloaded hosts, and application code increase time to first byte (TTFB). |
| Response transfer | Response bytes travel back to the browser. | Distance, congestion, packet loss, and a large payload increase receiving time. |
| Browser work | The browser parses HTML, executes scripts, calculates layout, and paints pixels. | Render-blocking CSS or JavaScript and heavy third-party code can make a page appear slow even when network timing is acceptable. |
Persistent connections allow later requests to reuse an existing connection, avoiding some DNS, TCP, and TLS work. They reduce setup overhead but cannot remove propagation delay or a slow origin.
Why a website has high latency
Geographic distance and propagation
Packets must physically travel between the visitor and the server. Cloudflare identifies distance as a principal cause. A 2019 Cloudflare load-balancing whitepaper estimates 0.82 milliseconds per 100 miles; treat that as a vendor estimate rather than a universal constant, because real routes are not straight lines and network equipment adds processing and queuing time.
Distance affects both the initial connection and every trip that reaches the origin. A visitor in another continent may therefore wait noticeably longer for a dynamic page, even with a fast local access network.
Connection setup
A first visit commonly pays for DNS, TCP, and TLS before useful application bytes arrive. A page that opens several hostnames can repeat that work. Reusing connections, reducing hostnames, and serving related resources through a consistent endpoint can limit setup trips.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Congestion, loss, and routing
Routers process packets, queues form when links are busy, and packets can be lost. Loss triggers retransmission; an inefficient route may send traffic through a distant or congested exchange. These conditions vary by ISP, time of day, and geography, so one test location cannot represent every visitor.
Origin processing and TTFB
When a request cannot be answered from cache, the origin must run application code, query data stores, call other services, and generate a response. Database contention, cold starts, overloaded servers, and slow dependencies all increase TTFB. A nearby server with poor processing time can be slower than a more distant but efficient one.
Request count and asset cost
Every additional request can incur scheduling, connection, and server work. Large images, uncompressed fonts, render-blocking stylesheets, parser-blocking scripts, and unnecessary third-party calls add transfer or execution time. Combining files indiscriminately is not always best, but eliminating requests that provide no user value is nearly always beneficial.
Measure each part of latency before changing infrastructure
Inspect a real page in browser DevTools
- Open the page in a current browser and choose Developer Tools → Network.
- Enable the timing or waterfall view and reload with the cache disabled for a first-load measurement. Record DNS, connection, SSL, request, waiting (TTFB), content download, and total timings for the document and key assets.
- Repeat with the browser cache enabled. The difference shows how much repeat visits benefit from reuse.
- Filter by domain and type to identify third-party hosts, APIs, fonts, images, and scripts that create extra connections or long waits.
- Use the browser’s network throttling controls to model high-latency and low-quality connections. A fast office connection can hide problems experienced on mobile or rural networks.
Resource Timing entries expose DNS lookup, TCP connection, TLS connection, request, response, and transfer timestamps. Compare the document’s TTFB with static assets: a high document TTFB points toward origin or routing work, while a fast document with slow images points toward payload, caching, or asset delivery.
Free tools Windows power users keep installed
One-click scans. No signup required.
Measure a URL from the command line
Cloudflare documents this curl pattern for separating major timings:
curl -w "nnDNS Lookup: %{time_namelookup}snTCP Connect: %{time_connect}snTLS Handshake: %{time_appconnect}snTime to First Byte: %{time_starttransfer}snTotal Time: %{time_total}sn" -o /dev/null -s https://www.example.com/slow-asset.jpgRun it several times, from more than one network or region, and against both a cacheable asset and a dynamic page. The command reports elapsed times for that particular route and moment; it is not a global score. Check response headers at the same time. A header such as cf-cache-status can show whether a Cloudflare-served response was a cache hit, miss, or bypass, when that header is present.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
Use synthetic tests and real-user monitoring together
A synthetic test gives repeatable conditions from a chosen location. Real-user monitoring (RUM) captures the distribution visitors actually experience across devices, ISPs, routes, and countries. Track median (p50), p75, and p95 TTFB and page-load timings, separated by geography and connection type. Also record cache-hit ratio, error rate, and resource-level timings. A single average can hide a severe problem for a smaller but important region.
Reduce latency in the order that usually produces the most reliable gains
1. Confirm the bottleneck
Classify the delay before buying capacity or changing providers. If DNS dominates, investigate DNS hosting and resolver behavior. If TCP or TLS dominates, reduce new connections and hostnames. If TTFB dominates, profile the origin and its dependencies. If receiving time dominates, optimize payloads or delivery. If network timings are acceptable but the page is still visually slow, profile JavaScript, CSS, layout, and rendering.
2. Cache safe content at the edge
Edge caching stores a response at a location near visitors. A cache hit can answer without a trip to the origin. Cloudflare describes cached responses falling from hundreds of milliseconds to a few milliseconds in suitable cases; that is a vendor description, not a guaranteed result for every site.
Start with content that is immutable or can tolerate brief staleness:
- Versioned JavaScript, CSS, fonts, and images.
- Public downloads and other identical responses for many visitors.
- HTML pages whose freshness and personalization rules are explicit.
Give versioned assets long freshness lifetimes. When a file changes, change its filename or version identifier so old copies can remain safely cached. For HTML and API responses, define Cache-Control directives, vary only on headers that truly change the response, and establish an invalidation plan. Never cache private account data or personalized responses as public content. Monitor hit ratio, stale content, invalidation time, and origin request volume.
3. Place the origin near the largest user populations
Choose a hosting region close to the users who generate most dynamic traffic. If visitors are widely distributed and every request requires computation, use multi-region application deployment or data placement where consistency and failover requirements permit it. AWS describes moving systems closer to users and using options such as Local Zones and CloudFront to reduce distance.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Proximity is not a substitute for efficient processing. Measure database and application time in each region, and account for cross-region calls: a front end in one region that synchronously queries a database in another can recreate the distance you removed.
4. Improve routing and cache hierarchy when the traffic justifies it
Tiered caching lets regional or upper-tier caches fetch from the origin once and serve many lower-tier edges, reducing repeated long-haul fetches. Managed routing can select less congested paths or healthier origins. Cloudflare reports an average 30% latency reduction for its Argo Smart Routing product; that is a product claim and should not be treated as a guaranteed result for your routes.
Use routing controls when measurements show path quality or origin selection is a material problem. Compare latency, packet loss, availability, observability, and recurring operating cost against the simpler option of better cache placement.
5. Reduce requests and bytes
- Resize images to their displayed dimensions and compress them; choose an efficient format appropriate to the browser and image type.
- Minify CSS and JavaScript, remove dead code, and split bundles so the first view does not download features it cannot use.
- Inline only genuinely critical small CSS; defer noncritical styles and scripts without delaying required interaction.
- Remove third-party tags that do not support a measured business or accessibility requirement.
- Preload only resources needed immediately, and avoid creating a long chain of dependent requests.
- Serve fonts efficiently, limit families and weights, and ensure font loading does not block readable text.
These changes improve transfer and rendering time. They cannot eliminate the physical propagation delay between a visitor and an origin.
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 reinstall6. Reuse connections and set correct cache headers
Keep-alive and modern HTTP connection reuse prevent repeated setup for related requests. Serve resources over a configuration that supports connection reuse, and avoid scattering assets across unnecessary hostnames. Set explicit freshness, validation, compression, and content-type headers so browsers and intermediary caches can reuse responses safely.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.CDN edge caching or closer hosting?
These solutions address different bottlenecks and are often combined.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
| Decision axis | Edge caching | Closer or multi-region hosting |
|---|---|---|
| Best fit | Cacheable static files and repeatable public responses. | Dynamic pages, APIs, and personalized requests that must reach compute. |
| Geography | Places cached bytes at multiple edge locations. | Places application and data processing nearer to user populations. |
| Freshness | Requires explicit TTLs, revalidation, and invalidation rules. | Can return current data directly, but deployment and replication add complexity. |
| Origin processing | Reduces origin requests only when a cache hit is possible. | Reduces distance to the origin but does not fix slow code or queries. |
| Routing control | May provide tiered cache or managed path selection. | Can route users to regional compute and failover targets. |
| Observability | Track hit ratio, edge timing, cache status, and invalidation. | Track regional TTFB, application traces, database time, and replication health. |
| Cost and operations | Usually the quickest change for static delivery; fees and cache rules still apply. | Higher deployment, data, and operational complexity when multiple regions are involved. |
If a large share of traffic requests identical static assets, edge caching is usually the quickest first intervention. If requests are personalized or uncachable, a closer or multi-region origin matters more.
A practical rollout plan
For a mostly static site
- Measure document and asset timings from each important audience region.
- Put versioned assets behind edge caching and verify cache status after a cold and warm request.
- Set long-lived freshness for immutable files and a controlled policy for HTML.
- Resize images, remove unused scripts, and check that the first render does not wait on noncritical resources.
- Re-test cache-hit ratio, TTFB, transfer time, and p75/p95 results.
For a dynamic application or API
- Trace TTFB into application, database, dependency, and queue time.
- Cache only public, repeatable responses; keep private and personalized data uncacheable or correctly keyed.
- Place compute and data near the largest user groups, then test consistency and failover.
- Reduce synchronous cross-region calls and optimize slow queries.
- Use routing or tiered caching only after measurements show path or repeated-fetch problems.
For a globally distributed audience
- Break RUM data down by country, ISP, device, and connection type.
- Compare edge cache performance with regional-origin performance for dynamic requests.
- Set a target for p75 and p95 rather than optimizing only the fastest region.
- Test during different times and failure conditions, including an origin outage or cache purge.
Common mistakes and how to correct them
Confusing a speed test with website latency
A speed test measures capacity to a test server. It does not reveal your site’s DNS, route, TLS setup, TTFB, cache policy, or browser execution. Use page waterfalls and RUM for those questions.
Caching everything publicly
Public caching of personalized responses can expose data or serve one user’s content to another. Classify responses by privacy and variability first, then write cache keys and headers that reflect those differences.
Purging caches for every deployment
Frequent global purges create origin spikes and erase the benefit of long-lived caching. Prefer versioned filenames for static assets and reserve purges for content that cannot be versioned.
Adding a CDN without fixing a slow origin
A cache miss still waits for the origin. If TTFB remains high on misses, profile code, databases, and dependencies or move compute closer to users.
Optimizing only the median
p50 can look healthy while distant users or congested mobile networks suffer at p95. Segment by region and connection type, and watch error rates alongside latency.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Assuming fewer files always wins
Large monolithic bundles can delay the first view and force every page to download unused code. Split by route or feature, keep critical resources small, and measure the resulting request and execution costs.
How to judge whether a change worked
Change one major variable at a time where possible. Capture a baseline, deploy the change, warm and cold-test caches, and compare the same URLs from the same regions. Review:
- DNS, TCP, TLS, TTFB, transfer, and total timing for representative resources.
- p50, p75, and p95 real-user timings by geography and device.
- Cache-hit ratio, origin request rate, and invalidation or stale-content incidents.
- Application, database, and dependency timing for dynamic requests.
- Error rates, timeouts, availability, and operating cost.
A change that lowers TTFB but increases errors, serves stale private data, or raises cost beyond its value is not a successful latency improvement. Keep freshness, privacy, reliability, observability, and ongoing operations in the same decision.
Quick Recap
Key takeaways
- Latency is round-trip delay; bandwidth is capacity. A fast connection can still have a slow website response.
- Distance, DNS and connection setup, routing conditions, origin processing, request count, payload size, and browser work all contribute.
- Measure DNS, TCP, TLS, TTFB, transfer, cache status, and rendering separately instead of guessing.
- Edge caching removes avoidable origin trips for cacheable content; geographically appropriate compute reduces delay for dynamic requests.
- Smaller assets, fewer requests, persistent connections, and non-blocking resources improve perceived speed but cannot remove propagation delay.
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.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
