Change one variable. Record every condition.

Step 1

Describe the symptom before testing.

Record whether the problem is consistently high ping, short spikes, packet loss or disconnects, or desync while the displayed ping appears normal. These symptoms have different likely causes.

Step 2

Establish a baseline.

Keep the same device, connection method, game region and party host. Record at least two sessions instead of selecting the best run. Note household uploads, downloads and any known service incident.

• Record two baseline sessions under the same game server, device and connection conditions.
• For the comparison run, change only one variable and state that change.
• Keep the time window, visible symptom, ping range and loss or spike observations with the raw notes.

Step 3

Rule out causes a route cannot fix.

• Compare Ethernet with Wi-Fi where practical.
• Pause local uploads, cloud sync and downloads.
• Check the game publisher's official status or support source.
• Separate frame-rate or input delay from network delay.
• Repeat at another time before attributing a change to a tool.

Step 4

Publish the record, not a headline number.

A publishable result states the test date, region, ISP context, connection method, game target, sample count and all material limitations. It reports the typical result rather than the single lowest observation. Without that record, the page remains a method or troubleshooting guide—not a product verdict.

Download the blank CSV test log or use the local diagnosis tool to decide what to check first.