[GMU Redux] Testing bandwidth and load times.
We’re in for some fun on this new experiment. Before digging too deep, let’s see how are the current state of affairs. First things first. The major target for the site being the Mauritian population. On its “About E-Government” page, the site states:
The vision of the Government is to provide an effective and efficient delivery of services, on a 24/7 basis, to citizens as well as to the business community. In this respect, the Government has invested in the necessary infrastructure, namely, the Government Online Centre and the Government Web Portal as a gateway to provide Government services online.
This calls for some thought. Delivering quality information first comes through delivering it easily. How are these services delivered then?
The loading time question.
The government website is a public service, hence needs to be effective and practical but the first thing that many users see of this website is the time it takes to load. So let’s dive into this.
Swift page loading is a must today. According to usability guru Jakob Nielsen, web users are ruthless, they have very little patience and page loading time is a huge drawback. (Source)
“People want sites to get to the point, they have very little patience,” he said.
[...]
Web users were also getting very frustrated with all the extras, such as widgets and applications, being added to sites to make them more friendly.
Such extras are only serving to make pages take longer to load, said Dr Nielsen.
Consequently, people get bored with the loading time of websites and end up not using the tools built for their own use. We should also take into consideration one important element, the evolution of bandwidth. With more and more bandwidth available, less time is needed to load a page. In the late 90s, a decent load time was tested and set at 7 seconds for a page on a 56 kb/s dialup. Today, this is measured in milliseconds and under 4 seconds for a page.
Load time testing.
So we did a small research on the website’s loading time. The government’s website has been tested on Pingdom Tools. On a T1-ADSL network, the site takes between 13-14 seconds to load. The full test is available here.
To get a clearer view, some Mauritian web users have been asked to test the site from different locations on the island. Here are the results:
Around 15 seconds on Orange ADSL 512 Kbps @ this moment(1.28 PM) on Chrome! Fond du sac North!
Source : on Twitter
Takes approx. 18sec to load www.gov.mu via Firefox/ Emtel Wimax
Source : on Twitter
My.T 512k. Actual speed is around 90kbps | Firefox 3.5.7 – 94s | Opera 10.10 – 102s | Location: Triolet
Source : on Twitter
The good, the bad and the ugly
The good thing is that, depending on the bandwidth, the site meets only nearly twice the late 1990′s recommendations, it might have been really bad. Who are we trying to fool here ?
The bad thing is that, on the actual standards of bandwidth consumption, the site is 4 or 5 times slower than what is usually seen around the web nowadays.
The really ugly thing about all this is the way local users have not been taken into consideration as well as availability. How? Some points discussed online.
Many Mauritians don’t have ADSL/My. T & Emtel. I expect it would take more time(over 4 mins) when being used on dial-up.
Source : on Twitter
A gross estimate is that there are around 400k Internet users in Mauritius… & around 60-70% of them are dial-up/Nomad users.
Source : on Twitter
As an aftermath, more than 50% of Mauritians need to wait over a minute to load the first page. Now that’s what cannot really be called service.
Sources
This loading problem on the website might have different sources:
- Server capabilities. The server can have difficulties delivering pages. Modern browsers also accept Gzipped pages, thing that the server does not actually do.
- Code. Messy code is present everywhere and each page is a great example of what should not be done.
- Seperation of content and layout. All are tightly mixed making it difficult to read for any browser.
- Excessive use of unnecessary javascript.
- Javascript not loaded in external files.
- Technology used. It seems that the portal runs on a java or ASP cms and that no page is optimised in terms of code. (Can someone confirm in the comments please?) Standard fast PHP and MySQL might be an interesting try.
SEO Friendly?
Ok, lets admit that some persons care about SEO for such a portal, why would it matter? Simply because people need to find the information. It comes to the quality of the information delivered. For the time being, no real user-centered information is delivered. Just have a look at how the site’s whopping near 60 000 pages look like when indexed in Google.
An example of SEO necessity can be a person having to re-issue his/her id card. Typing the term “mauritian identity card” in Google gives this:
Another fail maybe, but why take this into consideration? Google Webmaster Tools has been updated to include page performance tools. One new criteria in site crawling is now SPEED. This is linked to the load time problem. Another thing is that, content remains king and is a better king if easily found through search engines.
Let’s talk about this…
What is your experience of this site? Do you think that it would gain something with shorter load time? Do you think that the problem comes mainly from the site or your ISP?
Disclaimer
This project is an experimentation on how web users would like the Mauritian Government website to be. This is in no case a real life project. It is based on analysis and experimentation of concepts on the basis of the website currently in use. This project is in no way associated to the Government of Mauritius nor is it an official project. All the material used remains the property of their respective owners and no part of the posts published on the Web Design Bureau of Mauritius on this experiment can be copied or used without written consent of the Web Design Bureau of Mauritius.

































