Yeah, I was about to say, delay monitoring would be easy if a hidden input value of the timestamp was used. It can be easily spoofed, but if you wrote your own very simple function to encrypt/obfuscate the original timestamp like Martijn suggested, most spam bots probably wouldn't be able to figure that out. But maybe I shouldn't underestimate spam bots.