Wikipedia and Google are fast - close to desktop rates. Amazon isn't - and ITT is certainly stretching the limits, but then it is a page with an almost infinite number of elements to be rendered.

In my opinion we see several issues there:

1. The Microb engine applies rendering as it goes, so that complex pages with multiple nested containers embedded imagery get rerendered many times. Opera was better there, as it showed a mostly plain rendition in process, applying the bulk of styles only after all elements were loaded.

2. The tight WiFi power management increases latency on Maemo compared to desktop/laptop OSes - whenever the latencies incurred in page rendering slow the loading of consecutive embedded elements beyond breaks of more than 200ms, the WiFi will get sent asleep, so that it has to be awakened for fetching each image, adding further delays to each request.

3. Bad page design - that ITT as a site catering for a handheld device renders worse than the arguably awful online-version-of-a-Walmart-flyer Amazon implies that the ITT stylesheet and layout urgently need tuning. Even more so as the alternative "mobile" versions are by now so out of date that they can hardly be used to access the site any more. Unfortunately MicroB can't make use of user style sheets so far, so that has to be fixed by the site operators.