Stay organized with collections
Save and categorize content based on your preferences.
Wednesday, December 21, 2011
As the team responsible for tens of thousands of Google's informational web pages, the
Webmaster Team is here to
offer tips and advice based on their experiences as hands-on webmasters.
If you've never tested or analyzed usage of your website, ask yourself if you really know whether
your site is useful for your target audience. If you're unsure, why not find out? For example, did
you know that on average users scroll down 5.9 times as often as they scroll up, meaning that
often once page content is scrolled past, it is "lost?"
(See Jakob Nielsen's findings on scrolling,
where he advises that users don't mind scrolling, but within limits.)
Also, check your analytics—are you curious about high bounce rates from any of your pages,
or very short time-on-page metrics?
First, think about your user
The start of a web project—whether it's completely new or a revamp of an existing
site—is a great time to ask questions like:
How might users access your site—home, office, on-the-go?
How tech-savvy are your visitors?
How familiar are users with the subject matter of your website?
The answers to some of these questions can be valuable when making initial design decisions.
For instance, if the user is likely to be on the road, they might be short on time to find the
information they need from your site, or be in a distracting environment and have a slow data
connection—so a simple layout with single purpose would work best. Additionally, if you're
providing content for a less technical audience, make sure it's not too difficult to access
content—animation might provide a "wow" factor, but only if your user appreciates it and
it's not too difficult to get to the content.
Even without testing, building a basic user profile (or
"persona")
can help shape your designs for the benefit of the user—this doesn't have to be an
exhaustive biography, but just some basic considerations of your user's behavior patterns.
Simple testing
Testing doesn't have to be a costly operation – friends and family can be a great resource. Some
pointers:
Choosing your testers: A range of different technical ability can be useful,
but be sure to only focus on trends—for example, if more than 50% of your testers have
the same usability issue, it's likely a real problem—rather than individual issues
encountered.
Testing location: If possible, visit the user in their home and watch how they
use the site—observe how they normally navigate the web when relaxed and in their natural
environment. Remote testing is also a possibility if you can't make it in person—we've
heard that Google+ hangouts can be used effectively for this
(find out more about using Google+ hangouts).
How to test: Based on your site's goals, define 4 or 5 simple tasks to do on
your website, and let the user try to complete the tasks. Ask your testers to speak aloud so
you can better understand their experiences and thought processes.
What to test: Basic prototypes in clickable image or document format (for
example, PDF) or HTML can be used to test the basic interactions, without having to build out a
full site for testing. This way, you can test out different options for navigation and layouts
to see how they perform before implementing them.
What not to test: Focus on functionality rather than graphic design elements;
viewpoints are often subjective. You would only get useful feedback on design from quantitative
testing with large (200+) numbers of users (unless, for example, the colors you use on your
site make the content unreadable, which would be good feedback!). One format for getting some
useful feedback on the design can be to offer 5-6 descriptive keywords and ask your user to
choose the most representative ones.
Overall, basic testing is most useful for seeing how your website's functionality is
working—the ease of finding information and common site interactions.
Lessons learned
In case you're still wondering whether it's really worth research and testing, here are a few
simple things we confirmed from actual users that we wouldn't have known if we hadn't sat with
actual users and watched them use our pages, or analyzed our web traffic.
Take care when using layouts that hide/show content: We found when using
scripts to expand and collapse long text passages, the user often didn't realize the extra
content was available—effectively "hiding" the JavaScript-rendered content when the user
searches within the page (for example, using Control + F, which we've seen often).
Check your language: Headings, link and button text are what catches the user's
eye the most when scanning the page. Avoid using "Learn more..." in link text—users seem
averse to clicking on a link which implies they will need to learn something. Instead, just try
to use a literal description of what content the user will get behind the link—and make
sure link text makes sense and is easy to understand out of context, because that is often how
it will be scanned. Be mindful about language and try to make button text descriptive,
inviting and interesting.
Test pages on a slower connection: Try out your pages using different networks
(for example, try browsing your website using the wifi at your local coffee shop or a friend's
house), especially if your target users are likely to be viewing your pages from a home
connection that's not as fast as your office network. We found a considerable improvement in CTR
and time-on-site metrics in some cases when we made scripted animations much simpler and faster
(hint: use Google's
Page Speed Online
to check performance if you don't have access to a slower Internet connection).
So if you're caught up in a seemingly never-ending redevelopment cycle, save yourself some time in
the future by investing a little up front through user profiling and basic testing, so that you're
more likely to choose the right approach for your site layout and architecture.
We'd love to hear from you in the comments: have you tried out website usability testing? If so,
how did you get on, and what are your favorite simple and low-cost tricks to get the most out of
it?
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["\u003cp\u003eUsability testing, even on a small scale, can provide valuable insights into user behavior and preferences to improve website design and functionality.\u003c/p\u003e\n"],["\u003cp\u003eConsider the technical abilities, environment, and familiarity with the subject matter of your target audience to shape the design and functionality of your website.\u003c/p\u003e\n"],["\u003cp\u003eConduct simple, low-cost tests with a small group of users, focusing on tasks and interactions, to identify and resolve common website usability issues.\u003c/p\u003e\n"],["\u003cp\u003ePay attention to clear language in headings, links, and buttons, optimizing them for easy understanding and scannability to improve user experience and engagement.\u003c/p\u003e\n"],["\u003cp\u003eTest your website on different internet connection speeds to ensure optimal performance and user experience for all visitors, regardless of their network conditions.\u003c/p\u003e\n"]]],["The Google Webmaster Team advises focusing on user experience through basic testing and profiling. Key actions include defining user profiles (personas) based on tech-savviness, environment, and content familiarity. They recommend simple testing with small user groups to identify usability issues in layouts and navigation. Define 4 or 5 simple tasks for the users to do. They also suggest avoiding hidden content, using clear, descriptive language for links and buttons, and testing on slower internet connections. Functionality, rather than graphic design, should be the main focus.\n"],null,["# Website user research and testing on the cheap\n\nWednesday, December 21, 2011\n\n\nAs the team responsible for tens of thousands of Google's informational web pages, the\n[Webmaster Team](/search/blog/2011/05/introducing-google-webmaster-team) is here to\noffer tips and advice based on their experiences as hands-on webmasters.\n\n\nIf you've never tested or analyzed usage of your website, ask yourself if you really know whether\nyour site is useful for your target audience. If you're unsure, why not find out? For example, did\nyou know that on average users scroll down 5.9 times as often as they scroll up, meaning that\noften once page content is scrolled past, it is \"lost?\"\n([See Jakob Nielsen's findings on scrolling](https://www.useit.com/alertbox/scrolling-attention),\nwhere he advises that users don't mind scrolling, but within limits.)\n\n\nAlso, check your analytics---are you curious about high bounce rates from any of your pages,\nor very short time-on-page metrics?\n\nFirst, think about your user\n----------------------------\n\n\nThe start of a web project---whether it's completely new or a revamp of an existing\nsite---is a great time to ask questions like:\n\n- How might users access your site---home, office, on-the-go?\n- How tech-savvy are your visitors?\n- How familiar are users with the subject matter of your website?\n\nThe answers to some of these questions can be valuable when making initial design decisions.\n\n\nFor instance, if the user is likely to be on the road, they might be short on time to find the\ninformation they need from your site, or be in a distracting environment and have a slow data\nconnection---so a simple layout with single purpose would work best. Additionally, if you're\nproviding content for a less technical audience, make sure it's not too difficult to access\ncontent---animation might provide a \"wow\" factor, but only if your user appreciates it and\nit's not too difficult to get to the content.\n\n\nEven without testing, building a basic user profile (or\n\"[persona](https://en.wikipedia.org/wiki/Persona_(marketing))\")\ncan help shape your designs for the benefit of the user---this doesn't have to be an\nexhaustive biography, but just some basic considerations of your user's behavior patterns.\n\nSimple testing\n--------------\n\n\nTesting doesn't have to be a costly operation -- friends and family can be a great resource. Some\npointers:\n\n- **Sample size:** Just five people can be a large enough number of users to find common problems in your layouts and navigation ([see Jakob Nielsen's article on why using a small sample size is sufficient](https://www.useit.com/alertbox/20000319)).\n- **Choosing your testers:** A range of different technical ability can be useful, but be sure to only focus on trends---for example, if more than 50% of your testers have the same usability issue, it's likely a real problem---rather than individual issues encountered.\n- **Testing location:** If possible, visit the user in their home and watch how they use the site---observe how they normally navigate the web when relaxed and in their natural environment. Remote testing is also a possibility if you can't make it in person---we've heard that Google+ hangouts can be used effectively for this ([find out more about using Google+ hangouts](https://support.google.com/plus/bin/static.py?guide=1257349&page=guide.cs&answer=1215273)).\n- **How to test:** Based on your site's goals, define 4 or 5 simple tasks to do on your website, and let the user try to complete the tasks. Ask your testers to speak aloud so you can better understand their experiences and thought processes.\n- **What to test:** Basic prototypes in clickable image or document format (for example, PDF) or HTML can be used to test the basic interactions, without having to build out a full site for testing. This way, you can test out different options for navigation and layouts to see how they perform before implementing them.\n- **What not to test:** Focus on functionality rather than graphic design elements; viewpoints are often subjective. You would only get useful feedback on design from quantitative testing with large (200+) numbers of users (unless, for example, the colors you use on your site make the content unreadable, which would be good feedback!). One format for getting some useful feedback on the design can be to offer 5-6 descriptive keywords and ask your user to choose the most representative ones.\n\n\nOverall, basic testing is most useful for seeing how your website's functionality is\nworking---the ease of finding information and common site interactions.\n\nLessons learned\n---------------\n\n\nIn case you're still wondering whether it's really worth research and testing, here are a few\nsimple things we confirmed from actual users that we wouldn't have known if we hadn't sat with\nactual users and watched them use our pages, or analyzed our web traffic.\n\n-\n **Take care when using layouts that hide/show content:** We found when using\n scripts to expand and collapse long text passages, the user often didn't realize the extra\n content was available---effectively \"hiding\" the JavaScript-rendered content when the user\n searches within the page (for example, using Control + F, which we've seen often).\n\n- **Check your language:** Headings, link and button text are what catches the user's eye the most when scanning the page. Avoid using \"Learn more...\" in link text---users seem averse to clicking on a link which implies they will need to learn something. Instead, just try to use a literal description of what content the user will get behind the link---and make sure link text makes sense and is easy to understand out of context, because that is often how it will be scanned. Be mindful about language and try to make button text descriptive, inviting and interesting.\n- **Test pages on a slower connection:** Try out your pages using different networks (for example, try browsing your website using the wifi at your local coffee shop or a friend's house), especially if your target users are likely to be viewing your pages from a home connection that's not as fast as your office network. We found a considerable improvement in CTR and time-on-site metrics in some cases when we made scripted animations much simpler and faster (hint: use Google's [Page Speed Online](https://pagespeed.web.dev/) to check performance if you don't have access to a slower Internet connection).\n\n\nSo if you're caught up in a seemingly never-ending redevelopment cycle, save yourself some time in\nthe future by investing a little up front through user profiling and basic testing, so that you're\nmore likely to choose the right approach for your site layout and architecture.\n\n\nWe'd love to hear from you in the comments: have you tried out website usability testing? If so,\nhow did you get on, and what are your favorite simple and low-cost tricks to get the most out of\nit?\n\n\nWritten by\n[Kathryn Cullen](https://plus.google.com/113030639083158400706/about),\nGoogle Webmaster"]]
