The free web debugging proxy for any browser, system or platform.
The websocket messages does not have any kind of incoming timestamp.
It would be good to have that for multiple reasons (performance measurement, order of messages etc)
It is what it is.
It should be 'timings' , not timers. Timers give wrong association.
Each WebSocketMessage has a Timers object; learn more here.
That said, there was a request to enable adding these as columns in the WebSocket Inspector for ease of reading; that seems like a fine idea.
Messages are presently ordered by ID; I believe that means that as the ID increases dtDoneRead will also be increasingly later.
You won't be notified about changes to this idea.