Performance optimization

· by Göran Svensson · Read in about 2 min · (396 Words)

Static website service performance improvements

We have made significant performance improvements in our static website service and have dug deep into everything on the client and server side. All images are now sent with Cloudinary’s Akamai CDN including the favicon, and every CSS, HTML and Javascript file are compressed and minified.

Speed Index

We use webpagetest for our performance tests. As a measure of how one experiences the web page speed we use Speed Index. The Speed Index is the average time at which visible parts of the page are displayed. It is expressed in milliseconds and dependent on the size of the viewport.

Speed Index Reference Results We have now also separated the routes for the front page and the Angular app. The Angular app is now between the median to 10th percentile compared to the reference speed index, which is as good as it can get. Our front page which we want to be as quick as possible is now below the 10th percentile 6 of 8 times.

Angular app (Appernetic Static website Generator service) performance test from:

Front page performance test from:

Our uptime monitoring with Pingdom also shows that the we are on the right track now. For the front page, we now have the performance grade 92 of 100. Google PageSpeed Insights shows 67 of 100 for mobile devices and 87 of 100 for computers.

Response time diagram last 24 hours Response time diagram last 24 hours for the Angular app.

Pingdom test result logs for the Angular app (Appernetic static website service) Pingdom test result logs for the Angular app (Appernetic static website service).

Caching

Caching with CloudFlare is improving. Once the cache has been properly warmed up, it will even be better than this.

Appernetic static website service, caching with CloudFlare Appernetic static website service, caching with CloudFlare.