In a meeting today, a client said they wanted a single-page checkout
process. The checkout tunnel is an area that I prefer to have as
vanilla as possible so that customers have no surprises, but I am
open to change.
I've never done any testing on one-page vs. staged checkout, and I
haven't been
Single-page checkout generally results in lower conversion:
http://econsultancy.com/blog/3095-gap-com-s-single-checkout-not-a-good-idea-report
http://www.getelastic.com/ecommerce-checkout-report/number-pages-ecommerce-checkout-process/
I think the real question is whether the customer wants
I have read reports that go in both directions. My personal
experience has favored certain implementations of single page
checkout.
I think the question cannot be simply single page vs. multi
page checkout. The total experience brings in a lot of variables.
I have implemented single-page
Also, split testing should take into account the potential confusion
for customers, at both the design stage, and on the software layer.
Split Test Accelerator and Google Website Optimizer will load a
cookie that is used for the duration of the experiment, to ensure
returning visitors will see
Read: The number of steps perceived doesn't need to translate
into pages let alone entire page reloads.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=46724
I feel a BLOG post coming on this one...
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=46724
Welcome to the Interaction Design Association
