Nationwide Speed Map

- >10s
- 3s-10s
- 1s-3s
- 0.5s-1s
- <=0.5s
29 monitoring points in this test
100%
| Region | Fastest | Slowest | Average |
|---|---|---|---|
| All Nodes | 台湾台北 0.262s | 澳门 0.350s | 0.304s |
| China Telecom | -- | -- | -- |
| China Unicom | -- | -- | -- |
| China Mobile | -- | -- | -- |
| East China | -- | -- | -- |
| South China | -- | -- | -- |
| Central China | -- | -- | -- |
| North China | -- | -- | -- |
| Southwest | -- | -- | -- |
| Northwest | -- | -- | -- |
| Northeast | -- | -- | -- |
| HK/MO/TW | 台湾台北 0.262s | 澳门 0.350s | 0.304s |
DNS Resolution Stats
2Showing: 29/29
| Node | Response IP | IP Location | Status | Total | Resolve | Connect | Download | Redirect | Head |
|---|---|---|---|---|---|---|---|---|---|
| 海外台湾高雄 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.305s | 0.043s | 0.004s | 0.191s | -- | |
| 海外台湾台北 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.262s | 0.004s | 0.004s | 0.187s | -- | |
| 海外香港 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.298s | 0.004s | 0.023s | 0.202s | -- | |
| 海外澳门 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.350s | 0.016s | 0.001s | 0.261s | -- | |
| 海外卡塔尔 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.744s | 0.291s | 0.015s | 0.216s | -- | |
| 海外沙特阿拉伯 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.673s | 0.218s | 0.017s | 0.220s | -- | |
| 海外印度 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.604s | 0.140s | 0.002s | 0.306s | -- | |
| 海外印度尼西亚 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.317s | 0.036s | 0.002s | 0.243s | -- | |
| 海外新加坡 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.248s | 0.012s | 0.001s | 0.220s | -- | |
| 海外日本东京 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.184s | 0.009s | 0.002s | 0.157s | -- | |
| 海外以色列 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.371s | 0.117s | 0.005s | 0.148s | -- | |
| 海外韩国 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.356s | 0.103s | 0.003s | 0.185s | -- | |
| 海外越南 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.408s | 0.071s | 0.001s | 0.265s | -- | |
| 海外马来西亚 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.332s | 0.086s | 0.009s | 0.224s | -- | |
| 海外菲律宾 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.367s | 0.050s | 0.001s | 0.249s | -- | |
| 海外泰国 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.373s | 0.062s | 0.028s | 0.250s | -- | |
| 海外韩国 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.687s | 0.260s | 0.038s | 0.305s | -- | |
| 海外菲律宾 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.379s | 0.029s | 0.004s | 0.266s | -- | |
| 海外英国 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.159s | 0.025s | 0.002s | 0.106s | -- | |
| 海外芬兰 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.229s | 0.071s | 0.009s | 0.126s | -- | |
| 海外西班牙 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.223s | 0.054s | 0.002s | 0.119s | -- | |
| 海外德国 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.121s | 0.010s | 0.002s | 0.097s | -- | |
| 海外法国 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.151s | 0.025s | 0.002s | 0.104s | -- | |
| 海外波兰 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.214s | 0.046s | 0.020s | 0.115s | -- | |
| 海外美国芝加哥 | 35.71.171.212 | 美国///亚马逊 | 200 | 0.144s | 0.002s | 0.009s | 0.082s | -- | |
| 海外美国华盛顿 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.135s | 0.002s | 0.001s | 0.082s | -- | |
| 海外巴西 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.470s | 0.130s | 0.002s | 0.115s | -- | |
| 海外南非 | 166.117.108.131 | 美国///亚马逊 | 200 | 0.804s | 0.183s | 0.002s | 0.269s | -- | |
| 海外澳大利亚 | 35.71.171.212 | 美国///亚马逊 | 200 | 1.057s | 0.223s | 0.002s | 0.424s | -- |
Website Speed Test Test Findings for lootbar.com
- Tested
- Oct 19, 2026, 6:53 PM
- Completed probes
- 29/29
- Valid HTTP response probes
- 29 (100%)
- Average total response time
- 378 ms
This HTTP website speed test ran on 2026-10-12. All 32 observed nodes returned a valid HTTP response with status code 200, giving a 100% response rate. Total response time was 340 ms at the median, 675 ms at P90, and 375 ms on average, with
lootbar.com HTTP speed test performance by network
Valid HTTP response rate counts probes with both a status code and total response time. P50 is the total time at or below which half of valid responses completed.
Valid HTTP response rate
Valid HTTP response rate (%)
100%Highest rate
P50 total response time
Total response time (ms)
332 msLowest P50
Key findings
- All 32 observed nodes obtained a valid HTTP response, every HTTP status code was 200, and the response rate was 100%, with no unavailable nodes.
- Total response time was 340 ms at the median, 675 ms at P90, 741 ms at P95, and 375 ms on average, with the distribution weighted toward the lower range.
- Two response IPs were observed; this is observed response IP diversity for this time window only.
- The telecom, unicom, and mobile carrier groups each had 0 nodes, so no carrier comparison is supported by these figures.
These results describe this distributed test only and do not establish long-term availability, security, or a root cause.