I have been paying a good amount of attention to
Speed, speedier and speediest!
The start of a new year is always a good time to begin something new. Google has
decided hinted that they’re going to begin giving higher page rank to faster web sites. This makes sense, I don’t want to click on the first result if it is dog-slow, I’d rather click on something almost equally relevant that is faster. As a developer, think about how you serve the requests that are made. According to Google, a page loading in 1.4 seconds isn’t even in the top 20% of all measured web sites and 3.2 second page load is in the bottom half.
Enable compression of the files you send
How do you do this? I’m not going to explain it when there are so many others already have (much better than I could too!). A simple search will give you plenty of results describing how to enable this with your specific server set-up. Even fellow blogger Keith Dahlby describes how to enable this in IIS.
Send fewer bytes per file
This one is beneficial two-fold. The first gain is going to be quicker downloads to the client and the second is that the browser can “paint” the page faster; especially if you’re doing any kind of DOM manipulation when the document is ready. This is also relevant for your images, the smaller the file size, the faster the download.
Minify JS and CSS files
I think it’s common for developers to look at server code when thinking about performance. Not only do you want your C#, Ruby or Java to run quickly, but also all the tiny pieces that tie things together. You’ll likely find bigger gains in some of these tips than in others, but even the little things can help you in the long run. Imagine increasing your traffic by twenty times? What about new features slowly adding more “bloat” to your pages? It’s the little things that can help combat those types of speed bumps.
That’s going to wrap it up for now, there will be more SEO tips for developers to come later. If you want to know more details of how I’ve accomplished these speed tips, hit me up on Twitter (@ChrisMissal) or leave a comment!
Also, here are some helpful links, use them, know them: