That depends largely on how you define a "good website".  I would recommend not designing them from scratch at all without a good reason.  Most webhosting providers have some excellent templates and site building tools to help you out. 

You may also want to look at some of the other factoids on this topic such as:

http://factoidz.com/how-to-sell-products-and-services-online-by-building-your-own-website-on-a-shoestring-budget/

http://factoidz.com/how-to-easily-design-a-website/

Most 'WYSIWYG" web site builders employ bloating proprietary coding that only works on Internet Explorer, and often fails on modern, World Wide Web Consortium ("W3C") recommendations. -Dreamweaver-built web sites are big offenders. They tend to fail dramatically on any browser other than Internet Explorer.

 Proprietarily web creation software-built sites often fail Accessibility s.508 for the Handicapped as well, so handicapped person will often get less from the site. -Screen readers, text-to-speech/text-to-braille etc. are often useless and the handicapped person is denied content. Denied, -this can be a problem in some locales as a web site that 'denies access' to a signifigant portion of the population can potentially be sued (county, state, federal sites, etc. and perhaps even municipal web sites are targets.)

A good web site should pass minimal validation. One of the biggest offenders is the use of "tables" for web pages when the data is not 'tabular.' Also, even though probably very few people are still using a v.4.x user agent ("browser" for the short) use of 'nested tables' causes a real big problem. For one, in Windows_98, nested table layout is known to cause a 'stack overflow' which often resulted in the "BSoD", -the dreaded "blue screen of death." This was a fault of the user agent (browser) but still, it is taxing on a computer's resources. A well-built web site is minimalistic in code-weight and should load entirely upon a 56KBS modem in 'about 10 seconds.' Most fail this, and attrition from the site increases proportionately. -For every additional 5-seconds after the first 10 or 15 seconds, you lose another 10%-maybe of your visitors whom 'back out' of the site which is not resolving to view.

When I build web pages, I try to validate and visually check upon these and other browsers: IE (I might code for v.5.x legacy, but no further back than this), Firefox/Mozilla/SeaMonkey, Opera, Flock, Safari (I use Safari-on-XP, but it reveals potential problems that MAC-users might encounter) and if I'm feeling really  generous, will check it out on LINUX with browsers like Konqueror, Galeon, etc. The pages may not *look exactly the same* on all user-agents but the content needs to be all there, delivered and visible.