// TOOLING

SpeedTestVisualizer

speedtest-visualizer.sh
screenshot.png
SpeedTest Visualizer
performance_metrics.log
0
DL streams
0
UL streams
0
Pings per test
0
Connection grades
/* |

Browser-based speed tests show you a single number and discard it. Standard single-stream tests underreport real-world throughput because modern connections are designed for concurrent traffic. There was no tool that tested the way real applications use the network, in parallel, and kept a historical record to spot patterns over time.

// |

A dual-layer speed test. The backend runs 6 parallel download streams (size ladder: 1, 2, 4, 8, 16, 32 MB), 4 parallel upload streams, and 20 pings at 80ms intervals (jitter = standard deviation of RTTs). A 10-second measurement window with a 2-second congestion warmup discards early ramp-up noise. ip-api.com identifies the ISP and location. Results are graded into letter-grade connection profiles (A–F) and rendered as an interactive 3D time-series graph with React Three Fiber.

=> |

Parallel streaming produces throughput figures 15–30% closer to real application performance than single-stream tests. The 3D dashboard makes peak-hour throttling and ISP inconsistency immediately visible across test history.

$ list features

# 5 features found

+Parallel Stream Engine

6 concurrent download fetches across a size ladder (1→32 MB) and 4 concurrent upload streams saturate the connection the way real applications do. The 10-second measurement window with a 2-second warmup discards TCP slow-start noise from the final average.

+Latency & Jitter Suite

20 pings fired at 80ms intervals. Jitter is computed as the standard deviation of round-trip times, a more statistically honest measure than min/max range. Results feed the profile grading system.

+ISP Identification

ip-api.com resolves the public IP to ISP name and region at the start of each test. Results are tagged so you can compare performance across ISPs or network locations in the history view.

+Letter-Grade Connection Profiles

Download speed, upload speed, latency, and jitter are each graded A–F against thresholds derived from real-world application requirements. The overall grade is the lowest individual grade, the weakest link defines the experience.

+3D Time-Series Dashboard

React Three Fiber renders historical test results as a 3D surface with orbit controls. A flat chart hides whether your connection degrades at peak hours, the 3D surface makes it visible at a glance.

$ npm list --depth=0

package.json · dependencies

$ git log --oneline

$ debug --issues

FIX:

TCP slow-start means the first 1–2 seconds of any download massively underreport the connection's true capacity. A 2-second warmup window discards all samples before the connection stabilises, the 10-second measurement only begins after the pipe is full.

FIX:

Reporting min/max RTT range as jitter overstates variability, one outlier ping ruins the figure. Standard deviation of 20 RTTs is stable, meaningful, and the figure VoIP applications actually care about for call quality prediction.

FIX:

Rendering each historical test as a separate geometry caused frame drops past ~100 sessions. All data points are merged into a single BufferGeometry; vertex positions update in-place on new data, draw calls remain at 1 regardless of history length.

LET'S BUILD SOMETHING TOGETHER

I'm always open to discussing new projects, partnerships, or just a good idea.