{"id":170,"date":"2009-04-12T17:42:00","date_gmt":"2009-04-12T17:42:00","guid":{"rendered":"http:\/\/www.dresan.com\/blog\/?p=170"},"modified":"2009-04-12T17:42:00","modified_gmt":"2009-04-12T17:42:00","slug":"how-wide-should-your-website-be","status":"publish","type":"post","link":"https:\/\/dresan.com\/blog\/2009\/04\/12\/how-wide-should-your-website-be\/","title":{"rendered":"How Wide Should Your Website Be?"},"content":{"rendered":"<p>For the longest time I&#8217;ve tried to design the websites I&#8217;m responsible for to be pretty narrow &#8211; the <a href=\"http:\/\/www.dresan.com\/\">Library of Dresan<\/a> is supposed to be just over 800 pixels, <a href=\"http:\/\/www.fanufiku.com\/\">fanu fiku<\/a> is supposed to be just over 700 pixels, and <a href=\"http:\/\/www.studiosandi.com\/\">Studio Sandi<\/a> is just about 800 pixels.  The rationale behind this was that in the olden days of the Internet, user&#8217;s screens were as small as 1024 by 768 or even 800 by 600, and even users who had wider monitors displayed their browser in a window that didn&#8217;t take up the full screen.<\/p>\n<p>I remember reading an article (I don&#8217;t remember where) that pointed out with browser sidebars and chrome, the width of the page could be far less than monitor width.  I measured it on my circa-2000 screen and I found that I had about 800 pixels of width for the web page.  So that led to the design of the Library: 800 pixels of width, 600 for the main content and 200 for the sidebar.  The banner itself was a little over 1000 pixels so that it didn&#8217;t end abruptly if the user made their screen wider.<\/p>\n<p>But that was almost ten years ago.  Does that logic still hold?<\/p>\n<p>Many people view the web on laptops and phones.  Dealing with phone resolution will require more than just dealing with screen widths, so I&#8217;ll return to it in a later article when I tackle the CSSification of the Library.  But a quick search suggests that <a href=\"http:\/\/www.geek.com\/laptop-screen-size-resolution\/\">typical laptop screen widths range<\/a> from the 1024&#215;768 XGA standard to the 1440&#215;900 WXGA+ widescreen standard.  There are some people who have smaller laptop screens, of course, but they are in the minority.  Conversely, screens do get larger: for example, for many years I owned a glorious Toshiba Satellite laptop with a 1600&#215;1200 screen.  But on those larger screens users often use smaller windows for their browsers: for example, on this MacBook Pro, with a 1440&#215;900 screen, I&#8217;m only using a little more than 1200 pixels for the browser window &#8211; and typically I use narrower windows.<\/p>\n<p>So something more than 800 and less than 1400 appears to be a good guess.  Discussion on the web seems to indicate people are <a href=\"http:\/\/www.webmasterworld.com\/forum21\/9839.htm\">starting to give up on the 800 width<\/a> and <a href=\"http:\/\/forums.digitalpoint.com\/showthread.php?t=687599\">moving to 900 or more<\/a>, but <a href=\"http:\/\/www.webproworld.com\/graphics-design-discussion-forum\/63728-width-website.html\">rarely more than 1024<\/a>.<\/p>\n<p>Digging around, I found more articles with the same idea &#8211; <a href=\"http:\/\/www.webdesign.org\/web\/web-design-basics\/website-usability\/the-web-page-width-dilemma.2641.html\">Mario Sanchez<\/a> argues the goal of web site width is to avoid horizontal scrolling, and recommends you design your web site for 800 pixels, with a layout that works well at 1024.  <a href=\"http:\/\/www.useit.com\/alertbox\/screen_resolution.html\">Jacob Nielsen<\/a> recommends straight out to optimize your site for 1024, but not to design for a specific size and let your layout be &#8220;liquid&#8221;, changing width for your users&#8217;s monitor sizes.  Personally I think this breaks down if you have images to display, though I reserve the right to be convinced otherwise by CSS wizardry at a later time.  <\/p>\n<p>All of the above are opinions, of course; what about the evidence that they&#8217;re based on?  The <a href=\"http:\/\/store.steampowered.com\/hwsurvey\/\">Steam Hardware Survey<\/a> put out by Valve Corporation suggests that 95% of users use screens of 1024 pixels or wider, with fully 50% at 1024&#215;768, 1280&#215;1024, or 1440&#215;1900.  Similarly, the <a href=\"http:\/\/www.w3schools.com\/browsers\/browsers_display.asp\">Browser Display Statistics<\/a> analysis by W3 Schools indicate 36% of users have a display resolution of 1024&#215;768 &#8230; and 57% have higher.  <b>Update:<\/b> I checked the Library&#8217;s own stats, and found that Google Analytics does indeed track screen resolutions.  Less than 5% of all users had a resolution less than 1024&#215;768, and only 1.5% had a resolution less than 800&#215;600.  Of that, 0.5% were listed as no resolution, leaving 1% at 640&#215;480.  Those numbers will come back later&#8230;<\/p>\n<p>Take all that with a grain of salt given that some significant percentage use browser screens larger than their monitor resolution &#8211; Nielsen points out in the <a href=\"http:\/\/www.useit.com\/alertbox\/screen_resolution.html\">same article I mentioned above<\/a> that as resolutions get staggeringly large (he predicts 5000&#215;3000 in the future) users begin to display multiple side by side windows.  True enough, at the Search Engine That Starts With a G, all of my officemates have dual monitors with aggregate resolution of 2400&#215;1920, but none of us typically displays a browser window larger than half the screen &#8211; 1200 pixels, minus chrome or subtracted width to see other windows underneath.<\/p>\n<p>So that leaves me with the feeling that Nielsen and Sanchez are essentially right.  My personal take on it for the Library is:<\/p>\n<ul><\/p>\n<li><b>Your website should display well in no more than 1024 pixels of width.<\/b> You may use a &#8220;liquid&#8221; layout that can expand to use more space, but it should not require more than 1024 pixels to display.<\/li>\n<p><\/p>\n<li><b>The essential content of your web site should fit into the leftmost 800 pixels of width.<\/b> If you are displaying graphics or images or have a lot of site widgets, some of these features may scroll off to the right on an 800&#215;600 screen.  Don&#8217;t put anything essential on the right.  Your mileage may vary if you are creating a web site for right-to-left languages, of course.<\/li>\n<p><\/p>\n<li><b>Make sure your &#8220;liquid&#8221; layouts don&#8217;t break down on very wide or narrow screens.<\/b> A user who displays a very wide window on a 2400 pixel wide screen should not see all your paragraphs turn into long marching lines of text &#8211; these can become hard to read.  Similar problems can happen when a screen is squeezed very small &#8211; for example, Wikipedia used to display terribly on certain mobile phones, creating vast blank spaces for the user to navigate through.<\/li>\n<p><\/ul>\n<p>The new design for the Library uses around 1000 pixels, with the leftmost 600 for text (to satisfy the 1% of people who are still stuck at 640&#215;480), the next 200 for site navigation (for the less than 5% stuck at 800&#215;600), and the remaining 200 for everything (and everyone) else: search boxes, author pictures, and Flickr badges; in short, anything less important than the articles and navigation features.  Technically this is not a &#8220;liquid&#8221; layout, but hopefully this will be something the vast number of users can enjoy with little scrolling, and something that other users can appreciate without feeling left out.<\/p>\n<p>-the Centaur<\/p>\n","protected":false},"excerpt":{"rendered":"<p>For the longest time I&#8217;ve tried to design the websites I&#8217;m responsible for to be pretty narrow &#8211; the Library of Dresan is supposed to be just over 800 pixels,&#8230;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[11,3],"class_list":["post-170","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-development","tag-webworks","ratio-2-1","entry"],"_links":{"self":[{"href":"https:\/\/dresan.com\/blog\/wp-json\/wp\/v2\/posts\/170","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dresan.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dresan.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dresan.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/dresan.com\/blog\/wp-json\/wp\/v2\/comments?post=170"}],"version-history":[{"count":0,"href":"https:\/\/dresan.com\/blog\/wp-json\/wp\/v2\/posts\/170\/revisions"}],"wp:attachment":[{"href":"https:\/\/dresan.com\/blog\/wp-json\/wp\/v2\/media?parent=170"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dresan.com\/blog\/wp-json\/wp\/v2\/categories?post=170"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dresan.com\/blog\/wp-json\/wp\/v2\/tags?post=170"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}