diff --git a/website/src/pages/docs/comparison.mdx b/website/src/pages/docs/comparison.mdx
index e5a00707e3..3aa2186832 100644
--- a/website/src/pages/docs/comparison.mdx
+++ b/website/src/pages/docs/comparison.mdx
@@ -6,6 +6,18 @@ import { Callout } from '@theguild/components'
 
 This comparison highlights the main differences when using Yoga instead of Apollo Server.
 
+### Better runtime performance
+
+GraphQL Yoga has significantly less latency and much higher requests rate than Apollo Server in all [popular benchmarks](https://github.com/graphql-crystal/benchmarks).
+including when using Apollo Federation - see benchmarks [here](https://github.com/ardatan/benchmarks/tree/federation#apollo-federation-server-benchmarks)
+| Name                          | Language      | Server          | Latency avg      | Requests      |
+| ----------------------------  | ------------- | --------------- | ---------------- | ------------- |
+| [GraphQL Yoga with Response Cache](https://github.com/dotansimha/graphql-yoga) | Node.js | http | 46.54ms | 2.2kps |
+| [GraphQL Yoga with JIT](https://github.com/dotansimha/graphql-yoga) | Node.js | http | 764.83ms | 120ps |
+| [GraphQL Yoga](https://github.com/dotansimha/graphql-yoga) | Node.js | http | 916.90ms | 100ps |
+| [Apollo Server](https://github.com/apollographql/apollo-server) | Node.js | Express | 1,234.12ms | 64ps |
+
+
 ### No Framework-specific Packages
 
 One of the goals of `graphql-yoga` is to have as few `graphql-yoga` packages as possible.
@@ -91,9 +103,6 @@ GraphQL Yoga only has a fraction of the dependencies of Apollo Server, and in ge
 
 GraphQL Yogas APIs are designed for code-splitting and thus have no side effects, where Apollo server specifies that is has side effects and thus, cannot be code splitted.
 
-### Better runtime performance
-
-GraphQL Yoga has significantly less latency and much higher requests rate than Apollo Server in all [popular benchmarks](https://github.com/graphql-crystal/benchmarks).
 
 ### GraphiQL