Nationwide Speed Map
- >10s
- 3s-10s
- 1s-3s
- 0.5s-1s
- <=0.5s
12 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: 12/12
| Node | Response IP | IP Location | Status | Total | Resolve | Connect | Download | Redirect | Head |
|---|---|---|---|---|---|---|---|---|---|
| 电信贵州贵阳电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信湖北十堰电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信四川广安电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信河北电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信北京电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 联通甘肃联通 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 联通上海数据中心 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 海外俄罗斯莫斯科 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 海外柬埔寨金边 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 海外迪拜 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信电信青海 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
| 电信宿迁电信 | -- | 节点异常 | Node unavailable | -- | -- | -- | -- | -- | -- |
Website Speed Test Test Findings for nelson898.github.io
- Tested
- Sep 25, 2026, 9:00 AM
- Completed probes
- 12/12
- Valid HTTP response probes
- 0 (0%)
- Average total response time
- --
This HTTP website speed test, observed on 2026-09-25, recorded an overall response rate of 92.4%, a median total response time of 1293 ms and a P95 of 10436 ms. Of 317 observed nodes, 278 returned 200, with 14 returning 301 and 1 returning
There is not enough network HTTP speed-test data to draw this chart.
Key findings
- The overall response rate was 92.4%, below the 95% threshold; 24 nodes did not obtain a valid HTTP response, while 2 platform probe failures are excluded from website performance.
- P95 total response time reached 10436 ms, above the 10000 ms threshold, while the median was only 1293 ms, indicating slow results concentrated in the tail.
- Unicom showed an 85.7% response rate, 14.3 percentage points below the 100% seen on overseas routes and above the 10-point threshold; its P50 of 2518 ms also exceeded telecom at 1050 ms and mobile at 1172 ms.
- Status codes were dominated by 200 (278), alongside 14 instances of 301 and 1 of 302; 4 response IPs were observed, which is address diversity within this observation window.
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.