A set of benchmark and profiling tests recently done by the Webkit dev team (see below)

image: webkit.org
has been highlighting several interesting technological limitation that will play a major role in future development and hosting of web applications over the two sides of the south pacific.
This research is showing that the higher your connection bandwidth is, the more significant is the latency effect on the initial page load time.
This means that with the growing demand for rich user experience web application (made available due to improved ADSL/Cable end user internet connection across the OECD) the effect of being far from target audience markets will posses more technological challenges for achieving the same result available by overseas competitors.
Industries that utilizes overseas web marketing for Australian and NZ products will now need to put more thought into distributed application that will place the static and large content across different servers around the globe in order to achieve the same user inexperience available by North American, European and Asian competitors.
Some of those solutions may include utilizing CDN storage technologies and advance techniques of http caching methods.
When trying to summarize the key requirement for serving rich user experience apps to a London customer from a AU/NZ server over the southern cross cable, these will probably be the key considerations:
- Small HTML/XHTML file: other component within they page could not start loading until the initial landing page has been fully parsed.
- Try to avoid calls to the back-end database where possible, the faster your page will render and released over HTTP, the less latency your overall page load will experience.
- Get your static content (JS/CSS and images) as close as possible to the end user or at least set long expiry headers to those objects, the more popular your pages will become the higher the chances they will be cached somewhere down the stream.
- minimize the number of total files per page, web browsers are limited to a fixed number of concurrent HTTP requests, once exceeded, your browser will queue the pages for download until the next available sliding frame even if it will have available bandwidth for those requests, this could be achieved by grouping the different JS libraries and CSS styles into single files and using icons within sprites instead of dedicated image files.
- Geo locate your incoming request and when possible rewrite the media files URLs to near by servers or at least less media intensive pages (a good example could be setting the number of paginated media catalog items for less images per page for far clients).
Additional on going New Zealand latency issues are going to be addressed within this research post