nodejs · RafaelGSS · Nov 15, 2022 · Nov 10, 2022
diff --git a/documentation/poor-performance/README.md b/documentation/poor-performance/README.md
@@ -1,30 +1,3 @@
 # Poor Performance
 
-In this document you can learn about how to profile a Node.js process.
-
-- [Poor Performance](#poor-performance)
-  - [My application has a poor performance](#my-application-has-a-poor-performance)
-    - [Symptoms](#symptoms)
-    - [Debugging](#debugging)
-
-## My application has a poor performance
-
-### Symptoms
-
-My applications latency is high and I have already confirmed that the bottleneck
-is not my dependencies like databases and downstream services. So I suspect that
-my application spends significant time to run code or process information.
-
-You are satisfied with your application performance in general but would like to
-understand which part of our application can be improved to run faster or more
-efficient. It can be useful when we want to improve the user experience or save
-computation cost.
-
-### Debugging
-
-In this use-case, we are interested in code pieces that use more CPU cycles than
-the others. When we do this locally, we usually try to optimize our code.
-
-- [Using V8 Profiler](./step1/using_v8_profiler.md)
-- [Using Linux Perf](./step2/using_linux_perf.md)
-- [Using Native Tools](./step3/using_native_tools.md)
+See: https://github.com/nodejs/nodejs.org/tree/main/locale/en/docs/guides/diagnostics/poor-performance
diff --git a/documentation/poor-performance/case_study.md b/documentation/poor-performance/case_study.md
diff --git a/documentation/poor-performance/step1/using_v8_profiler.md b/documentation/poor-performance/step1/using_v8_profiler.md
diff --git a/documentation/poor-performance/step2/using_linux_perf.md b/documentation/poor-performance/step2/using_linux_perf.md
diff --git a/documentation/poor-performance/step3/using_native_tools.md b/documentation/poor-performance/step3/using_native_tools.md