Cloudflare edge testPerformance, not guesswork
Call of Duty / Warzone connection check.
Test your connection, then follow the game-specific fixes and settings below.
Jump to the full guide ↓Call of Duty / Warzone: fix lag, high ping and packet loss
Diagnose packet burst, high ping and rubber-banding in Call of Duty and Warzone without confusing a network problem with a PC hitch.
Find out what is actually lagging
A packet-burst warning is a reason to investigate, not proof that your ISP is dropping packets. Note whether latency or loss rises at the same moment, whether the frame rate falls, and whether your squad sees the same hitch. A fast download result alone cannot identify which of these is responsible.
High ping or jitter
Actions arrive late, or delay fluctuates. Compare the in-game latency reading with your usual baseline.
Packet loss
Updates may be missing and movement can snap back. Look for a loss reading, not just a low average ping.
Low FPS or input delay
A choppy image or delayed controls can come from the device or display. Check an offline/local mode when available.
Settings worth checking in Call of Duty / Warzone
Menu names can change with patches, editions and platform. Use the controls available in your build; do not apply PC-only instructions to a console.
Latency and packet-loss telemetry
Use the settings search, if available, to find Telemetry. Enable Server Latency and Packet Loss when your title exposes them. Labels and availability differ between COD releases and platforms.
What it does: Shows what happens during a match; it does not change the connection.
On-Demand High-Quality Streaming
In current COD content settings, open Menu → Manage Files → Graphics. Select Minimal under On-Demand High-Quality Streaming. Older releases may call it On-Demand Texture Streaming.
What it does: Reduces streaming bandwidth at the cost of texture quality. It is not a guaranteed packet-burst fix.
Frame-rate and graphics settings
On PC, choose a frame-rate cap the machine can sustain, then lower demanding graphics options if frame time spikes. Change one setting and repeat a comparable match.
What it does: Helps rendering consistency; it cannot repair network packet loss.
PC troubleshooting, step by step
- Pause downloads in every launcher you use, including Steam, Battle.net and the Xbox app, and pause cloud backups. Launch one COD installation and complete any required update before comparing results.
- If the problem begins immediately after a game or driver update, let any displayed shader-preparation process finish. Use the launcher's supported verify/repair option if loading problems persist; avoid deleting random cache folders.
- Compare a stable frame-rate cap with your normal settings. If the camera hitches while latency and loss remain steady, investigate CPU/GPU load, temperature and background recording before changing router settings.
Console support and fixes
- On PlayStation or Xbox, pause downloads and capture uploads, then compare a wired session with your usual connection. Check that the console is actually using Ethernet rather than a saved Wi-Fi network.
- Compare an offline or local mode, when your COD title provides one, with an online match. Delay in both points toward display/controller or rendering issues; online-only disruption needs the network and service checks.
- Use the television's Game Mode for display delay. A supported high-frame-rate mode can improve response, but neither option changes server ping.
Check the console connection itself
PS5: Settings → Network → Connection Status → Test Internet Connection. Xbox: Settings → General → Network settings → Test network speed & statistics. Other models can use different labels. These tests assess platform connectivity, not your game's exact match server.
Record errors and NAT warnings if joining or party chat fails. NAT changes are not a general cure for high ping. Avoid DMZ mode or opening ports without a diagnosed need and the platform's own guidance.
A controlled checklist for ping spikes and loss
- Record a baseline. Note your game mode, platform, time, connection type and the in-game reading. Run RaceMyNet outside a match. Keep two or three results rather than relying on one unusually good test.
- Remove local wireless uncertainty. Compare Ethernet directly to the main router where possible. A cable into a wireless mesh satellite may still use a wireless backhaul. If Ethernet is unavailable, compare close to the main router.
- Pause heavy traffic. Stop downloads, cloud backups and livestream uploads across the household for one comparison. If lag disappears only when traffic stops, investigate congestion and your router's supported queue-management options.
- Check the simple physical causes. Reseat Ethernet plugs, try a known-good cable or another router port, and restart network equipment once using its manufacturer's instructions. Do not factory-reset it as the first step.
- Change one thing and retest. Compare similar matches at your normal playing time. Keep improvements that repeat. A faster DNS service, a VPN or more Mbps is not a guaranteed reduction in game-server ping.
Prefer the game's own loss display for game traffic. If RaceMyNet reports an HTTPS fallback, request failures are not a direct measurement of the game's UDP packet loss.
If Call of Duty / Warzone still has connection problems
- Compare several matches at the same time of day. A single bad lobby cannot establish a permanent home-network fault.
- Record the exact COD title, playlist, platform, time and warning shown. Warzone and annual COD releases can have different issues; report the relevant title rather than just 'COD lag'.
If several games and devices struggle on a wired connection, give your ISP the times, results and affected services. If only this game or mode is affected, start with the publisher's support and service information below. Include the platform, region, timestamps and a short clip of the indicators. Share diagnostic logs privately through official support.
Will Minimal texture streaming fix packet burst?
It can reduce one source of background traffic, so it is worth a controlled comparison. If packet burst remains, inspect frame times and match telemetry. It does not prove that the cause is streaming, or that the game server and ISP route are healthy.
Official guidance and further help
Menu instructions were checked against the publisher guidance below. General comparison steps are troubleshooting suggestions, not a promise of a particular ping or a guaranteed fix.
Use the test as a baseline. Verify the result in your game.
A browser test and a game match use different servers. Compare repeat measurements, in-game indicators and the same playing conditions before deciding whether a change helped.