This Week in Website Performance

weeklyThis Week in Website Performance is a weekly feature of the blog. It summarizes recent articles about website performance. Why? Because your friends at care.

Are you making any of these 8 common (and wrong) assumptions about mobile performance?

Author: Tammy Everts.

There are a number of best practices you should be following when optimizing pages for mobile devices. This insightful article details a number of incorrect assumptions which impact such a process. A solid understanding of the state of mobile browsing is given, as well as tips on where to focus to make effective positive changes to your mobile site’s performance.

Five Steps for Travel Sites, Mobile and Web Performance

Author: Ori Zaltzman.

Gogobot is a travel website which is relatively resource-heavy. Their focus on performance at all times has resulted in a site which performs very well. This article delves into their 5 tips for performance that can work for most sites. One of the tips is to not use CDNs for dynamic content and there is a recommendation how to accomplish this.

3 Fixes for Common Mobile Banking Performance Problems

Author: Penny Crosman.

Mobile banking app usage is on the rise, mirroring all online mobile activity. This article discusses three issues to mobile banking that can be relevant to any other industry. Tips on improving download speed, avoiding app crashes, and glitches due to device diversity apply to any site. While many may shrug these issues off as out of their control, there are ways to influence these apparently external problems with great design.

Making The Web Faster With SPDY

Author: Matt West.

If you are using SPDY or thinking about using it to compress your site download, you may have questions about how it works or how to implement it on apache or nginx. If so, then this is the article for you! From outlining how SPDY fits into the stack architecture to how it unpacks content on the client side, this comprehensive treatment covers all the bases regarding how SPDY works, and then shows the step (that’s right, one step) needed to implement server-side.