60 Questions to Consider When Designing a Website

Dec 15 2010 by Alexander Dawson | 38 Comments

60 Questions to Consider When Designing a Website

We spend a lot of time asking ourselves, our clients and other people questions. Whether it’s choosing the perfect shade of green for our latest web layout or figuring out how to implement a complex typographical solution, the ability to ask the right questions is among the most critical of skills for a web designer. In this article, we’ll go over 60 specific questions that web professionals should ask before taking their website public.

Why Asking Yourself Questions Is Important

Many professionals work with the aid of checklists, while others routinely check for certain issues as the design evolves. While there isn’t a sure-fire way to avoid the embarrassment of forgetting something post-launch, the habit of continually questioning your work as you develop a website is critical. Sometimes it can be as simple as "Does this work?"; in other cases, more technical questions need to be asked (and answered).

Asking Yourself Questions Is ImportantThe 25-point Website Usability Checklist (PDF) can be a helpful aid to your workflow.

It doesn’t make the job any easier to second-guess yourself into a state of neurosis  (something perfectionists do quite often) or to make blind decisions. There’s no perfect method for gauging a project’s needs or the decisions we make, but asking difficult questions during the process helps us avoid issues later on.

15 Questions for Project Management

One of the central tasks of web design is project management. Building a new website is like setting the foundation for a house. With so many details to deal with, planning ahead and managing the ongoing tasks is essential.

Basecamp is a popular and effective project management app.

1 Has the client signed the contract? Working without a contract is extremely risky.

2 Do you know what the final product should look like? Having a solid plan of action, including a few diagrams, wireframes, prototypes or mock-ups, can enhance clarity.

3 Has all of the content been written? A website without content is like a painting without a canvas; ideally, a website should be built around the content, not vice versa.

4 Does the website require any pre-built solutions? Life can be made easier with tools such as content management systems (e.g. WordPress) and scripts, so determine what you need before you start coding.

5 Do you know what the competition offers? Your rivals are often the best source of ideas, and knowing what they offer can help you meet visitors’ expectations.

6 Have you set appropriate deadlines? Setting realistic deadlines and tracking your progress towards those deadlines is always important.

7 Will you need to factor in additional costs? Websites are relatively inexpensive, and you can build a good one using free software, but still, you must be on top of any expenses you might incur.

8 Do you have the necessary skills? Some websites are more complex than others; consider which technologies you will need to work with and whether your knowledge of them is current.

9 Have you thought about marketing? A website without visitors is useless. Look into your options for social networking, SEO, advertising and more.

10 Will the website actually be useful (or even necessary)? There is no point wasting your energy on a project that will have no value for end users, so start by weeding out bad ideas.

11 Is a target audience mapped out? Knowing what kind of people you hope will visit the website will help you not only write appropriate content but design effectively, too.

12 Do you have a checklist or criteria? Even a set of basic criteria to maintain quality control or a checklist for larger projects would help.

13 Can your host cope with the demand? Getting the right type of hosting is important; there’s no point in having shared hosting if you’re going to be streaming gigabyte-heavy video.

14 Have you got the media?  Some websites require video, audio and special file types such as PDF documents. Accounting for assets early on lessens the risk of launch delays.

15 What features do you hope to include? Perhaps you need to accept payment, or maybe you want a photo gallery. Whatever you need, plan ahead prior to designing the layout.

15 Questions for Code-Authoring

Next up are questions to ask regarding writing code. If you design or develop websites, you’ll find yourself working with HTML, CSS, and JavaScript. Every language has a range of best practices and guidelines to follow, which is great if you want to standardize your end-product. However, there are a lot of other things to consider besides being standards-compliant.

The impact of source code on the effectiveness of your content is often overlooked yet very real.

16 Does the code validate? While validation isn’t a complete testament to code quality, it does help to make sure that your code follows recommended standards and can show you errors in your markup, CSS, and JavaScript.

17 Have you considered using CSS3 and HTML5?  Though many users still don’t use browsers that have CSS3/HTML5 support, if implemented with progressive enhancement in mind, taking advantage of these future W3C recommended standards gives your products added value and improves the craftsmanship of your web designs.

18 How semantic is the code? Using the right tag for the job is essential, and search engines love semantic code. Use <p> for paragraphs, <ul> for listed items that have no ranking, <ol> for items that have a sequential relationship, <a> for hyperlinks and <button> for clickable UI components that perform an action/user task.

19 Are you taking advantage of optional files and site add-ons? Whether in the form of using the Sitemaps XML protocol or including a favicon, these optional files can enhance your website. See five files that can improve your website.

20 Do you need an RSS feed? If your website is content-heavy and is updated frequently (e.g. a blog or news site), having an RSS feed will be a necessary site feature for keeping your users up-to-date with fresh content. If you don’t use a CMS with this feature built-in, check out SimplePie, a PHP class for building your own RSS feed.

21 Will the code degrade gracefully? Graceful degradation (also known as fault-tolerance) — the notion that a system (in this case, a website) will still function under sub-optimal situations — is essential for flexible and web accessible site builds. Learn how to pragmatically apply graceful degradation when using CSS3.

22 Have you considered SEO? While search engine optimization should not dictate your design decisions, it wouldn’t hurt to consider how your website could be more visible in search engine results. Read some SEO tips to remember when building your site and ways to improve the SEO of your web designs.

23 Do you provide a printer-friendly style sheet? Designing a print CSS file is worth the time investment as many users still do print out web pages.

24 Is any of your code deprecated or non-standard? Using "dead code" such as the <font> tag that was deprecated in W3C HTML 4 specifications as well as non-standard code such as the <blink> tag is frowned upon and won’t allow your work to validate against W3C web standards recommendations. Double-check that you’re not using any by taking advantage of free validation tools such as the W3C Markup Validation Service.

25 Do you need to use conditional comments? IE6 isn’t going to go away completely, and if your project requires you to support IE and to use browser-specific code, use conditional comments to serve IE-specific stylesheets instead of using hacks. This does two things: It gives you the ability to get your code to validate under W3C standards, and when you decide to stop using browser-specific code, you only need to remove the conditional comments in your site template. Leveraging JavaScript techniques for fixing IE6 and projects such as HTML5 Boilerplate to solve deprecated-browser rendering issues could be another option, but you’ll be stuck in scenarios where the user uses an old browser with JavaScript disabled — a scenario that is not as uncommon as you might think.

26 Are structure (HTML), presentation (CSS), and behavior (JavaScript) separated? This is important not only because it’s best practice, but also leads to more manageable and maintainable code.

27 Is your site navigation laid out in a practical way? The navigation menu is the most important part of your website. Getting it right is an integral part of an effective site information architecture.

28 Have you checked for unnecessary HTML elements and redundant CSS style rules? Code bloats easily, so strip away any non-essential and repeated bits of code for more maintainable and leaner (and thus, higher performance) website builds. For HTML/CSS optimizing purposes, check out HTML Tidy and CSSTidy.

29 Is the code organized and maintainable? Put care and attention into your code. Lay it out so that it’s easy to read, update and manage.

30 Would a framework enhance the site? These days, open source Ajax/web development frameworks such as jQuery and MooTools can speed up code-authoring and ensure fewer headaches due to cross-browser issues. If you suspect these frameworks might help, why not investigate and learn about them?

15 Questions for Web Designing

The process of creating a layout is full of questions related to color, typography and even distinctiveness. While your project management style may be superb and your coding technique beyond measure, design comes with its own set of questions. Web design calls for endless decisions, and that’s what these following questions are supposed to help you resolve.

Asking Yourself Questions Is ImportantUsing a wireframing tool like Balsamiq Mockups ensures a solid layout foundation.

31 Have you optimized your media? Images, videos and audio take up more bandwidth and space than anything else. Consider compressing and optimizing them with tools such as Smush.it.

32 Is the user interface overcrowded? If there’s one thing no one likes, it’s a stuffy and bloated design. Determine whether reductionism can help you design better websites.

33 Is the design distinctive and unique? With site templates in abundance, having a layout that’s fresh and eye-catching is a must. Breaking the mould may improve your brand’s identity.

34 When should I redesign? Are you able to produce something totally different or enhance what you have?

35 Does the layout make sense? Whether you pick one column or three, a lot of scrolling or none, decisions on your pages’ visual hierarchy will directly affect readability.

36 Do the colors give off the right feeling? Color is closely linked to emotion; a palette can be the difference between a fun-looking website and professional-looking one.

37 What typography is best? As with color, typography affects the feel of the website. Build your font stacks wisely and attentively and take time to craft a masterful typography design.

38 How visible are links? Links have no purpose if they cannot be seen. Make sure you take the time to design your hyperlinks well.

39 Are you using enough white space? Too many websites squeeze everything too close together. If you add some breathing room, the result could be improved readability.

40 Have you considered content on-demand? With the rise of Ajax and fast content switching techniques, packing more data onto the page is easy. Consider doing this with very long web pages.

41 Is the design aesthetically pleasing? While this process is subjective, it’s still a good idea to get feedback from your friends, co-workers and perhaps a stranger or two to determine whether your work is visually appealing or not.

42 Is the content readable? Nothing is more important than content; if it’s legible and coherent, then your site users will be happy.

43 Does the design scale at various resolutions? Displays are getting bigger (bigger desktop monitors) and smaller (mobile devices) at the same time; make sure your work renders in all web-enabled devices. For mobile devices, take advantage of free tools for testing designs in mobile devices.

44 Are important site features emphasized? Some things are more important than others; consider the various ways that relevant content can be highlighted so that visitors can easily find it.

45 Does the website feel complete? This is probably among the most important yet difficult questions to answer. Recognizing when it’s ready requires a lot of care and thought.

15 Questions for the User Experience

The user experience is perhaps the most important factor for determining the success of a website. Here are questions related to UX, usability, and accessibility.

Accessibility, usability and compatibility: few things are more important. Silverback is a popular usability testing app.

46 Does the website work equally well across different browsers? There are plenty of browsers out there — make sure your website works well in the major ones. You can use a web service like Browsershots to preview your work in various operating systems and web browsers.

47 Is the website mobile-friendly? While desktop browsers are pretty straightforward (with the exception of IE), mobile devices require an extra bit of care and attention; read about best practices for the mobile web design.

48 Have you tested the website in a screen reader? Unfortunately, even with free screen readers out there like Fire Vox, a screen-reading add-on for Firefox, few web designers consider testing their designs for screen-reader web accessibility. You might want to.

49 What happens when JavaScript is turned off? Not every experience is the same and we can’t control the visitor’s browsing environment, so try to make sure your website gracefully degrades when JS is turned off.

50 Do you offer alternatives to Flash content? Following on the previous point, if your website is particularly Flash-dependent, you might want to make sure that your use of Flash is accessible.

51 Did you remember alt attributes? One of the simplest accessibility aids to implement is using descriptive and useful alt attribute for images.

52 Have you evaluated your website against Web Content Accessibility Guidelines? Complying with web accessibility best practices is important for users who have disabilities that affect their capability to browse the web. Fulfilling the recommendations in the W3C Web Content Accessibility Guidelines (WCAG) is the perfect place to start.

53 Has the website been tested by other people? Usability testing is quite easy and inexpensive to carry out nowadays. Performing tests could give you ideas for improvements. Check out web services such as Concept Feedback and Feedback Army.

54 Do your URLs make sense? URLs that are easy to read will give potential visitors the chance to predict where they’re headed (and is good for SEO to boot). Using pretty URLs (example.com/about-us) instead of system URLs (example.com/?p=655) can enhance the experience of visitors. If you’re using a content management system or a custom-built app, learn about rewrite engines.

55 How quickly does your site load? Speed is an important factor of usability. Consider how your website will affect visitors, particularly ones on slow connections.

56 Is the search functionality easy to use? Most websites need a search box to help visitors locate the information they need. Ensure that yours is easy to use and that the results are accurate.

57 Will there be any potentially obnoxious behavior? Whether it’s pop-ups and modal windows that won’t close, or scripts that cripple right-clicking, make sure your site doesn’t have behavior that annoys users.

58 Are your web forms usable? If you’re asking for too much information or your forms are too hard to complete, people will enter fake details or simply refuse to submit the data.

59 Can the site owner be contacted without difficulty? While you might get spammed in the process, allowing visitors to send you an email or to initiate a Skype call could be a great way to connect with them.

60 Have you checked for broken links? Root out dead links in every nook and cranny. Tools such as Xenu’s Link Sleuth can automate the process; learn how to discover broken links in your website.

Conclusion

As we learn and grow, our competency increases, which changes our perspective and workflow. Designers and developers who regularly question their methods and ideas are usually the ones who get the job done right and are the ones who consistently improve their processes and products.

Related Content

About the Author

Alexander Dawson is a freelance web designer, author and recreational software developer specializing in web standards, accessibility and UX design. As well as running a business called HiTechy and writing, he spends time on Twitter, SitePoint’s forums and other places, helping those in need.

38 Comments

New2Design

December 15th, 2010

Great Article…. Its a great checklist for us beginners to adapt to.

Usman

December 15th, 2010

all these points are really important. I am still in learning process so I am not aware of many web designs skills.

but to keep these points in mind is very important.

most probably : point 1,3 and 50 are more important for me i think.
thanks a lot

Rakesh Kumar

December 15th, 2010

Hey, Dawson, As I am also designer and here i have learned more new things. Thanks

Peter

December 15th, 2010

Great list. I think this article give many usful information. Thanks

DTX Studios

December 15th, 2010

Very useful article! All points are valid. Good job.

Lisa Casson

December 15th, 2010

What an amazing article. Thanks for the questions and reference links.

Shrikrishna Meena

December 15th, 2010

Useful article but Finding the faults ourselves (i.e. Designers themselves) will teach and help more than that reading anywhere else…
Well, I’m already aware of 90% of the points you mentioned… and remaining 10% are really good.

john

December 15th, 2010

“Have you considered using CSS3 and HTML5?”

Seriously? CSS3 and HTML5 are not something you need to “choose”. Whether you’re writing up-to-date HTML or you’re not.

If you’re asking yourself “Does the code validate?” this should be out of the question.

Geoff McMahen

December 15th, 2010

Great list, very detailed.

Gabriele Maidecchi

December 15th, 2010

Although as you mention there’s no law set on stone, valid 100% of the times, I feel like this list is very reasonable and can sure become an helpful addition to the design/production process.
Thanks for sharing it.

Young

December 15th, 2010

Awesome article Alex. Just like Shrikrishna said, everything that’s not something I already knew were gems – didn’t know about Smush.it – that’s an awesome tool! Thanks a bunch. Good checklist too.

@John: Most clients I’ve dealt with care more about the aesthetics than validation, i.e. They’re usually okay with CSS3, fully aware that IE won’t support it, and honestly I’ve yet to meet someone who was THAT concerned about valid CSS – HTML, yes, but not so much CSS. I think sometimes it’s the right choice, if the client absolutely needs to have rounded rectangles and I don’t have the time / am not paid enough, I’d do CSS3 over adding tons more markup, not to mention the graphics work, to get it done. Alex is not saying you should consider CSS3 and HTML5 whenever you can – he’s saying they should be applied when appropriate, unhindered by bureaucratic validations.

Alexander Dawson

December 15th, 2010

Thanks for the feedback guys!

@Paul: I didn’t forget them (I just chose to keep things simple). Though there are some excellent checklists out there. I’m a particular fan of SitePoint’s 101 Checklists book (On project management). Personally, I’m always asking myself questions!

@john: Actually, the choice to use upcoming standards IS a choice that people choose to make. If it wasn’t there would have never been the whole XHTML 1.0 VS 1.1 problem (which ties in with browser functionality). Plenty of people still use Transitional HTML 4, which is basically HTML 3.2 (compatibility for old dead code). So it should qualify IMO.

@Young: I’ve been using SmushIt for ages and it’s done wonders with my images.

Dave

December 15th, 2010

Great list!

I’ve been wanting to assemble something like this for years, but haven’t had the time because I’ve been doing it.

Marcelo Mizuno

December 15th, 2010

Great article… tanx

Raul

December 16th, 2010

nice article! its always great to have a check list while working on a website

Monika

December 16th, 2010

“3 Has all of the content been written? A website without content is like a painting without a canvas; ideally, a website should be built around the content, not vice versa.”

and what do you do if you have to design a cms?
if you have to design a website for a newssite/magacine- should all the news *be written* ;)

;)

This point is unrealistic.

But we designer have to know the kind of content, and the customers from our customers. Like “Bait the hook to suit the fish, not the fisherman.”

kindly regards

Monika

Stephani

December 16th, 2010

Excellent list! I’ll be linking to this as a resource from our website. Thank you!

Alexander Dawson

December 16th, 2010

@Monika: Designing a CMS is not the same as designing a site. A CMS is an application, used to output and manage the sites content. Application design follows different rules to web design, and there is a pretty wide difference between the two. A good CMS solution should be working in the background, doing it’s job – invisible and unobtrusive to the visitor. A good website on the other hand should be very much seen and heard as it’s the justification for visiting that site (both in aesthetic and content design).

Diane

December 16th, 2010

Great article! I believe you mean “inexpensive” in #53 and SEO in item #54. Thanks again for a very helpful article.

Abhisek

December 16th, 2010

Probably we need to consider Security and Privacy Issues as well.

Jacob Gube

December 17th, 2010

@Diane: Thanks Diane. Fixed.

Keith Davis

December 18th, 2010

Alexander
Only 60!

This must have taken you ages – a truly comprehensive list of check questions.

Particularly interested in…
“Have you considered using CSS3 and HTML5?”

I’m noticing more and more articles on CSS3 – rounded corners, drop shadows and the like but how many people are using it?

Ranjit

December 21st, 2010

Great Article. Thanks for sharing Alex..

Anderson

December 21st, 2010

60 very USEUL tips, not only the usual stuff that there is in thounds of websites across the internet.

Link

December 21st, 2010

A great deal of design out there is over the top and hard to navigate. I think this article needs to be read by a great deal of designers. I found this article very helpful and it reinforces the purpose of designing a website to represent the company. It isn’t about how many animations you can pile on a page. That is unfortunately what we seem to be bombarded with lately. That kind of content slows the page loading and is annoying when trying to locate information that counts.

Thor

December 22nd, 2010

Great article. The attachment is really helpful as well. I have been involved in my churches web site. The checklist will be something useful to go over with people in my church.

Péricles

December 25th, 2010

Great article guy, checking all of this items even the most begining user can get closer to perfection… thank you…

Chris Everson

December 26th, 2010

I think that obtaining current site information (domain + ftp) is super important when doing re-designs or when the client already has a domain name. FTP information is dependent on whether or not you’ll need access or not obviously.

Amit Bhatia

December 31st, 2010

Your list is all-in-one resource for designers. Thanks for putting an effort to compile this list.

Nidhin Baby

January 7th, 2011

Very useful posting. Thanks for sharing it :)

Christian Amauger

January 7th, 2011

Very useful and interesting article. Thank you for posting it!

Shauna

January 7th, 2011

@Keith Davis – I can’t speak for others, but I use CSS3 as often as is feasible. For most of my projects, it’s generally drop shadows, text shadows, and gradient backgrounds. It saves a ton of time, resources, and headache, especially if you know the IE filters that mimic the same behavior and/or accept that some browsers might not have all of the niceties.

For gradient backgrounds, since I generally still have to fall back to an image for IE and non-Gecko or Webkit browsers, the advantage lies in the fact that the Gecko and Webkit browsers will skip the image download and only look at the gradient generation, which saves server requests and download times.

I think more people should use what they can, to help keep web innovation moving forward. If everyone waited until every aspect of a spec was available across all browsers, we wouldn’t even be using CSS2.1 right now.

raoul

January 18th, 2011

many many thanks! Just what I needed

Bfreebies

January 30th, 2011

Hmm is anyone else encountering problems with the images on this blog loading? I’m trying to determine if its a problem on my end or if it’s the blog. Any suggestions would be greatly appreciated.

Jerrick

February 21st, 2011

That awesome question do have answer to have but implement to fix it , will be another question to follow up.

TimKola

July 16th, 2011

that was an awesome read and has made me want to spend a bit more time havin a read through more of your blog
cheers for your insightful knowledge

Happytodos

September 30th, 2011

I personally use happytodos for project management. It has time tracking, task scheduling and online collaboration.

Leave a Comment

Subscribe to the comments on this article.