About a year ago (July 2015) we ran a webinar with Rick Still from the FT about their journey to move their new site to full HTTPS delivery. Once that had been done they turned on h2 delivery and had some early indicators of performance improvements.
One year down the line I am speaking to more and more customers where making the move to HTTPS is only just happening. The carrot for a lot of this is the performance gains on offer by h2, the additional features of server push that are getting more attention and other features such as Service workers, Geo location services and improved SEO rankings.
A/B testing has become popular among many websites and many customers. However the client side solutions introduce performance delays so the whole process has always felt wrong to me. If you care about conversion so much that you want to optimise the usability as much as possible, why would you sacrifice performance and the negative affects on conversion in order to “hopefully” find this out?
How much does it cost me, the consumer, to browse poor mobile websites? As well as the obvious performance issues costing me time, browsing large pages ends up costing me money! Having had the pleasure of experiencing two train delays in the last week I have now been presented with the dreaded message below:
Part 1 – Defining the problem
Is optimising a website the same as decorating a rundown old house?
Obviously not, you would be a fool to think so, but in many ways there are some similarities and I’m not talking about the obvious pun of time to first paint!!
Identify a Global Event – TICK
Reserve advertising budget – TICK
Secure advertising space – TICK
Forget to check your website is performing well …. DOH!!!!