This is a battle against front-end performance. There are tons of practical and hands-on front-end optimisation techniques in ASP.NET MVC based on Page Speed. Nevertheless, these techniques are not restricted to ASP.NET MVC only. You can draw on these experience in other sort of web projects as well.
Introduction
This is a battle against front-end performance. There are tons of practical and hands-on front-end optimisation techniques in ASP.NET MVC based on Page Speed. Nevertheless, these techniques are not restricted to ASP.NET MVC only. You can draw on these experience in other sort of web projects as well.
Battle I
Synopsis
According to Best Practices for Speeding Up Your Web Site, 80% of the end-user response time is spent on the front-end. Most of this time is tied up in downloading all the components in the page: images, stylesheets, scripts, Flash, etc. So it's bother-worthy to put attention on the front-end, though, there are also a lot of things need to handle in the back-end. This post will talk about several performance pitfalls in the browser and the steps to address them in ASP.NET MVC.
Battle II
Synopsis
In the post, "Front-line of Front-end, Rational Front-end Performance Tuning in ASP.NET MVC, I", I have illustrated a way to rationally increase front-end performance. However, we still have some debts remained. Basically, we made a sensational improvement on HTTP Request and File Size, which was reduced by 97% and 71% separately. The score evaluated by Page Speed was raised from 73 to 81.
Battle III
Synopsis
This is the last post in this series. The aim of this post is to eliminate performance pitfalls all the way. We will discuss the respects of Combining CSS files, Minifying html, Minifying CSS file, Minifying JavaScript file, and Utilising CDN. I intend to get a perfect 100, but finally I found it’s not a piece of cake.
posted on
