In my opinion, minimising the time that content takes to appear on the average user’s browser (or range of browsers) should have the same sort of priority as reducing call waiting times in a customer services centre or ensuring diners are quickly seated at a restaurant. In all three of these cases, a faster time to deliver the service is what matters.
Speed counts… and in the case of a site that transacts, speed can have a real impact on the bottom line.
So what’s a fast page response time and what’s a slow one? The complex answer to this question is “its complex”, but luckily the simple answer is “it’s simple, there are several online sources to help you”. Including: http://pagespeed.googlelabs.com/ This is the first place I would visit to measure the speed of your website pages. The performance from Google is scored and suggestions given to improve your page speed in: high, medium & low priority (as well as other best practice recommendations). For example the homepage of http://www.idealinterface.co.uk/ gets a score of 85/100 http://pagespeed.googlelabs.com/#url=http_3A_2F_2Fwww.idealinterface.co.uk&mobile=false Note: You can currently only use this site to measure one page at a time. It is not possible (as far as I am aware) to record a series of actions.... such as a user’s typical transaction process through your eCommerce site.
So don't dismiss the subject of website performance. You may find it could mean the difference between a good website and great one.