@@ -54,13 +54,13 @@ at once, consider the [Chrome Tracing] tool.
54
54
Chances are that your app could be a little leaner, faster, and generally less
55
55
resource-hungry if you attempt these steps.
56
56
57
- 1 ) [ Carelessly including modules] ( #1-carelessly-including-modules )
58
- 2 ) [ Loading and running code too soon] ( #2-loading-and-running-code-too-soon )
59
- 3 ) [ Blocking the main process] ( #3-blocking-the-main-process )
60
- 4 ) [ Blocking the renderer process] ( #4-blocking-the-renderer-process )
61
- 5 ) [ Unnecessary polyfills] ( #5-unnecessary-polyfills )
62
- 6 ) [ Unnecessary or blocking network requests] ( #6-unnecessary-or-blocking-network-requests )
63
- 7 ) [ Bundle your code] ( #7-bundle-your-code )
57
+ 1 . [ Carelessly including modules] ( #1-carelessly-including-modules )
58
+ 2 . [ Loading and running code too soon] ( #2-loading-and-running-code-too-soon )
59
+ 3 . [ Blocking the main process] ( #3-blocking-the-main-process )
60
+ 4 . [ Blocking the renderer process] ( #4-blocking-the-renderer-process )
61
+ 5 . [ Unnecessary polyfills] ( #5-unnecessary-polyfills )
62
+ 6 . [ Unnecessary or blocking network requests] ( #6-unnecessary-or-blocking-network-requests )
63
+ 7 . [ Bundle your code] ( #7-bundle-your-code )
64
64
65
65
## 1) Carelessly including modules
66
66
@@ -418,7 +418,6 @@ As of writing this article, the popular choices include [Webpack][webpack],
418
418
[ performance-cpu-prof ] : ../images/performance-cpu-prof.png
419
419
[ performance-heap-prof ] : ../images/performance-heap-prof.png
420
420
[ chrome-devtools-tutorial ] : https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/
421
- [ chrome-tracing-tutorial] :
422
421
[ worker-threads ] : https://nodejs.org/api/worker_threads.html
423
422
[ web-workers ] : https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers
424
423
[ request-idle-callback ] : https://developer.mozilla.org/en-US/docs/Web/API/Window/requestIdleCallback
0 commit comments