From 963a9d5003756af10897c469af05d70585a42f90 Mon Sep 17 00:00:00 2001 From: Ben Schwarz Date: Thu, 29 Nov 2018 13:06:18 +1100 Subject: [PATCH] Updated article link to the canonical source (#1444) --- content/docs/optimizing-performance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/optimizing-performance.md b/content/docs/optimizing-performance.md index 3e5d8621..aaed723c 100644 --- a/content/docs/optimizing-performance.md +++ b/content/docs/optimizing-performance.md @@ -177,7 +177,7 @@ To do this in Chrome: 6. React events will be grouped under the **User Timing** label. -For a more detailed walkthrough, check out [this article by Ben Schwarz](https://building.calibreapp.com/debugging-react-performance-with-react-16-and-chrome-devtools-c90698a522ad). +For a more detailed walkthrough, check out [this article by Ben Schwarz](https://calibreapp.com/blog/2017-11-28-debugging-react/). Note that **the numbers are relative so components will render faster in production**. Still, this should help you realize when unrelated UI gets updated by mistake, and how deep and how often your UI updates occur.