21 (More) Things to A/B Test

Optimizely published a list of 71 Things to A/B Test on their blog. It’s a pretty cool list. Here’s my additional 21 things you could consider testing if you’re hunting for inspiration:

  1. Wizards. For setup processes, checkouts or other long-ish flows, test a wizard-style UX vs one long ‘settings’ page.
  2. Surveys. If you’re running customer surveys A/B test different formats/lengths to find the best response rates before sending it to everyone.
  3. Symbols of trust. Split test landing pages that contain trustworthy symbols (such as industry affiliations, security checks, etc) to see whether the give your users more confidence in your product.
  4. Popups. Those things that pop up on the bottom right of your browser. Yes. They can be really useful for gathering feedback and subscriptions. Split test the content, visuals and time delay.
  5. Overlays. When clicking on a CTA test whether people will convert more if you take them to a different page or if you show them an overlay with the content/form they requested.
  6. Long-form vs. Short-form. Test out versions of your home page (or landing page) that are short and to the point vs. longer scrolling versions containing tons of content.
  7. Up-sell. When somebody’s about to check out or complete an action test out whether they’d be interested in a (relevant!) upsell. Eg, if I’m buying some bit of enterprise software I might be up for adding a premium support package. 
  8. Cross-sell. “People who bought this also really liked that.” Boom.
  9. Customer Support. If you offer post-sales product support try testing whether people convert more if you play it up on your landing pages or checkout process.
  10. Highlighted text. If you have long paragraphs try highlighting relevant parts in bold or a good background colour.
  11. Animations / Transitions. If things need to change on the page when the user makes an action (or moving to a different page) try using CSS animations to make the transition and experience smoother. If you confuse users less they might convert more.
  12. Rounded corners. Yup.
  13. Instantly Valuable CTA. OK, what I mean here is to try and deliver instant gratification to your users. For instance, Optimizely do a really nice job of this by asking you to simply plug in your website URL and without signing up or anything you can immediately start using the product.
  14. Shorter forms. Forms are necessary but the shorter they are the more likely your users will fill them in.
  15. Optional forms. Try testing making more items in your subscription forms optional.
  16. Phone numbers. Sometimes providing a prominent phone number gives customers the confidence that you’re a ‘real’ company.
  17. Company logo. We all want that branding but does it have to be that big? And colourful? :-) Try testing a smaller or monochrome version of your company logo to give more space to your content.
  18. Question CTAs. Try testing whether your visitors will convert more if you position your CTA text as questions. “Do you want to save money? <Yes!>”.
  19. Pricing. It’s perfectly ok to A/B test your product price to find the optimal price point at which people will convert.
  20. Features vs. Benefits. Are your customers in the market for a “backup and encryption tool” or “peace of mind”? Split test your message to find out which resonates more: features of your product or the benefits.
  21. Task vs. Goal. Let’s say you sell a live chat support product. The kind people embed on their sites for users to chat to a rep. Are you selling to your customers the “ability to integrate live chat easily” (task) or the possibility of “being in touch with customers 24/7″? This is subtly different to #20 but quite similar I admit. Anyway, just test it :-)

Feel free to split test me on Twitter.

Interview: How Paul Jarvis works with Jetpack

Originally posted on Jetpack for WordPress:

We got in touch with one of our users Paul Jarvis to find out what he thinks of the Jetpack plugin – how it has helped him and what he’d like to see in a new version. Paul is a freelance web designer/developer as well as an author of various popular books who’s been using WordPress since before he was born.

Paul lives in British Columbia, Canada. You can stalk him on Twitter @pjrvs or read about his books and work on his website.

Who is Paul?


What do you do for a living?

I’m a freelance web designer/developer and author. I’ve built websites for 20 years and written books for the last 4.

What’s the best thing about your job?

I can set my own hours and stop working when I’ve made enough for the year (typically 3-4 months off per year).

How did you first start using…

View original 494 more words

Top 5 Best Practices when using Jetpack on client websites

Originally posted on Jetpack for WordPress:

If you’re creating WordPress websites for clients, Jetpack is for you. Jetpack easily adds a great number of features to your client’s websites without the need for a dozen different plugins, reducing the technical debt that you or your client will need to maintain over time.

We recommend these best practices when using Jetpack for a client site that will keep things running smoothly and help you provide a great service to your clients.

This article covers:

  1. Use Jetpack’s Development Mode
  2. Invite your client to connect to WordPress.com
  3. Activate Jetpack only on the live domain
  4. Use your account when a connection is required
  5. Work with staging sites
  6. How to install Jetpack

1. Use Development Mode

Jetpack offers a Development Mode that is enabled when using Jetpack on a localhost. If you’re developing on a development server, you can manually enable development mode.

You can enable this as constant in…

View original 756 more words

terminal copy

Git and GitHub Tutorials

I’ve not used Git or GitHub much in the past except for checking out stuff. I’ve been getting up to speed on how it all works and found the following tutorials extremely useful:

  • The Simple Guide to Git
    This is great if you’re either already familiar with Git and/or are comfortable with command line apps. I found this to be really useful as a crib sheet.
  • GitHub for Beginners
    A 2-part, step-by-step tutorial that could easily be called “GitHub for Dummies”. I skipped over most of this but I think it does a really good job of explaining stuff in layman’s terms.
  • Pro Git
    A full-length online book (free) that covers everything.
  • Git Reference
    And finally this is a full reference of all Git commands and their options.