Two Different Problems With the Same Name

Players call everything "lag," but there are two distinct faults with two unrelated fixes. Input lag is local: the delay between your hand moving and the screen updating, caused by your peripherals, frame rate, and display. Network lag is remote: the delay and unreliability between your machine and the game server, caused by your connection and route. The fastest way to tell them apart is to check whether the problem survives with the server removed from the equation — if the game feels heavy in an offline practice mode or even in the menus, it is not your internet.

The Five-Minute Diagnostic

Run these in order. Each one narrows the answer, and the whole sequence takes less time than one match.

Move the mouse in the main menu. No server is involved. If the cursor or camera feels smeared, delayed, or disconnected from your hand, the problem is entirely local — display processing, frame rate, or the input path.
Play an offline mode. A practice range, a bot match, a single-player campaign, or a training room. Aim at a static target and flick between two points. Heavy, floaty aim here is input and render latency, full stop.
Watch the in-game ping counter while it feels bad. If the number stays flat at 30 ms during the exact moment things feel wrong, the network is not the cause of that moment. If it jumps to 200 ms or the connection icon appears, it is.
Watch other players, not yourself. Enemies teleporting, sliding, or snapping back to a previous position is a network symptom. Your own crosshair feeling weighty while everyone else moves smoothly is a local symptom.
Test the connection idle and under load. Run a browser latency test with the network quiet, then again while a large download runs. A number that is fine when idle and terrible under load points at queueing in your own connection rather than a bad route.

Symptom to Cause Table

What you observe	Most likely side	Why	First thing to try
Menus and cursor feel delayed	Input or display	No server involvement at all	Enable game mode on the display, check refresh rate is set correctly
Aim feels heavy offline as well as online	Input or render	The local chain is the only common factor	Raise and stabilise frame rate, disable traditional V-Sync
Enemies teleport or rubber-band	Network	Their position updates are arriving late or not at all	Check for packet loss and jitter, get on a cable
Your own character snaps back after moving	Network	Client prediction being corrected by the server	Same as above; look for loss on the upstream path
Shots that clearly hit register nothing	Usually network	Lag compensation working from a stale or inconsistent view	Reduce jitter and loss before anything else
Everything is smooth but consistently a beat late	Either — depends on magnitude	Stable delay can come from a distant server or from display buffering	Compare offline feel against online feel
Fine for twenty minutes, then a burst of chaos	Network	Congestion, interference, or a background transfer starting	Test under load, check who else is using the connection
Worse only in the evening	Network	Shared capacity peaks at predictable hours	Compare readings at different times of day
Worse after a graphics setting change	Render	New GPU bottleneck deepening the frame queue	Cap frames slightly below maximum, lower one heavy setting
Mouse feels fine wired, mushy wireless	Input	Radio scheduling and power saving on the peripheral link	Use a dedicated dongle or a cable rather than Bluetooth

The Local Suspects Worth Checking

Four local causes account for most complaints that turn out not to be the internet.

Display processing. Televisions apply motion interpolation, noise reduction, and colour processing that hold frames for tens of milliseconds. Game mode disables most of it. This single toggle is the largest free latency win available to console and living-room PC players, and it is routinely left off.

Refresh rate not actually set. A 144 Hz monitor connected over the wrong cable or left at a default 60 Hz output is common. Check the display settings in the OS, not the box the monitor came in.

V-Sync and frame pacing. Traditional V-Sync can buffer multiple frames and adds delay you feel immediately. If you have a variable refresh rate panel, use it with a frame cap a few frames below the maximum. If you do not, uncapping frames usually feels more responsive at the cost of tearing.

Wireless peripherals. A dedicated 2.4 GHz gaming dongle is close to wired in practice. Bluetooth is not designed for it and can add noticeable, variable delay, especially with power-saving enabled. Peripherals also drift as batteries drain, and polling rate sometimes drops in low-power modes — worth checking when a mouse that used to feel sharp no longer does.

The Network Suspects Worth Checking

Network lag has three separable components, and knowing which one you have determines the fix.

High but steady latency. Usually distance and routing. If the server is 5,000 km away, physics sets a floor that no router setting improves. The fix is choosing a closer region where the game allows it.
Unstable latency, or jitter. Delay that swings from packet to packet. Games handle steady delay far better than variable delay, so this feels disproportionately bad. Wireless links and congested uplinks are the usual sources — our comparison of Wi-Fi versus Ethernet for gaming covers why a cable helps here more than it helps the average.
Packet loss. Data that never arrives. Produces teleporting, missed hits, and warning icons. Even one or two percent is enough to ruin a competitive match while leaving a speed test looking perfect.

If your latency is fine when the network is idle but collapses the moment anyone starts a download or an upload, you have bufferbloat: oversized queues in your router or modem holding packets rather than dropping them. It is one of the most common causes of "my internet is fast but my game lags," and it has a specific fix described in our guide to what bufferbloat is. If instead the baseline is fine and you get sudden isolated jumps, the pattern-matching in our guide to fixing ping spikes is the better starting point.

Confirming the Network Side Properly

Measure twice, in two conditions, and write both numbers down.

Idle baseline. Close background applications, pause cloud sync and game updates, get every other device off the network if you can, then run a browser latency test. Note the typical value and how much it varies between samples. This measures warm HTTPS round trips to nearby cloud endpoints rather than in-game packets, so read it as a calibrated proxy — it will sit slightly above a raw ICMP ping, but it is consistent across runs.
Loaded test. Start a large download or upload, wait for it to reach full speed, and run the same test again. A jump from 25 ms to 200 ms under load is a queueing problem inside your own connection, and it is fixable.
Repeat at a different hour. If evening readings are consistently worse than morning readings, the cause is shared capacity during peak time, not your equipment.
Change one thing, then retest. Cable instead of wireless. Router queue management enabled. A different server region. Changing several variables at once guarantees you learn nothing.

When Both Are True

The reason this diagnosis frustrates people is that both problems frequently exist at once. A player on a 60 Hz TV with motion smoothing enabled and a congested wireless link has perhaps 60 ms of avoidable local delay stacked on top of an unstable connection. Fixing only one leaves the game still feeling wrong, which makes it easy to conclude the fix did not work.

So work the chain in order, cheapest first: display settings, then frame rate, then input path, then the connection. Test after each change using the same method, and keep the improvements that survive a real match rather than the ones that look good in a menu. If you are still unsure which side you are dealing with after all of this, the common cases and their answers are collected in our latency FAQ.