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: 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 scwljsq.scl168.club
- Tested
- Oct 2, 2026, 12:38 PM
- Completed probes
- 12/12
- Valid HTTP response probes
- 0 (0%)
- Average total response time
- --
This HTTP website speed test ran on 2026-10-02. The overall response rate was 11.3%: 34 of 302 observed nodes returned a valid HTTP response, with a median total response time of 399 ms and a P95 of 892 ms. Two issues were detected: a low r
There is not enough network HTTP speed-test data to draw this chart.
Key findings
- The overall response rate was 11.3%, with 268 nodes not obtaining a valid HTTP response; all 34 valid responses were HTTP 200, spread across 14 observed response IPs.
- Telecom nodes showed a 0.8% response rate with only 1 valid response and a total response time of 1340 ms; Unicom and Mobile nodes obtained no valid responses.
- Overseas nodes showed a 100% response rate, with all 33 nodes returning valid responses at a median total response time of 370 ms and an average of 412 ms, a 100 percentage point gap versus Unicom.
- Nine platform probe errors were recorded and excluded from the observed node counts, so they are not attributed to the tested website.
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.