diff --git a/docs/content/en/docs/benchmarks/_index.md b/docs/content/en/docs/benchmarks/_index.md
deleted file mode 100644
index 22ec2f5ff98..00000000000
--- a/docs/content/en/docs/benchmarks/_index.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: "Benchmarks"
-icon: "resources"
-weight: 4
-description: >
-  This section presents benchmarks used to test Tetragon.
----
-
-Tetragon benchmarks are run per release to ensure overhead created by Tetragon
-is within expectations.
diff --git a/docs/content/en/docs/getting-started/enforcement.md b/docs/content/en/docs/getting-started/enforcement.md
index 73f078e3c88..9b5fe019ff7 100644
--- a/docs/content/en/docs/getting-started/enforcement.md
+++ b/docs/content/en/docs/getting-started/enforcement.md
@@ -193,5 +193,4 @@ using policies. Some useful links:
 
 To explore details of writing and implementing policies the [Concepts]({{< ref "/docs/concepts" >}}) is a good jumping off point.
 For installation into production environments we recommend reviewing [Advanced Installations]({{< ref "docs/installation" >}}).
-For a more in depth discussion on Tetragon overhead and how we measure system load try [Benchmarks]({{< ref "docs/benchmarks" >}}).
 Finally [Use Cases]({{< ref "docs/use-cases" >}}) and [Tutorials]({{< ref "docs/tutorials" >}}) cover different uses and deployment concerns related to Tetragon.