How to analyze your sites speed and make it faster?

30 Aug 2019
6 min read

Today, our users have no patience for websites with poor screen load speeds. They just naturally expect the pages they visit to load fast and run smooth. Your web pages need to not only load quickly, but also run well; that means scrollinganimations and interactions should be silky smooth.

Fast display speed is the key to success with your website

Industry case studies have also proven the fact that high-performing sites engage and retain users better than low-performing ones.

So how do you get started with Optimisations on the Web?

Improving page speed isn’t some arcane and mysterious dark art. The very first step in improving your page speed is to measure current performance and analyze where and how you can make positive changes. You can simply use Chrome Dev tools to understand how your page is loaded on client’s system.

To understand this auditing process better let’s take an example page from and see what can be improved in order to load it fast for users.

Below is a Premium Member’s profile page on

Profile Page from Premium CarouselProfile Page from our Premium Carousel

To learn the page load time of the targeted page, I inspected the page loading performance in all the three different tabs in network tab, performance tab and audit tab available in Chrome Dev Tools.

Page Load analysis in Network , performance and Audit Tab:

Page Load analysis in Network , performance and Audit TabPage Load analysis in Network , performance and Audit Tab

Page Load analysis in Network , performance and Audit TabPage Load analysis in Network , performance and Audit Tab

Page Load analysis in Network , performance and Audit TabPage Load analysis in Network , performance and Audit Tab

All the above output flows helps you know the Page Load Journey of your page. Loading a web page is like a film strip that has three key moments.

Is it happening? | Is it useful? | And, is it usable?

Page Load analysis in Network , performance and Audit Tabimage via

By analysing Http calls you can easily make out that biggest drain on performance of your page is due to the need to complete dozens of network round trips to retrieve resources such as styles, scripts, data and images. So, the next step is figuring out how to load just what you need.

The above outputs enable you to find out what all resources are being requested, their priorities, how many bytes are being downloaded and if there are any unwanted network requests / js and css code which you can eliminate.

Here are a few proven tips which you can use to optimize your website and improve its overall quality and performance.

  1. Minify the js and css assests
  2. Load optimized Images
  3. For Single-page applications use code-splitting
  4. Async / defer js scripts that are not necessary for initial page render
  5. Use Sprited Images for small icons to reduce individual network calls.
  6. Avoid redirects
  7. Don’t load Full libraries (e.g. all of lodash, Moment + locales), load only what you need using tree shaking
  8. Use resource hint link like a dns-prefetch, preconnect, prefetch

and follow the Audit Mantra – Test , Record , Fix and Repeat

Record the state of your site before making any changes, to uncover problems and set a starting point for improvements or regressions. This will give you the feedback you need to show results and justify the development effort.

The example page we picked up in this post is already optimized for fast Page load with code splitting, loading compressed versions of js and css , async loading of js, tree shaking and much more. But everyday we write so much of code to add new features and bring easy and convenience to our users, we bloat the page again with unnecessary code and assets. Hence it’s important to perform health check of your website on regular basis.

Optimization opportunities I noticed while re-auditing

  • A few new small icons are added on page UX but are being downloaded on separate network request. We can do image spriting there.
  • An API call is made to fetch various counts like count of new matching profile , count of near me matches, etc… but these are not even displayed anywhere on the page may be as a need of new UX design of the page. We can get rid of these extra call save 1.40 sec

Extra Api CallsExtra Api Calls

  • An API call is made to fetch recent success stories but again this item is not displayed on this page may be as a need of new UX design of the page. We can remove this extra call also and save on downloaded bytes and time.
  • Render blocking resource section in Audit tab tells the poly-fills used to support es6 and flex box on old browsers is blocking page render. We can optimize this to load when necessary, skip it for modern browsers for faster load times ( sample code shown below) and can save extra 12 KB (minified version) download taking 1,200 ms on modern browsers.
    '<script src=",fetch"></scr' +
  • Audit tab also guided us to use preconnect for domains we are connecting for API calls or tracking.

<link rel="preconnect"> informs the browser that your page intends to establish a connection to another origin, and that you’d like the process to start as soon as possible.

  • Audit tab also highlighted the main thread is taking more time in script Evaluation and it’s 3,972 ms. We can use code coverage tool to remove unused css and js.

Don't forget to check code coverageDon’t forget to check code coverage

Code coverage is a feature in DevTools that allows you to discover unused JavaScript (and CSS) in your pages

The goal, as always, should be to enable users to interact with your site with the least amount of friction. So run the smallest amount of JavaScript necessary to deliver real value.

Go Audit Today and Boost the Performance of Your Site
Go Audit Today and Boost the Performance of Your Site


Image credits: