Web Performance Best Practices. Serving Static Content from a Cookieless Domain - Ravelrumba. Serving static content from a cookieless domain is a standard performance best practice, one you’ve surely encountered if you’ve used a performance analysis tool like YSlow or Page Speed. The concept is simple—don’t serve static content like images and stylesheets from a domain that sets cookies—but exactly how to achieve this might not be clear to everyone.
And for beginners, both the concept and the execution can be slightly confusing. So here is a brief explanation of the idea, followed by a few options for implementing it. The trouble with cookies From a performance perspective, the trouble with cookies is that once the server sets a cookie for a particular domain, all subsequent HTTP requests for that domain must include the cookie. Of course, cookies are typically very small. But remember that this extra weight, however small, is added to every request. So how do we do it? I’ve emphasized the word “request”to highlight the fact that it’s only the request that matters. Using a CNAME. Automatically minify and combine JavaScript in Visual Studio. As you begin developing more complex client-side functionality, managing the size and shape of your JavaScript includes becomes a key concern.
It’s all too easy to accidentally end up with hundreds of kilobytes of JavaScript spread across many separate HTTP requests, significantly slowing down your initial page loads. To combat this, it’s important to combine and compress your JavaScript. While there are useful standalone tools and HttpHandler based solutions to the problem already, none of them work quite how I prefer. Instead, I’m going to show you my dead-simple method for automatically compressing and combining script includes. To accomplish that in this post, we will select a compression utility, learn how to use it at the command line, explore a useful automation feature in Visual Studio, and apply that to keep scripts combined and compressed with no ongoing effort.
Selecting a JavaScript compression tool The first thing we’ll need is a utility to compress our JavaScript. Conclusion. Speed Tracer - Google Web Toolkit - Google Code. Speed Tracer is a tool to help you identify and fix performance problems in your web applications. It visualizes metrics that are taken from low level instrumentation points inside of the browser and analyzes them as your application runs. Speed Tracer is available as a Chrome extension and works on all platforms where extensions are currently supported (Windows and Linux). Using Speed Tracer you are able to get a better picture of where time is being spent in your application. This includes problems caused by JavaScript parsing and execution, layout, CSS style recalculation and selector matching, DOM event handling, network resource loading, timer fires, XMLHttpRequest callbacks, painting, and more.
Ready to get started? For your convenience, here are some links to our documentation: Contribute! Speed Tracer is open source! Don't forget to join our google group! Google I/O 2010 - Measure in milliseconds: Meet Speed Tracer. Pagetest - where web sites go to get FAST! Godaddy windows shared gzip « myNotes. Referring to the article “Best Practices for Speeding Up Your Web Site” from YUI, Gzip compression reduces the response time. Gzip compression generally reduces the response size by about 70% and approximate 90% of today’s internet traffic travels through browsers. After searching around for answer on how to implement gzip compression on ASP.NET application, I found the solution below is the easiest to implement.
Add the configuration shown below in the in web.config file. This configuration setup enable gzip compression on static and on dynamic content. I have tried it on GoDaddy’s Windows Shared Hosting and it works fine. Enable Gzip compression in ASP.NET using web.config configuration. This implementation is confirmed with Firebug as shown in the snapshot taken below. I don’t get paid for writing blog posts. Check out what other says about this post by clicking at the title of this post.