In December 2012, we were working with a client whose website covered New Year’s Eve events. Demand was seasonal, so preparation needed to happen before the peak rather than after the site slowed down.
The client was preparing with a content delivery network. Our work included reducing time to first byte, the delay before the server begins sending a response. The original post reported an improvement, but the underlying measurements are not reproduced here, so this is a historical account rather than a current performance benchmark.
The useful lesson is to prepare the whole customer journey for demand. A page needs to respond, load its content and let visitors complete their task. Server response time is one part of that experience, not a substitute for measuring it end to end.
See site speed and business performance and conversion work.
Historical note: adapted from the December 2012 post. Original URL and publication date retained. This is not a current Melbourne event guide or a claim about the client’s present results.