Download and upload throughput
It estimates how much data your device can move to and from a selected test server.
Website test vs speedtest
Website test vs speedtest: what is actually being measured?
A normal speedtest can show whether your own connection is fast, but it does not prove that a specific website, API, CDN, or domain is reachable and fast from Vietnam. A website test checks the real target URL and separates DNS, TCP, HTTP, and latency signals.
- Internet speedtests focus on the user connection and nearby test servers
- Website tests focus on a real URL, hostname, port, response path, and regional behavior
- Use both when you need to separate last-mile speed from website-side, DNS-side, or CDN-side problems
What does a normal speedtest usually measure?
Ping to a test server
It measures latency to the speedtest endpoint, which may be different from the route to your website.
Local device and ISP path
The result is affected by Wi-Fi, device load, the local ISP, and how close the test server is.
A general connection baseline
It is good for checking whether the user's internet access is broadly healthy.
What does a website test measure instead?
1
Resolve the domain
DNS results show which A, AAAA, or CNAME answers are returned from different probes or resolvers.
2
Check TCP reachability
TCP checks show whether the target port can be reached before a full HTTP response is available.
3
Read HTTP status and headers
HTTP checks show status code, redirects, timing, and response headers, which help identify CDN or application differences.
4
Compare Vietnam probe results
Regional probes help show whether slowness is broad, local, or tied to a specific network path in Vietnam.
Which one should you use?
Use speedtest for the user's connection
If every website is slow, start with a normal speedtest to check the user's local internet quality.
Use 13CE for one website or API
If only one domain, CDN, login page, API, or game endpoint is slow, test that target directly.
Use DNS results when routing looks inconsistent
Different DNS answers can explain why one region reaches a different CDN edge or origin path.
Use both during incidents
A speedtest can rule out a local connection issue, while a website test can confirm whether the target path is unhealthy.
Quick comparison
SpeedtestInternet speedtest
- Measures a generic connection
- Usually selects a test server automatically
- Good for user-side baseline checks
13CEWebsite test
- Measures a specific URL or hostname
- Shows DNS, TCP, HTTP, latency, and regional differences
- Good for CDN, API, and website troubleshooting
Ready to test a real website path?
Start with the target URL instead of a generic connection score. Then compare HTTP, DNS, TCP, and latency results to decide whether the issue is local, regional, DNS-related, CDN-related, or application-side.