Nationwide Speed Map

- >10s
- 3s-10s
- 1s-3s
- 0.5s-1s
- <=0.5s
11 monitoring points in this test
100%
| Region | Fastest | Slowest | Average |
|---|---|---|---|
| All Nodes | -- | -- | -- |
| China Telecom | -- | -- | -- |
| China Unicom | -- | -- | -- |
| China Mobile | -- | -- | -- |
| East China | -- | -- | -- |
| South China | -- | -- | -- |
| Central China | -- | -- | -- |
| North China | -- | -- | -- |
| Southwest | -- | -- | -- |
| Northwest | -- | -- | -- |
| Northeast | -- | -- | -- |
| HK/MO/TW | -- | -- | -- |
DNS Resolution Stats
0Showing: 0/0
| Node | Response IP | IP Location | Status | Total | Resolve | Connect | Download | Redirect | Head |
|---|---|---|---|---|---|---|---|---|---|
| No valid test results were obtained. Please run the test again. | |||||||||
Website Speed Test Test Findings for tn1p1021.tjlhsji.com
- Tested
- Oct 21, 2026, 7:39 PM
- Completed probes
- 11/11
- Valid HTTP response probes
- 0 (0%)
- Average total response time
- --
This HTTP website speed test on 2026-10-21 recorded an overall response rate of 65.1%, below the 95% reference threshold, with a median total response time of 957 ms and a 95th percentile of 4259 ms. The telecom carrier's low response rate
There is not enough network HTTP speed-test data to draw this chart.
Key findings
- The overall response rate was 65.1%: 105 of 301 observed nodes did not obtain a valid HTTP response. Status codes were mostly 200 (185), with 11 instances of 302.
- The telecom carrier's response rate was 17.6%, 82.4 percentage points below the overseas carrier's 100%, exceeding the 10-point reference threshold.
- Unicom and mobile recorded response rates of 98.6% and 92.3%, with median total response times of 869 ms and 918 ms, appearing comparatively stable.
- The overseas carrier reached a 100% response rate, but its median total response time was 3240 ms and its 90th percentile 4341 ms, well above the domestic carriers.
Improvement recommendations
- The HTTP response rate is 0%, below the 95% review threshold. Retest failed probes and use their status codes or network errors to inspect the CDN, reverse proxy, or origin only if failures persist.
These results describe this distributed test only and do not establish long-term availability, security, or a root cause.