web-optimization

Website Performance Optimization

Project @Udacity #frontendnanodegree

Step 1: Critical Rendering Path (CRP) Optimization

Scope: Optimize PageSpeed Insights score of at least 90 for Mobile and Desktop for index.html.

Defined the CRP Metrics and optimized them by:

• reducing the number of critical resources
  • removed render-blocking analytics.js JavaScript by adding async attribute to its script tag.
  • removed render-blocking google fonts + style.css CSS by moving them to the bottom of the HTML.
• reducing the number of critical bytes of critical resources
  • used Grunt build tool to perform optimization such as minification of CSS and JS and image optimization (see Step4 for details).
• hence, shortening the critical path length

Index.html now measures a score above 90 on PageSpeed Insights for both Mobile and Desktop devices.

Step 2: Frame Rate Optimization

Scope: Optimize views/js/main.js to make views/pizza.html render with a consistent frame-rate at 60fps when scrolling.

Changes made on views/js/main.js file:

• Calculated dinamically the number of pizzas needed to fill the screen, based on browser window resolution.
• Used document.getElementById() and document.getElementsByClassName() Web API calls throughout the code instead of document.querySelector() and document.querySelectorAll(), respectively; a faster way to access the DOM.
• Fixed the major forced synchronous layout (FSL) issue by defining document.body.scrollTop / 1250 outside the loop, as its value do not depend on the number of targeted elements.
• Also, moved document.getElementById("randomPizzas") and document.getElementById("movingPizzas1") outside the loop so they will get to make only one DOM call.
• Declared the phase and elem variables outside the for loops preventing them from being created every time the loop is executed.
• Stored items.length into a local variable for a more efficient iteration.
• Added backface-visibility: hidden on the mover class in views/css/style.css file, so the backside of the rotated elements are not going to be painted when scrolling the page.

Now, views/pizza.html renders with a consistent frame-rate at 60fps when scrolling.

Step 3: Computational Efficiency

Scope: Using the pizza size slider on the views/pizza.html page, resize pizzas in less than 5ms.

After tracing and idetifying the performance issue in DevTools/Timeline, I found that an FSL was causing the high resize time of the pizzas.

Changes made on resizePizzas function in views/js/main.js:

• Fixed FSL by refactoring changePizzaSizes function, reducing repetition of code and by switching offsetWidth calculation from px to %; also,
• Switched to document.getElementById() and document.getElementsByClassName() Web API calls for a faster access of the DOM.
• Stored randomPizzas.length into a local variable for a more efficient iteration.
• Time to resize pizzas now is less then 1ms.

Step 4: Minification of CSS and JS, and Image Optimization

Scope: Download, configure and implement task runner on the project using Grunt.

How to run Grunt on this project?

• Download the project assets and make sure src folder, Gruntfile.js and package.json files are under one folder.
• Open your terminal window.
• Ensure that you have the npm package manager or Node.js installed and up-to-date by running npm update -g npm.
• Install Grunt’s command line interface (CLI) by running npm install -g grunt-cli.
• Since, Gruntfile.js and package.json are already configured for the project with the needed tasks and Grunt plugins –> you are ready to run Grunt:
  • Go to the project’s root directory in your terminal.
  • Install project dependencies by running npm install.
  • Run Grunt with grunt.