Add a response delay#

A fixed delay in milliseconds is added to every response, which surfaces races, loading states, and client timeouts.

The Response Delay field in the settings menu adds a fixed delay, in milliseconds, to every response before the proxy returns it to the client.

How the delay is applied#

A value of 0 disables the delay.
The proxy applies the delay per response, not per session, so a page that loads twenty assets pays the delay twenty times.
The proxy adds the delay after the server replies and before it hands the response back.

When a response delay helps#

Simulate slow networks: a 500 ms response delay surfaces races and loading-state bugs that never trigger on localhost.
Investigate timeouts: a delay that exceeds a client timeout reproduces the timeout reliably without a change to the server.
Test skeleton loaders: a few hundred milliseconds is usually enough to see whether a placeholder UI renders correctly.

Set the delay#

Enter a number in the field next to the ms label. GraphDagger saves the value immediately. Set it back to 0 to remove the delay.

For per-rule throttling (different delays on different endpoints, separate download and upload caps, fixed latency components), use the Throttle Bandwidth action in a rule instead.