diff --git a/docs/index.md b/docs/index.md
index d4a06fac1..da7d2dc72 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -139,13 +139,12 @@ Want to see your company here? [Submit a PR](https://github.com/zio/zio-kafka/ed
 
 ## Performance
 
-By default, zio-kafka programs process partitions in parallel. The default java Kafka client does not provide parallel
+By default, zio-kafka programs process partitions in parallel. The default java-kafka client does not provide parallel
 processing. Of course, there is some overhead in buffering records and distributing them to the fibers that need them.
-On 2024-11-23, we estimated this overhead to be 1.2 ms per 1k records
-(comparing [benchmarks](https://zio.github.io/zio-kafka/dev/bench/) `throughput` and `kafkaClients`, using the standard
-GitHub Action runners (4 cores), and with the Kafka broker in the same JVM). This means that for this particular
-combination, when processing needs more than 1.2 ms per 1k records, a zio-kafka based program will have **higher
-throughput** than a program based on a java Kafka client.
+On 2024-11-23, we estimated that zio-kafka consumes faster than the java-kafka client when processing takes more than
+~1.2ms per 1000 records. The precise time depends on many factors. Please
+see [this article](https://day-to-day-stuff.blogspot.com/2024/12/zio-kafka-faster-than-java-kafka.html) for more
+details.
 
 If you do not care for the convenient ZStream based API that zio-kafka brings, and latency is of absolute importance,
 using the java based Kafka client directly is still the better choice.