diff --git a/benchmarks/README.md b/benchmarks/README.md
index 59887a9..2ef0fed 100644
--- a/benchmarks/README.md
+++ b/benchmarks/README.md
@@ -15,3 +15,8 @@ From that point every line of code was benchmarked against the budget and thrown
 Of course, memory usage has always been a big factor in this. The name µWebSockets is meant to signify "small WebSockets" and comes from the memory optimizations made throughout. Holding many WebSockets should not require lots of RAM.
 
 If you're looking for a performant solution, look no further.
+
+## Common benchmarking mistakes
+It is very common, extremely common in fact, that people try and benchmark µWebSockets using a scripted Node.js client such as autocannon, ws, or anything similar. It might seem like an okay method but it really isn't. µWebSockets is 12x faster than Node.js, so trying to stress µWebSockets using Node.js is almost impossible. Maybe if you have a 16-core CPU and dedicate 15 cores to Node.js and 1 core to µWebSockets.
+
+So whatever you do, it is of greatest importance that you actually **do check and make sure that µWebSockets is being stressed to 100% CPU-time** before noting the result. If it isn't, then you're not really benchmarking µWebSockets - you're benchmarking your client, trying to stress µWebSockets! Please don't make this mistake.