4 Seconds Loading Time Is Maximum For Websurfers

nieske writes "Of course we all want webpages to load as fast as possible, but now research has finally shown it: four seconds loading time is the maximum threshold for websurfers. Akamai and JupiterResearch have conducted a study among 1,000 online shoppers and have found, among other results, that one third of respondents have, at one point, left a shopping website because of the overall 'poor experience.' 75% of them do not intend ever to come back to this website again. Online shopper loyalty also increases as loading time of webpages decreases. Will this study finally show developers of shopping websites the importance of the performance of their websites?"

Comments

tabs

[Kuciwalker]

It takes a lot longer than 4 seconds for a Slashdot story to load, particularly with the new AJAXy discussion system. I usually open up several things at a time in different tabs, which decreases the average loading time since I can read one thing while another loads. What browser were these people using?

Re:tabs

[init100]

It takes a lot longer than 4 seconds for a Slashdot story to load, particularly with the new AJAXy discussion system.

Slashdot does not use AJAX, just some Javascript, for the new discussion system. In essence, the only thing it does is hide all posts until you click on its header to expand it. The posts are there anyway, loaded along with the rest of the page. That way, it uses about the bandwith of the nested option, while presenting it as a dynamic threaded view. If they used AJAX, it would (probably) send an asynchronous query to the Slashdot servers asking for precisely the post you try to open. That does not happen, I checked tcpdump myself.

Had they really used AJAX, a comment thread might have been a lot quicker to load initially, but slightly slower loading each post.

Who is conducting that study?

[Anonymous Coward]

Note that Akamai has a vested interest in this study. They would like to encourage more businesses to use their technology so that their sites load faster.

I am not saying that the study is biased, but one should at least consider that it is in Akamai's best interest to convince every site owner that they will lose customers if their site is not fast enough.

Re:Who is conducting that study?

[SkunkPussy]

4s seems remarkably high!

I get frustrated by a delay of even 1s.

Only four seconds?

[BenoitRen]

Sounds to me like people are getting really impatient these days. I'm willing to wait up to 10 seconds to let a page load, and if it still hasn't, but is busy (instead of connecting again) I load another tab and occupy myself with something else.

However, four seconds sounds accurate for how long to wait until the page -starts- to load. If I have to wait longer than 4 seconds just to connect to a web server, I start to get impatient. If it takes much longer, I'll come back to it later and go do something else.

I call bullshit

[Deagol]

If the hyper-caffeinated, sugar-popping, MTV-watching, blipvert-desensitized ADD kids of today can tolerate the glacially loading site known as MySpace, I'd bet dollars to donuts that the slightly older, credit card-holding demographic of online shoppers gladly tolerate more than 4 seconds on we sites, and do so without much prejudice.

Either the summary is totally off, or this 'research' is total bunk.

Re:I call bullshit

[ScentCone]

I'd bet dollars to donuts that the slightly older, credit card-holding demographic of online shoppers gladly tolerate more than 4 seconds on we sites, and do so without much prejudice

I think it all comes down to what the site is doing, and how readily available another, virtually identical site (or range of merchandise, at similar prices, etc) actually is. The more sites there are that present and transact the same things in essentially the same way, the more that things like raw speed differentiate one from another. The more unique something is (niche merchandise, a blog with a particular perspective), the more patience people will have. Those things are nearly impossible to quantify, and thus you get largely BS, context-less reports like the one being discussed. I think that the larger conclusion ("people are less patient than they used to be") is valid - but pretty hard to nail down, in terms of specific seconds, for specific demographics, on particular platforms, across particular pipes, under certain seasonal circumstances, blah blah blah.

Why I leave..

[nolife]

Wow, a web caching company has determined that customers abandon a site that is slow.

That is not an issue for me. My highest chance of leaving is determined by when in the buying process, the site provides total price including all shipping, handling, taxes, and acceptance of coupons codes. If they need my name and address I may leave depending on if they have a shipping link or general shipping info somewhere on the site that I can reference first. I will ALWAYS leave if they require CC or payment information before providing the total price or even a hint of shipping costs.
I guess they need my address prior to calculating shipping and handling charges if they do not have flat rates but a place to enter my just my zip code should be enough IMHO.

For a good example of providing a good experience is NewEgg. They includes the shipping costs right next to the product descriptions without even having to go to a cart first.

I view the delay or confusion of shipping and handling charges to be an attempt to hide a total cost or get you to get so far that they figure you will not back out. I will back out and take my business elesewhere.
Almost like the the Ebay sellers that charge $20 to ship a motherboard (at least they are up front about it though).

Re:AJAX completely lacks performance.

[inKubus]

It's pretty easy:

If you're application uses a lot of repeated screens and is really only a data-view and entry application, you should go AJAX. Because the slightly longer initial load time (to load ALL the interfacey stuff) is better than having to rerender the interface over HTML every time you change views.

If it's a step by step wizard type thing, or informational (think wikipedia) just get on with it using syncronous web pages.

Where AJAX fails is in the hands of inexperienced developers, where they won't allow the app to load almost everything before running. This is not always possible--something like google maps is a good example of this. You are going to have to load the maps as you go because there's too much data. However, google maps really relies on Images as data which is not the most efficient. They need to expand their client to render the maps itself from GIS info (obviously the satellite overlay will need to come from images).

Also, it fails when there is a high latency connection. However, a lot can be learned from past interfaces: feedback! Flash a div on the screen letting the user know it's loading, apply visibility:hidden when it's done. As long as the user knows that it's actually DOING SOMETHING and not just sitting there, they will give it the benefit of the doubt and wait. Test the connection latency at startup and then let the user know what you know. If you tell them in advance that they might experience poor performance because of their current connection, they are more likely to tolerate it.

Good interface design is a lot more than having it be fast. You have to keep the user informed of the current situation. It's not slowness that annoys people so much as not knowing what's going on. Early X windows had that problem for me also. Whereas in Windows when you click something the window immediately is created by GDI while the actual application loads, in X the appliation is started somewhere and then IT creates it's own window. So when you click on an Icon, it takes a few seconds of nothing (it seems) while we wait for the kernel to find on FS, allocate memory for and run the executable which does it's own init and then FINALLY pops up it's window. If you're running over a network connection, there's no disk noise to let you know anything is happening, so you are basically just sitting there wondering if you should click again. I don't know if it's still like this.

Anyway, my point is that there are a lot of tricks you can use to prevent user annoyance because it goes a lot further than some arbitrary time length.