CDN Performance Analyzer - Test CDN Speed
Test your CDN's performance from locations worldwide. Measure response times, cache hit rates, TTFB, and identify optimization opportunities.
Understanding This Tool
What It Does
This tool measures how long a single HTTP request to one URL takes when made from ShowMyIP's server. When you submit a URL, the server sends one HEAD-style request that fetches only the response headers, times the full round trip with a millisecond stopwatch, and shows you that elapsed time. It is a quick one-shot connectivity-and-latency check from a single fixed location, and it discards the headers it fetches: it does not detect whether the URL is on a CDN, and it does not measure cache behavior or break the timing into phases.
Understanding the Results
- URL: The exact address you submitted, echoed back. This is your original input, not the final address after any redirects, so if the request was redirected the displayed URL may differ from the location that was actually measured last.
- Response Time: The approximate total round-trip time in milliseconds for the request, measured from ShowMyIP's server. This single sample includes everything the request did: a DNS lookup for the hostname, the TCP connection, the TLS handshake on HTTPS, up to 3 redirect hops if the server redirects, and receiving the response headers. It is one measurement with no averaging, so repeat tests will vary with network conditions.
Common Use Cases
- Quick latency spot-check: Get a rough sense of how fast a given URL or asset responds to a request originating from our server's location.
- Confirming a URL is reachable: A returned time means the request completed; an error message means the host could not be resolved or connected to within the timeout.
- Comparing two asset URLs: Run the same test against two different file URLs to see which responds faster from this single vantage point, keeping in mind each is one sample.
- Sanity-checking an edge or origin endpoint: If the asset is served by a CDN, this gives you the round-trip time from our server to whichever edge or origin the request reaches, useful as a rough before-and-after gauge after a configuration change.
- Detecting slow or timing-out hosts: Very high times, or an error after the 10-second timeout, can flag a misconfigured, overloaded, or unreachable endpoint.
Pro Tips & Best Practices
- Run it more than once: A single sample is affected by DNS caching, network jitter, and server load. Several runs give a better feel for typical latency than any one number.
- The measurement is from our server, not you: The time reflects the path between ShowMyIP's server and the target, in one fixed location. It will not match what your own browser or your users in other regions experience.
- Point it at a specific file, not just a homepage: Testing a direct asset URL (such as a script, image, or stylesheet) isolates the response time of that resource rather than a full HTML page.
- Treat errors as information: An error means DNS resolution, the connection, or a redirect failed or hit a limit (the tool follows at most 3 redirects and blocks requests to private or reserved addresses, certain internal hostnames, and certain ports). It does not necessarily mean the site is down for everyone.
Frequently Asked Questions
No. It only measures and displays the total round-trip time of a single HEAD-style request from our server. It fetches the response headers to complete the request but then discards them, so it does not report cache status, time-to-first-byte, or any header-by-header breakdown. The single Response Time value covers DNS, connection, TLS, any redirects, and the header response all together.
No. Every measurement comes from ShowMyIP's single server location. The tool does not test from multiple global points and does not reflect latency from your location or from your users elsewhere.
No. The tool times any reachable HTTP or HTTPS URL the same way and does not analyze headers to identify a CDN provider. If your asset happens to be on a CDN, the time simply reflects the round trip to whichever edge or origin the request reached.
Because each run is a single live measurement, not an average. DNS caching, network congestion, the path taken, and load on the target server all shift the result from one run to the next. Running it several times gives a more reliable picture.
The request did not complete. Common reasons are a hostname that cannot be resolved, a connection that failed or exceeded the timeout (10 seconds total, 5 seconds to connect), more than 3 redirects, or a target that the tool blocks for security, such as a private or reserved IP address, a known internal hostname, or a restricted port.
Frequently Asked Questions
Does this tool show cache hit rate or TTFB?
No. It only measures and displays the total round-trip time of a single HEAD-style request from our server. It fetches the response headers to complete the request but then discards them, so it does not report cache status, time-to-first-byte, or any header-by-header breakdown. The single Response Time value covers DNS, connection, TLS, any redirects, and the header response all together.
Is the test run from multiple locations around the world?
No. Every measurement comes from ShowMyIP's single server location. The tool does not test from multiple global points and does not reflect latency from your location or from your users elsewhere.
Does it detect whether my URL is served by a CDN?
No. The tool times any reachable HTTP or HTTPS URL the same way and does not analyze headers to identify a CDN provider. If your asset happens to be on a CDN, the time simply reflects the round trip to whichever edge or origin the request reached.
Why does the time change every time I run it?
Because each run is a single live measurement, not an average. DNS caching, network congestion, the path taken, and load on the target server all shift the result from one run to the next. Running it several times gives a more reliable picture.
Why did I get an error instead of a time?
The request did not complete. Common reasons are a hostname that cannot be resolved, a connection that failed or exceeded the timeout (10 seconds total, 5 seconds to connect), more than 3 redirects, or a target that the tool blocks for security, such as a private or reserved IP address, a known internal hostname, or a restricted port.
Last reviewed:
How this tool works: This tool runs in your browser and on our server in real time. Depending on the tool, results are computed directly from the input you provide or retrieved from live, authoritative data sources at the moment you run a lookup. We do not sell your data, and your lookups are kept private — any history shown here is stored only on your device.