Documentation

Steps Required to Run the Application

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

Optimzations made

index.html

  • Moved external CSS to internal CSS stylesheet
  • Removed external font reference
  • Made getting Google Analytics JavaScript library async

views/js/main.js

  • changePizzaSizes : Changes made to prevent FSL based on https://www.youtube.com/watch?v=C7HqMCCQok4. Removed redundant document.querySelectorAll(".randomPizzaContainer") and unecessary logic that accesses offsetWidth multiple times.
  • updatePositions : Moved call to scrollTop outside the loop
  • DOMContentLoaded event listener : Reduced number of image elements to 31 since only 31 are displayed on the screen

/views/images/pizzeria.jpg

  • Created different sized versions

Original README

Website Performance Optimization portfolio project

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.

Getting started

Part 1: Optimize PageSpeed Insights score for index.html

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 the top-level of your project directory 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.

Optimization Tips and Tricks

Customization with Bootstrap

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