Web Performance Journal #02

Web Performance Journal

Our second installment of the Web Performance Journal features information on SPDY, customer experience, and a fun tool to compare performance of two sites.

Goodbye SPDY

May 15, 2016 marks the 1 year anniversary of HTTP/2 RFC, it also marks the date when SPDY will no longer be supported by Chrome and Firefox. With browsers, servers and websites adopting HTTP/2 reducing the number of protocols support makes sense. The downside to this, is end users will see a performance hit when sites that they previously accessed via SPDY now revert to HTTP/1.1. According to W3Techs, today 6.7% of websites use SPDY.



Perfwars compares the performance of two sites in terms of page size, load time, and if certain optimizations are enabled. I have to admit that I had a lot of fun with the site, seeing how different sites compared in a head to head battle of performance. The data is broken down into usable and actionable items, displaying page weight by resource type and a list of files that are not optimized. This is a great tool to get a quick snapshot of how your site compares to a competitor. Bernie Sanders edges out Hillary Clinton in this battle.


Improving the Customer Experience

This article made me sad. In a survey of over 2000 company respondents only 4% indicated that making the customer experience as fast as possible was a priority. It was suggested that this meant that performance had been mastered which allows companies to focus on other value added areas. In my experience, site performance is not something that is mastered and can then be de-prioritized. Performance should always be at the forefront when developing new features or making any change. When performance is not considered there tends to be a regression in terms of performance. It’s great that organizations want to make applications personalized and valuable but doing so at the expense of performance may not improve the overall customer experience.

Come across an interesting article/anecdote? Share it with me @dparzych.

Learn more about Instart Logic: