Forum.Nokia.com
2.3.4 Infrastructure optimization
The latency between the WAP gateway and content server should be minimized. Each query traverses
this link twice, once as a request and once as a response.
The WAP gateway should be placed close to the GPRS gateway. (The GPRS gateway is technically called
a “Gateway GPRS Support Node,” or GGSN.) “Close” in this instance refers to both latency and the
probability of packet loss. Lost messages cause additional delays due to HTTP retransmission.
2.4 Site Organization
2.4.1 Doormat pages
It is not recommended to start the site using a doormat page, which serves no other purpose than to
perhaps greet the visitor and display a logo. It is better if the user can go to the service directly.
2.4.2 Login
Entering login information can be time consuming with a mobile phone. Login information should be
requested only once during the session, not each time after starting navigation from the main page.
Case-sensitive checking of user names and passwords should be avoided.
2.4.3 Detecting the browser
When using a modern Web site hosting environment, it is possible to detect the browser as well as
the language mode and supply the correct content transparently, without user interaction.
The Nokia Series 30 mobile browser sends a user agent field in the WSP header to the WAP gateway
when the content is fetched from the origin server. This user agent field can be used to define the type
of browser and then build a logic on the origin server to serve suitable content. From the WAP
gateway, it is then delivered inside the HTTP header.
2.4.4 Optimizing for size
Interactive pages should be short; informative pages, long. Having pages that are too short and
require many downloads is worse than having close-knit information on one longer page. In
particular, interactive pages with forms should not be too long, as users start to lose their feeling of
control if the form is more than two screenfuls. Empty rows can be misleading, as users may think
there is no more content below.
If, for example, a page contains a story or instructions, the entire content should be on one page.
Subtitles that take the user to points within a page help when browsing long, informative pages.
It is difficult to give hard and fast guidelines about how many links should be provided on one link list
page. If the links clearly belong together and are easy to browse (one line per link, in alphabetical or
other logical order), it is better to provide 30 links on one page than 5 links on six pages.
As for the total downloading time, some studies place an upper limit for acceptable delay on a PC-
based browser at 10 to 15 seconds, including all images. It is highly recommended to have a response
time (excluding connection time) of less than 10 seconds in a mobile environment.
WAP Service Developer's Guide for Nokia Series 30 Phones with WML Browser
9