Two Different Problems Called "Lag"

Console players use the word "lag" for two completely different problems, and mixing them up wastes hours of troubleshooting. Network lag is delay between your controller input reaching the game server and the result coming back — this is what a ping test measures. Input lag is delay between pressing a button and seeing it happen on screen, and it has nothing to do with your internet connection at all. It comes from your TV, your controller, and your console's own processing pipeline.

The two feel similar in the moment — everything is "delayed" — but the fixes are completely different. A faster router does nothing for TV-caused input lag, and a Game Mode setting does nothing for a bad NAT type.

Telling Them Apart

It's network lag if: other players rubber-band or teleport, hit registration feels wrong specifically online, single-player or offline modes feel fine, and the problem gets worse during peak evening hours.
It's input lag if: even single-player menus and offline games feel sluggish, the delay is constant rather than variable, and it started after you changed a TV or picture setting.
Quick test: load a single-player game with no online component. If it still feels delayed, look at your TV and controller first. If only online multiplayer feels off, the network is the suspect.

Wired vs Wi-Fi on Console

Both PS5 and Xbox Series X have a built-in Ethernet port, and it is worth using whenever you can reasonably run a cable to your router. A wired connection removes an entire category of timing variation — no radio retransmissions, no contention with your phone or laptop for airtime, no sensitivity to walls or microwaves. For fast multiplayer shooters and racing games, this shows up as steadier hit registration rather than a dramatically lower ping number. See our Wi-Fi vs Ethernet comparison for the actual latency and jitter numbers behind this advice.

If You Have to Use Wi-Fi

Pick the 5 GHz band, not 2.4 GHz. Both PS5 and Xbox Series X support dual-band Wi-Fi. The 2.4 GHz band is crowded with neighboring routers, Bluetooth devices, and even some microwaves, while 5 GHz has more clean channels and less interference — at the cost of shorter range.
PS5 owners with a compatible router can use 6 GHz (Wi-Fi 6E). It is the least congested band available and worth enabling if your router and placement support it.
Reduce distance and obstructions. Every wall and every floor between the console and the router adds signal loss, which increases retransmissions and jitter even if the average speed still looks fine.
Avoid channel overlap. If your router lets you manually pick a Wi-Fi channel, choose one with less traffic from neighboring networks — most router apps show a simple congestion chart for this.

NAT Type: The Setting Most Players Ignore

NAT (Network Address Translation) type controls how easily your console can form a direct connection with other players and with matchmaking servers. Xbox reports it as Open, Moderate, or Strict; PlayStation reports it as Type 1, Type 2, or Type 3. Despite the different labels, they describe the same underlying situation.

Xbox	PlayStation	What it means
Open	Type 1	Console has a direct, unrestricted connection. Best for matchmaking speed and party chat.
Moderate	Type 2	Console is behind a router but can usually still connect to Open/Type 1 players and most matchmaking, sometimes with extra setup delay.
Strict	Type 3	Console struggles to connect directly to other players. Expect slower matchmaking, smaller lobbies, and party chat or voice issues.

A restrictive NAT type does not necessarily mean higher ping once you're in a match, but it directly affects whether you can join certain lobbies at all, how long matchmaking takes, and whether party chat drops or fails to connect. Many "I can't hear my friend" or "can't join this lobby" complaints trace back to NAT type, not bandwidth.

Fixing NAT Type: UPnP vs Manual Port Forwarding

Both approaches solve the same problem — letting your console accept inbound connections instead of only initiating outbound ones — but they work differently:

Try UPnP first. UPnP (Universal Plug and Play) lets your console automatically ask the router to open the ports it needs, with no manual configuration. Log in to your router's admin page (usually 192.168.1.1 or 192.168.0.1 in a browser) and enable UPnP if it isn't already on, then restart the console and re-check NAT type. This fixes the majority of Moderate/Type 2 situations with zero manual setup.
If UPnP doesn't help, forward ports manually. Find your console's current local IP address in its network settings, then in your router's port forwarding section, create rules pointing the required ports to that IP. Microsoft and Sony each publish their current recommended port lists for Xbox Live and PSN — check the official support page for your platform since these numbers occasionally change.
Set a static local IP for the console first. Port forwarding rules point to a specific IP address. If your router hands out a new address to the console every time it reconnects (the default with DHCP), your forwarding rule silently breaks. Either set a static IP on the console or reserve its address in the router's DHCP settings so the forward stays valid.
Double NAT breaks both approaches. If you have a modem and a separate router both doing NAT (common with an ISP-provided gateway plus your own router), UPnP and port forwarding can fail even when configured correctly. Put the ISP gateway into bridge mode, or forward the relevant ports on both devices, to resolve it.

Console DNS Settings: What It Fixes and What It Doesn't

Changing your console's DNS to a public resolver such as 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) changes how quickly hostnames resolve to IP addresses — store pages loading, matchmaking services being located, and account sign-in can feel snappier if your ISP's default DNS is slow or unreliable. What it does not do is lower your in-game ping. Once your console has resolved a game server's address and connected to it, DNS is out of the picture entirely — the actual gameplay traffic does not pass through a DNS server. Treat a DNS change as a small quality-of-life tweak for menus and connectivity checks, not a lag fix for gameplay itself.

Downloads, Rest Mode, and Other Devices

Consoles are notorious for downloading large updates silently in the background, including while in rest mode overnight, and a big download running during a match will absolutely produce lag spikes and packet loss for everyone on the network. A few habits fix this:

Pause manual downloads before playing. Check the download queue in the system settings menu and pause anything active.
Disable automatic background downloads during rest mode if you tend to play right after waking the console, or schedule play sessions after overnight updates have had time to finish.
Count every other device on the network. A phone backing up photos, a smart TV streaming 4K, a laptop syncing to the cloud, or a second console patching a game all compete for the same connection. Pausing them, even temporarily, often fixes lag that looked like an ISP problem.

Router Placement and QoS

Router position matters more than most players expect. Keep the router elevated, away from walls, and away from microwaves, baby monitors, and other 2.4 GHz devices that share spectrum with Wi-Fi. If the console is wired, the cable path matters less, but the router still needs a clear, central spot to serve every device in the home well.

If your router supports Quality of Service (QoS), use it to give your console's traffic priority over bulk downloads and streaming from other devices. Many modern routers include a "gaming" or "game console" QoS preset that automatically prioritizes low-latency traffic; enabling it prevents someone else's 4K stream or cloud backup from causing your ping to spike mid-match.

TV Settings: Game Mode and Display Input Lag

Since input lag is felt the same way network lag is, it belongs in a lag-reduction checklist even though it has nothing to do with your internet connection. Modern TVs apply heavy image processing — motion smoothing, noise reduction, upscaling — that can add dozens of milliseconds between the console rendering a frame and the screen displaying it. Game Mode disables most of that processing to minimize the delay.

Enable Game Mode specifically for the HDMI input your console is plugged into; it's usually a per-input setting, not a global one.
Turn off motion smoothing (often labeled "motion interpolation" or a brand-specific name) even outside Game Mode, since it is one of the largest single contributors to display lag.
If your TV and console both support 120Hz or VRR (Variable Refresh Rate), enable them — they reduce perceived stutter independently of network conditions.

How to Actually Measure What's Happening

Console connection tests are a good starting point but a limited one — they typically report a single ping number to one nearby test server and don't show jitter or packet loss over time, which are usually the more useful numbers for diagnosing multiplayer stutter. For a fuller picture:

Run the console's built-in connection test first as a sanity check, and note the NAT type it reports.
Test on a browser or phone connected to the same network using our ping test to see download, upload, ping, and jitter together, run two or three times for a reliable average.
Test while the console is idle, then again while it's actively downloading or another device is streaming, to see whether load on the network is causing the spikes you feel in-game.
Compare wired vs Wi-Fi results if you can temporarily plug in a laptop or phone near the console, to see how much of your lag is coming specifically from wireless variance.

If your browser test looks clean — low ping, low jitter, no packet loss — but a specific game still feels laggy, the cause is more likely NAT type, that game's matchmaking region, or server-side issues rather than your general connection. Our guide on what causes high ping covers the broader set of causes in more depth, including several that apply to consoles just as much as PCs.