• Download or fork the application from here
• Select index.html to start the app
• You can find a version of the app running here

Optimizations include:

• Minification of html, css and js files to minimize the number of critical bytes
• JS asyncronous fetching of files
• Use of media queries to download only necesary stylesheets
• Inlined CSS to minimize the critical path length
• Compression and resize of images
• JS excecution optimizations

Optimizations are marked as comments with ***

Installing Grunt

You will also need to install the following plugings:

• grunt-responsive-images

npm install grunt-responsive-images --save-dev

• grunt-contrib-uglify

npm install grunt-contrib-uglify --save-dev

• grunt-contrib-cssmin

npm install grunt-contrib-cssmin --save-dev

• grunt-contrib-htmlmin

npm install grunt-contrib-htmlmin --save-dev

• grunt-pagespeed

npm install grunt-pagespeed --save-dev

Alternatively use load-grunt-tasks to load your plugins.

require('load-grunt-tasks')(grunt);

You also need to install either GraphicsMagick or Imagemagick CLI tools.

Your challenge, if you wish to accept it (and we sure hope you will), is to optimize this online portfolio for speed! In particular, optimize the critical rendering path and make this page render as quickly as possible by applying the techniques you've picked up in the Critical Rendering Path course.

To get started, check out the repository and inspect the code.

Some useful tips to help you get started:

1. Check out the repository
2. To inspect the site on your phone, you can run a local server

$> cd /path/to/your-project-folder
$> python -m SimpleHTTPServer 8080

1. Open a browser and visit localhost:8080
2. Download and install ngrok to make your local server accessible remotely.

$> cd /path/to/your-project-folder
$> ngrok http 8080

1. Copy the public URL ngrok gives you and try running it through PageSpeed Insights! Optional: More on integrating ngrok, Grunt and PageSpeed.

Profile, optimize, measure... and then lather, rinse, and repeat. Good luck!

####Part 2: Optimize Frames per Second in pizza.html

To optimize views/pizza.html, you will need to modify views/js/main.js until your frames per second rate is 60 fps or higher. You will find instructive comments in main.js.

You might find the FPS Counter/HUD Display useful in Chrome developer tools described here: Chrome Dev Tools tips-and-tricks.

• Optimizing Performance
• Analyzing the Critical Rendering Path
• Optimizing the Critical Rendering Path
• Avoiding Rendering Blocking CSS
• Optimizing JavaScript
• Measuring with Navigation Timing. We didn't cover the Navigation Timing API in the first two lessons but it's an incredibly useful tool for automated page profiling. I highly recommend reading.
• The fewer the downloads, the better
• Reduce the size of text
• Optimize images
• HTTP caching

The portfolio was built on Twitter's Bootstrap framework. All custom styles are in dist/css/portfolio.css in the portfolio repo.

• Bootstrap's CSS Classes
• Bootstrap's Components