We are in the midst of some infrastructure improvements. This is split among a variety of improvements – performance, security, maintainability, availability, and staying on the most current technology.
We did a set of improvements in our caching and server connections that improved the core response time of a race page load from 140 milliseconds to 100 milliseconds. While that is a lot, the web application is actually one of the minor delays in seeing a web page load. The overall page load time to users is about 1 seconds on fast internet and modern computers.
As you can see from the chart below, the actual web application is only about 10% of the page load time that a user sees. Much of it is network, and browser (DOM processing) rendering and display. Given that mobile is over 60% of the traffic, the overall average page response time is 2.29 seconds.
Here is a nice diagram that explains the amount of time it takes a web page to load:
We have done a lot of optimization all along this chain with things like high-speed content delivery networks, utilizing browser caching, and displaying the right size image for the display (smaller resolution for smaller screens saves network load time).
We know that having a quick website for your race is important and our continual improvements keep you in the fast lane. That is why we keep track of the milliseconds – so you don’t have to…