Thanks for the new version! In a short test with game level "x seconds per move" I've noticed that the engine moves almost immediately (<1 second calculation time per move, no exceptions) although I've defined 5s and in another game 10s per move.
I many cases that expected. Time control is not very good yet so zurichess very conservative.
The engine estimates the time for each depth as previous-depth-time * branching-factor where branching factor depends on the number of pieces on the table (I use logN). So if you have 30 pieces and 5 seconds left zurichess will not search a new depth if 1s has already passed.
I did some changes after the last online blitz tournament which gave an ELO improvement of about 20.