Valorant
Records server selection, party state, mode, network graphs and match evidence.
Download Valorant CSV →Open Valorant guide →Real test evidence kit
Six runs. Matching conditions. Raw evidence retained.
Each sheet has three normal-route runs and three controlled comparison runs. Empty measurements stay empty until a real game session supplies them.
Counter-Strike 2
Records current telemetry labels, matchmaking-ping constraint, party, map and frame-time context.
Download CS2 CSV →Open CS2 guide →Fortnite
Records matchmaking region, mode, party state, Net Debug Stats and match evidence.
Download Fortnite CSV →Open Fortnite guide →Apex Legends
Records data center, Performance Display, party, platform and match evidence.
Download Apex CSV →Open Apex guide →Escape from Tarkov
Records map, party leader, raid timing, server context and visible desync symptoms.
Download Tarkov CSV →Open Tarkov guide →World of Warcraft
Records realm, activity, Home and World latency, group state and evidence files.
Download WoW CSV →Open WoW guide →Genshin Impact
Records account server, platform, solo or co-op state, displayed latency and device behavior.
Download Genshin CSV →Open Genshin guide →Before run one
Freeze the conditions you can control.
Choose one game activity and one server, realm or matchmaking region. Record the device, connection method, party state and local time before changing a route or network setting. Pause downloads and cloud sync, and note any traffic you cannot pause.
A fair comparison does not require a laboratory. It requires the same question, the same visible symptom and enough context to explain what changed.
Required context
- Game version, mode or activity and selected service region.
- Device, Ethernet or Wi-Fi, and other household traffic.
- Visible symptom: stable high ping, spikes, loss, disconnects or frame-time stutter.
- Evidence filename for the in-game graph, screenshot or local log.
- Notes for failed or interrupted runs instead of deleting them.
Run order
Three baselines, then three comparisons.
Record three runs on the normal ISP route first. Change only the route or single setting being evaluated, then record three comparison runs under the closest practical conditions. The browser comparison uses medians so one unusually good or bad result does not become the headline.
If the server, party, activity or household traffic changes materially, stop and begin a new record instead of combining incompatible runs.
Interpretation limits
- A lower median in one location and time window is not a universal recommendation.
- Stable ping does not rule out packet loss, frame-time stutter or a service incident.
- A route cannot repair Wi-Fi interference, upload saturation or device performance.
- Missing jitter or loss values must stay missing; do not substitute estimates.
- Keep the raw files so another reader can audit the published summary.
The evidence contract
What must stay the same.
Use the same game version, device, connection method, server or realm and comparable activity. Keep failed runs; do not retain only the best screenshot.
What a record may conclude
- It may describe the six recorded runs and their conditions.
- It may compare medians for this location and time window.
- It may not claim a universal performance improvement.
- It may not turn one successful run into a product recommendation.
- Every published result needs raw screenshots or logs and explicit limits.