How to Fix High Ping on WiFi: Step-by-Step Diagnosis and Fixes for Laggy Gaming and Video Call Drops

High ping on WiFi is one of the most frustrating networking problems because it shows up in the worst moments — mid-match lag spikes, frozen video call screens, audio that cuts out and rejoins. Most people assume the fix is a faster internet plan. Usually it isn’t. The real cause is almost always somewhere in the local network chain between your device and the router, and fixing it costs nothing beyond a few configuration changes and, in some cases, a cable.

This guide starts with diagnosis — because applying the wrong fix wastes time — then works through every practical remedy in order of impact.

Step 1: Diagnose Where the Ping Is Coming From

Run a speed test from the WiFiSpeed homepage. It measures download speed, upload speed, and ping in a single test. Note your ping result. Then open a command prompt on Windows (Win + R, type cmd) or a Terminal on Mac and run:

ping 8.8.8.8

Run this while your game or video call is active. Compare the results:

• Test ping is 10ms but game ping is 80ms: The problem is game server location, not your network. No local fix will help; the server is simply far away.
• Test ping is 40ms and game ping is 80ms: Your local network or ISP is adding latency. Work through the fixes below.
• Ping is normally fine but spikes unpredictably: This is jitter, not steady high ping. Our jitter guide covers the distinct causes and fixes for inconsistent latency.

The most reliable isolation test: plug a laptop directly into the router with Ethernet and run the same ping test. If the wired device pings 10ms while your WiFi device pings 50ms, the wireless link — not the ISP — is your bottleneck. If both are high, the problem is upstream.

Fix 1: Use Ethernet — The Biggest Single Impact

WiFi adds 20–80ms of latency on top of your ISP’s baseline ping. A wired Ethernet connection typically delivers 5–15ms local round-trip time. No router setting, no QoS tweak, and no DNS change will fully close that gap. If your gaming PC, console, or work laptop is within cable reach of the router, a Cat6 patch cable drops latency more effectively than any hardware upgrade. A 10-foot cable costs under $10.

For devices that cannot easily run a cable — a TV in a different room, a desktop across the house — a MoCA adapter pair routes wired-speed traffic over the existing coaxial cable already in your walls. Our MoCA adapters guide explains how to set one up. Powerline adapters are a lower-cost alternative over electrical wiring, though they are more susceptible to electrical noise. Our powerline vs mesh comparison covers the trade-offs.

When You Cannot Run a Cable

Position the device as close to the router as feasible with clear line of sight. Walls, floors, and dense appliances force the WiFi radio to retransmit failed packets — each retransmission adds latency on top of normal wireless overhead. Every wall between your device and the router increases ping. Every additional floor roughly doubles the signal attenuation.

Fix 2: Switch to 5 GHz (or 6 GHz)

The 2.4 GHz band is shared by legacy WiFi devices, IoT sensors, baby monitors, cordless phones, and every neighbor network within range. Channel congestion on 2.4 GHz causes packet retransmissions that show up directly as elevated and inconsistent latency. The 5 GHz band has more non-overlapping channels and far less crowding from neighboring networks, which translates to lower and more consistent ping for devices within range.

For a device within 25–30 feet of the router with no more than one or two walls in between, 5 GHz outperforms 2.4 GHz for both throughput and latency in nearly every scenario. If your router or phone supports WiFi 6E or WiFi 7, the 6 GHz band goes further — virtually no competing networks use it yet, so interference is negligible for devices close to the router. Our 2.4 GHz vs 5 GHz vs 6 GHz guide covers the range trade-offs in detail.

Fix 3: Close Background Applications

A large background download or upload uses the same network queue as your game traffic. Without QoS configured, a 50 Mbps Steam download can push your game packets to the back of the transmit queue, spiking ping by 20–60ms even on a fast connection. This is the classic bufferbloat problem.

On Windows, open Task Manager with Ctrl + Shift + Esc and click the Network column to sort processes by bandwidth use. Common offenders during gaming sessions: Windows Update, OneDrive or Google Drive sync, Steam pre-loading a queued game, Discord auto-updates, and browser tabs streaming video in the background. Suspend all background downloads while gaming or on video calls.

Fix 4: Enable QoS on Your Router

Quality of Service (QoS) instructs your router to process gaming and video-call traffic before bulk data transfers when the uplink is near capacity. Without QoS, all traffic competes equally for the outgoing queue — a file backup upload by one device can cause your in-game packets to wait, creating the latency spikes that look like lag.

QoS configuration varies by router brand:

• ASUS routers: Log into the admin panel at 192.168.1.1, go to Advanced Settings → Adaptive QoS, enable it, and set Gaming as the top-priority category. You can also pin your gaming device to the highest priority slot by MAC address.
• TP-Link Archer routers: Go to Advanced → QoS, enable QoS, and add your console or PC as a High Priority device.
• Netgear Nighthawk: Open the Nighthawk app or go to Advanced → Setup → QoS Setup and enable Upstream QoS. Assign your gaming device the highest priority.
• Eero: Eero’s QoS is available through the eero app under Activity → Prioritize Device.

QoS has the most impact when multiple people share the connection simultaneously. If you are the only active user and ping is still high, QoS is not the root cause — continue down this list.

Set QoS Bandwidth to 80–90% of Your Measured Speeds

When configuring QoS bandwidth limits, enter 80–90% of your actual measured download and upload speeds from a speed test — not your plan’s advertised maximum. This buffer prevents the router itself from becoming the bottleneck, which would create queue delays that make QoS counterproductive.

Fix 5: Change Your DNS Server

Your ISP’s default DNS server resolves game server hostnames every time you connect to a new match or server instance. If the DNS server is slow or temporarily congested, every new connection starts with an extra 20–100ms delay. Switching to a faster public resolver takes under two minutes:

• Cloudflare: 1.1.1.1 (primary) and 1.0.0.1 (secondary) — consistently among the fastest globally
• Google: 8.8.8.8 (primary) and 8.8.4.4 (secondary) — high reliability and broad coverage

Change DNS in your router’s admin panel rather than on individual devices — it applies to everything on the network at once. Our full guide on changing your DNS server for faster internet covers the exact steps for TP-Link, ASUS, Netgear, and Eero.

Fix 6: Update Router Firmware

Outdated router firmware can leave performance regressions in place that manufacturers have already patched. Some firmware releases contain explicit improvements to NAT processing speed, QoS scheduling accuracy, and wireless driver behavior that directly affect latency. Most current routers — ASUS, TP-Link Archer, Netgear Nighthawk, and eero — support automatic firmware updates from their admin panels or companion apps. Check for pending updates and install them. For a step-by-step walkthrough across brands, see our router firmware update guide.

Fix 7: Check for WiFi Interference

Devices operating on 2.4 GHz — microwave ovens, cordless phones, baby monitors, and Bluetooth speakers — can temporarily saturate the channel and force WiFi packet retransmissions that spike ping. If your high ping correlates with kitchen use, phone calls, or specific times of day, interference is a likely contributor. Moving the router away from the microwave and switching to 5 GHz eliminates most of these sources entirely. Our guide on common WiFi interference sources covers each source and how to identify it.

When None of These Fixes Work

If ping remains high after switching to Ethernet, enabling QoS, updating firmware, and changing DNS, the problem is almost certainly upstream — either your ISP’s routing to specific game servers, or congestion on your ISP’s backbone during peak evening hours. Run the ping test at different times of day: if latency is low at 9 AM and spikes after 7 PM, the ISP is congested and a plan upgrade or ISP change is the only lasting fix. Contact your ISP with the test data — documented consistent latency issues during peak hours are sometimes escalated and resolved without a plan change.

For persistent latency problems despite a strong speed test, our bufferbloat guide covers how queue congestion inside your own router can create lag that looks identical to ISP problems but is fully fixable with the right router settings.