Currently there occurs 3 rendering cycles:
1. Server side rendered page which fails due to references to client location
2. New render after the user has been geolocated
3. New render after the itineraries have been found
Server side rendering should detect 'POS' reference in URL and render something appropriate. Optimally, there will be a single loading screen which changes to finished content after the ininerary search is ready.