Measure first. Change one thing.

Find what
is waiting.

“Lag” can mean a late response, uneven frames, a crowded connection, display processing, or a device running out of room to work. The useful fix starts with naming the delay.

Interaction pathone symptom ≠ one cause
INPUTresponse
FRAMEdisplay
PACKETreply
STORAGEready

The delayed event determines what you should measure.

Symptom router

What does the delay look like?

Choose the closest observation. You do not need to know the cause yet.

Evergreen reference70 sources · 13 chapters

The long view

Faster machines.
Different clocks.

From time-sharing terminals and television scan cycles to network queues, touchscreens, audio buffers, and cloud rendering: the history of lag is a history of complete interaction paths.

The reference explains what engineering actually shortened, what it chose to hide, and why averages often miss the pause a person notices.

The Lag Repair method

A fix should leave evidence.

01

Describe the event

“The character moves backward online” is testable. “My computer is bad” is not.

02

Change one variable

Preserve the conditions that matter so the comparison can teach you something.

03

Keep every outcome

Improved, unchanged, worse, and inconclusive results all narrow the next question.

Read how we research and test →

A better stopping condition

Not zero lag.
A result you can defend.

Know what changed, what remains unexplained, and whether the next step is another comparison, a support report, or simply stopping.

Begin with the symptom