incorporate Rob's feedback

Author: filipesilva

public/docs/ts/latest/guide/production-deploy.jade

@@ -52,6 +52,10 @@ a#dev-deploy
 
   The simplest way to deploy the app is to publish it to a web server
   directly out of the development environment.
+
+  It's not optimized and it won't be very fast for users.
+  But for some situations - like demos - all you need is to put your project online.
+
   It's already running locally. You're just copying it, almost _as is_, 
   to a non-local server that others can reach.
 
@@ -70,13 +74,17 @@ a#dev-deploy
 
   1. Enable production mode as [described below](#enableprodmode) (optional).
 
-  That's all it takes to publish your app!
+  That's the simplest deployment you can do.
+  It's not optimized, but it's online.
+
 
 a#node-modules
 :marked
   ### Load npm packages from the web (SystemJS)
 
-  The `node_modules` folder of _npm packages_ is huge and slow to upload to the server.
+  The `node_modules` folder of _npm packages_ contains much more code 
+  than what is needed to actually run your app in the browser. 
+  
   It's typically 20,500+ files and 180+ MB.
   The application itself requires a tiny fraction of that to run.
 
@@ -194,6 +202,11 @@ a#optimize
   Each tool does something different. 
   They work best in combination and are mutually reinforcing.
 
+  All of these work over your original source code, so don't forget to optimize that as well!
+  Don't use more libraries than you need to.
+  For libraries that allow you to import only parts of it, do so.
+  A good example is RxJs, where you can import operators individually instead of the whole library.
+
   You can use any build system you like.
   Whatever system you choose, be sure to automate it so that 
   building for production is a single step.
@@ -259,6 +272,9 @@ a#measure
   <a href="https://developers.google.com/web/tools/chrome-devtools/network-performance/understanding-resource-timing" target="_blank" title="Chrome DevTools Network Performance">
   Chrome DevTools Network Performance page</a> is a good place to start learning about measuring performance. 
 
+  Another good performance test is [WebPageTest](https://www.webpagetest.org/),
+  which you can also use it to make sure your deployment was successful
+
 a#angular-configuration
 .l-main-section
 :marked