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?"
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?
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.
Now that this research is in, I predict that all website designers will realize the futility of flashy designs and instead remake their sites to be more like Craigslist or Google. I'm predicting an end to Flash and Javascript.[/naivete]
Apology to Ubuntu forum.
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.
Either the summary is totally off, or this 'research' is total bunk.
Method of processing duck feet
One of the main reasons why I'm considering upgrading my 233-MHz laptop, is not because it's slow at doing heavy calculations (like Matlab, etc), but because it will soon to be impossible to surf the 'net. Not only are webpages growing larger and larger kB-wise, but they're also using increasingly more CPU resources when loading. Why is it necesary for my poor laptop to run at 100% CPU usage for a long time, just because I want to view a website? When gmail just came out it worked perfectly fast on my computer, but more and more javascript have been stuffed into it, so now it's almost useless for me. The tendency is same for many, many websites.
But for me the ability to sort through goods is the #1 priority. Yes I like to have a pretty site to look at but if I cannot find what I am looking for with a few simple queries then I am gone. Newegg is a fine example of a site where I can find what I want quickly. Tigerdirect is getting better. Dell is the worst. I have a theory that Dell is like many supermarkets, they rearrange stuff and make searching difficult so you see the maximum number of items before finding what you are actually looking for.
Web designers, if you want business, make it easy. I dont really think most people go to sites just to browse. Most of the time we are there with a purpose and as an ADD generation we want it quickly or we will move on.
CS: It is all sink or swim...oh and did I mention there are sharks in that water?
I'm on dial-up so I expect some long load times. However, if I get a flash webpage, I close it - I'm not messing about waiting an age for it to load. I'm not looking for some crappy 'multimedia experience' - I just want information, to buy something or whatever. I'm getting Broadband soon and I'll still be closing anything flash sites, no matter how fast they load. It's the web equivalent of powerpoint poisoning, and the worst thing is virtually every flash page I've seen hasn't been skippable.
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).
Bad boys rape our young girls but Violet gives willingly.
I'm here waiting for the thread to load up, click reply and decide to wri.. oooh, shiny thing!
Task Mangler
This is one tool I really find useful for Firefox:
https://addons.mozilla.org/firefox/433/
If you can't stand flash, then its for you.
Jumpstart the tartan drive.
From the Wikipedia page about XMLHttpRequest:
I don't know what the fuck you're talking about, and I don't think you do, either. Of course Internet Explorer supports AJAX. If it didn't, serices like GMail wouldn't have even been created in the first place. You do realize that the vast majority of the people in the world use IE, right? You won't see a technology become as widespread as AJAX has become if Internet Explorer doesn't support it.
This is a nonsensical thing to say. It all depends on what you are doing. Ajax can significantly increase performance too. Remember when GMail was first launched? The #1 thing everybody said was that it was fast. Why? Because it used Ajax.
Without mentioning what those systems were using Ajax for, there is zero useful information there. It's certainly possible that Ajax decreased performance in these cases, there's plenty of people throwing Ajax at things where it just isn't useful just because it's the buzzword du jour. On the other hand, there's also plenty of people using it as just another tool, and getting decent performance and usability improvements out of it.
In short: "Ajax completely lacks performance" == stupid. "Ajax harms performance when used to do [x], [y] or [z]" == useful information.
Bogtha Bogtha Bogtha
Registration causes me to abandon online store sites. I have a credit card. We've been working out the bugs for 50 years. Credit card sales work pretty well already. I am not going to waste a lot of time registering for your damn website in order to qualify to spend my money with you. Sorry. If you really really really really really really want me to do your market research for you I demand a discount - maybe free shipping, which is my other pet peeve. It really doesn't cost $15 bucks to pick, pull and pack that widget. I'll trade a few seconds of load up time for that. Now get to work assholes. I'm the customer, not you.
Will this study finally show developers of shopping websites the importance of the performance of their websites?
Developers already know this. But at the end of the day, we're paid to implement the ill-considered plans of marketers and designers.
Proud member of the Weirdo-American community.
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.
Cool! Amazing Toys.