How to fix CS2 lag, packet loss and rubber-banding
Turn on telemetry, reproduce the hitch and see what spikes when it happens.
Show ping, network problems and frame time
Open Settings → Game → Telemetry. Set the ping, network problems and frame time/FPS displays to Always while you test. Enable detailed network quality if you want to check packet loss and jitter separately.
A consistently high ping means replies take longer to come back. Jitter means the timing of those replies varies. If players jump backwards as the network readout spikes, start with the connection. If the whole view freezes and frame time shoots up while the network figures stay steady, try the same map in local Practice to see if you can reproduce it there.
Try two servers and change one thing
Play a few minutes on each of two nearby servers. From New Zealand, Sydney gives you a useful comparison when you’re playing with friends in Australia. Record the time, server address and what changed on the HUD. A single steady ping reading can miss the hitch you’re trying to catch.
If both servers hitch, pause downloads and cloud sync, then repeat. On Wi-Fi, try Ethernet if you can. If only one server hitches, compare notes with someone else on that server before changing your PC settings.
Test buffering if the network spikes persist
In Settings → Game, try one step more of Buffering to smooth over packet loss / jitter and repeat the test. Extra buffering adds delay. Put it back if it makes the game feel slower without reducing the hitches.