625791 - [Fx4Launch] Push new non-fx homepage test winner live

Status: VERIFIED INVALID

(www.mozilla.org :: General, defect, P1)

Description

[Laura Forrest]

We're currently testing the following non-fx homepage versions:

http://www.mozilla.com/en-US/firefox/new/curly.html
http://www.mozilla.com/en-US/firefox/new/creatures.html
http://www.mozilla.com/en-US/firefox/new/button-top.html

Please push the winner live on our 1.1 release. 

Blake - can you update test results here when test is done? Code freeze for 1.1 is next Thursday, so would be great to have results in by then, if possible. 

Thanks!

Comment 1

[Laura Forrest]

Blake - can you confirm that we're currently testing the URLs above?

Comment 2

[Blake Cutler]

The experiment is running.  I added a Firefox 4 Beta link to the variations in order to keep consistency with the control.

Comment 3

[Laura Forrest]

Thanks Blake - looks like we won't have results until next week. Moving this to the 1.2 release (but perhaps pushing the new page can simply be a one-off task).

Comment 4

[Laura Forrest]

Hey Blake - How close are we to having stat sig results?

Comment 5

[Laura Forrest]

Results from this test are in and the "Creatures" version performed at the same level as our current page and has more of a warm brand welcome. It will also match the creatures used throughout the rest of the site (mobile, plug-in check, SUMO, About).

http://www.mozilla.com/en-US/firefox/new/creatures.html

Since this is a test version it'll need a couple of WebDev tweaks before it can go live. That includes:

1. Include the link to the Beta below the download button (please keep the same tagged destination URL too, as always)

2. Extend the bottom gradient line below the graphic out further like on our live site. Not sure if you need a modified graphic to do so. 

3. Add the download counter number below the graphic. The most current number is 716,524,654 (that's 3.5 only). The daily feed is here: https://metrics.mozilla.com/stats/firefox_downloads_total.json While piping in the daily feed would be great, feel free to just use that exact number if that is too time consuming. Note though, we would like to use the live number come Fx 4 launch.  

4. Not sure if you need a Mac/PC graphic - I believe we used both in the tests so we should have those. LMK if I should hunt them down.

Let me know how I can help here.

Comment 6

[John Slater]

+1

Thanks!

Comment 7

[James Long (:jlongster)]

For #2, the gradient line is part of the image:

http://mozcom-cdn.mozilla.net/img/home/screenshot-main-mac.png

So we'll need new graphics, probably just do the same with the new image.

For #3, the new page does include the counter, the live page is the one that does not, so is it just that the number needs to be updated?

Comment 8

[Michael Morgan [:morgamic]]

Have we done any qualitative testing?  Might be a good opportunity to use answerlab or something similar to quantify actual reactions to the design.

From what I see it's a lateral move, so we're putting work into getting us to where we already are.  Ideally we could find a design that performed better where users had a measured positive response to it.

Comment 9

[John Slater]

We'll have to update this page with Fx4 copy for the launch very soon anyway, so let's merge the two projects - that way we'll reduce the amount of churn for WebDev and we'll have the page refreshed with the product release.

Moving to 1.4.

Comment 10

[Anthony Ricaud (:rik)]

James, please use yottaa.com or webpagetest.org to check performance regressions with the current online version.

I've already added http://www.yottaa.com/url/www-trunk-stage-mozilla-com-4d5b14daabe5cb5f1d00019b and http://www.yottaa.com/url/www-mozilla-com-4d5b151dabe5cb5f2300014b

The goal on this page is to display the download button as fast as possible so I think the live counter should be loaded after onload. You can use the same sysem nav-main.js is using to load.

Comment 11

[James Long (:jlongster)]

(In reply to comment #9)
> We'll have to update this page with Fx4 copy for the launch very soon anyway,
> so let's merge the two projects - that way we'll reduce the amount of churn for
> WebDev and we'll have the page refreshed with the product release.
> 
> Moving to 1.4.

Are you saying this should be launched with the firefox 4 launch?

I agree with morgamic that I'm not sure why we would use this if our current page performs the same.

Comment 12

[James Long (:jlongster)]

Tagging this with the fx4 launch since those pages might be changed

Comment 13

[Laura Forrest]

(In reply to comment #12)
> Tagging this with the fx4 launch since those pages might be changed

Yes, this bug will be changing for the Fx4 launch. See Bug 634135 for details.

Comment 14

[John Slater]

Since this bug is starting to bleed into the "prep the homepage for launch" bug (bug 634135) I'm going to close this one down so we can continue the discussion in one place.

Thanks!