Choosing a Router for Gaming: Latency Before Labels

Choose a gaming router by the problem it can solve, not by a gaming badge or a promised ping number. First separate local Wi-Fi trouble from delay that appears when the connection is busy. Then look for documented features, sufficient capacity with those features enabled, and a practical way to test and return the device if it does not help.

This is a selection and troubleshooting guide, not a hands-on product review. It contains no product scores, measured router rankings or purchase links.

Before buying: reproduce the symptom

Ofcom's broadband troubleshooting guidance recommends trying a wired connection and testing at different times. Use that to distinguish a repeatable network problem from a single poor run.

  • Only the distant Wi-Fi room is troublesome: compare the same device closer to the router and, where possible, by Ethernet. Placement and the wireless path deserve attention before replacing the gateway.
  • Calls or games degrade during uploads or downloads: compare idle and busy conditions using the same test endpoint. Queueing is one possibility, not a diagnosis based solely on a game disconnect.
  • The application is poor even when the connection is quiet: record the game region, time and symptoms. A new router cannot be assumed to change the remote server or the wider internet path.

Keep changes reversible and alter one setting at a time. Do not disable security controls or bypass an ISP gateway simply to chase a lower number.

Understand what queue management can help with

OpenWrt documents Smart Queue Management (SQM) as a combination of scheduling, active queue management, shaping and related functions to mitigate latency under heavy load. Its SQM guide distinguishes this from priority-only QoS and identifies CAKE and fq_codel as queue-discipline options.

A feature labelled “gaming priority” is not, by itself, evidence that a router can control your bottleneck. Ask what the feature actually does and whether the implementation supports your WAN setup. SQM may trade some peak throughput for better responsiveness under load. It does not promise to eliminate every source of delay or repair a radio-coverage problem.

OpenWrt also warns that SQM consumes CPU resources and that slower hardware may not keep up with full line rate. Its hardware-flow-offloading caveat applies to that documented OpenWrt configuration; do not generalise it to every vendor's acceleration system.

Questions to answer for each candidate

Firmware and support
Which exact hardware revision and firmware support the needed feature? Is the documentation current, and are updates available?
Capacity with features enabled
Look for evidence measured with shaping, security and any required VPN enabled. A raw routing rate is not proof of performance with all processing active.
Access-service compatibility
Confirm requirements with the ISP: WAN handoff, authentication, any retained gateway and bundled telephone or television services. Do not assume every router can replace every supplied box.
Ports and coverage
Match wired ports to your devices and plan. Decide separately how to cover the rooms you use; a higher headline wireless class is not a measurement in your home.
Recovery and return
Save the old configuration, know how to restore it, and check the seller's actual return conditions. A reversible trial is more useful than an unsupported universal recommendation.

Use a shortlist worksheet with one row per device and a link to the exact vendor manual for each claimed feature. Mark unverified capabilities as unknown. This guide does not certify any model's compatibility or throughput.

Test whether the change helped

  1. Save a baseline: device, wired or wireless connection, firmware, endpoint, time, idle performance and performance during a known transfer.
  2. Apply the documented setting for your own device. If using OpenWrt SQM, start from its preparation and setup instructions rather than copying another person's bandwidth values.
  3. Repeat comparable tests and the actual game or call. Compare both responsiveness and useful throughput, including upload.
  4. Check that other household tasks still work. If performance worsens or the configuration becomes unreliable, restore the baseline and investigate before buying again.

Do not compare grades from different tools as if they share a calculation. Keep the underlying measurements and conditions. The goal is a repeatable improvement in your application, not an isolated screenshot with a better letter.

Sources and next steps

This guide draws on OpenWrt's SQM documentation for queue-management behavior and limitations, and Ofcom's practical troubleshooting advice for repeatable wired/wireless checks. Neither source is a VelocityVerify product benchmark.

For the record to keep when the connection itself seems slow, use our advertised-versus-measured checklist. For interpreting broader statistical claims, read how to read broadband speed reports.