Hi - we've noticed that redirect tests no longer work properly with the Chrome browser - the latency is so bad it's unusable. We never had this problem in the past, so wondering is anyone else has this problem?
Yes it's just Chrome - we've had this problem for several months now so we're using Google Experiments for redirect tests now. We understand that there will always be an element of page rendering with a redirect however it's so bad in Chrome that you can't use it as it would invalidate test results. You can see for yourself here and compare with Chrome and Firefox: http://www.avg.com/us-en/tnt-qa?q=u
I came across this post, and wondering if there is any learning that can be shared here. We experience similar issues with full page redirect tests in our company, the extended latency is impacting user experience and test data (e.g. double-counted impressions).
