free geoip Fixed Width vs Variable Width Websites - protected virtual void jaysonBlog
in

jaysonKnight.com

Welcome to my corner of the internet

protected virtual void jaysonBlog

A conduit to the voices in my head

Fixed Width vs Variable Width Websites

I wanted to get some feedback from you guys on the whole “fixed vs variable width” debate for website design.  JK.com is (and always has been) a variable width site, and will more than likely continue to be for the foreseeable future, but I’ve seen some pretty good arguments as of late pushing fixed width design as it lends itself to better readability, and works better across different screen resolutions.  I personally prefer variable width mainly due to the fact that since I paid for a monitor capable of 1600x1200, I’d like as much of that real estate to be put to use as possible…but I also just like the whole look and feel of an entire browser window containing content. 

I do realize that at higher resolutions (like what I use) readability starts becoming a bit of an issue as blocks of text are stretched out (and usability tests have proven that readers prefer shorter lines of text), but the same is true for fixed width sites at higher resolutions…you’re left with a narrow column of content in the middle, with each side basically being left unused.  Not distracting per se, but kind of annoying nonetheless.  At lower resolutions, fixed width sites generally have an edge over variable width from what I’ve seen.  There are always some tradeoffs.

In a perfect world, web designers would create sites exactly how they want them to look (which in my case is quite true)…but in the real world you have to design for what your users want.  Not that I really care what (all 4 of) you people think, but wanted some feedback regardless ;-).

Share this post: Submit Fixed+Width+vs+Variable+Width+Websites to Technorati | Submit Fixed+Width+vs+Variable+Width+Websites to del.icio.us | Submit Fixed+Width+vs+Variable+Width+Websites to digg.com | Submit Fixed+Width+vs+Variable+Width+Websites to reddit.com | Submit Fixed+Width+vs+Variable+Width+Websites to DotNetKicks | Add Fixed+Width+vs+Variable+Width+Websites to Live Bookmarks
Only published comments... Jan 04 2006, 10:19 PM by Jayson Knight

Comments

 

Thomas Freudenberg said:

I prefer variable width sites too. However, I own a 24" 1920x1600 monitor, and variable width pages are difficult to read when the browser window is maximized.
January 5, 2006 12:26 PM
 

Brendan said:

I prefer variable width. On my main machine, I don't tend to maximise browser windows, so it's nice when sites look right at whatever size I've left the windows. It annoys me a little when I have to resize the window to suit the site. However, I'm currently on my laptop, which is only running at 1024x768 and the site still looks good to me. Some sites have me scrolling all around the place at this resolution, which isn't ideal. Many new entry level displays still look at their best at this resolution.
January 6, 2006 7:08 AM
 

Jayson Knight said:

Jesus Thomas, that's a shedload of pixels! In response to both of you guys, another post I have planned addresses something you both mentioned...maximized windows (and how many people keep windows maximized).
January 6, 2006 8:12 AM
 

Sara said:

Maybe its a passing phase but I actually prefer the fixed width and I am typically on my widecreen laptop with a res of 1920 x 1200. For whatever strange I like seeing the extra white space. When I have the entire page filled with content, uness its done REALLY well, it looks cluttered to me.
January 7, 2006 5:44 PM
 

Jayson Knight said:

Sara, I agree with you on super high resolutions like that, especially widescreen, which is why I went the dual sidebar route on my site (to frame the center content). That being said, I think some types of sites (namely blog type sites) lend themselves much better to fixed width, while other types (like forums) look a little goofy if done in fixed width. Or MS.com...it would look terrible as fixed width, but it's not a text only site. There is a decent chance that JK.com vNext may be fixed width (initially at least) as I'm working on beefing up my ad campaign...and Google ads are all fixed width (which is just dumb IMO).
January 8, 2006 1:06 AM
 

Eugenia said:

I personally prefer Fixed widths. Both ways have their good and bad points (high-res monitors is one reason), but I prefer fixed widths for sites that have icons and images aligned left and right. If it's not fixed, then the icon will look like crap on the left or the right of a very long sentence (while it would look much cooler when the sentence renders in 3-4 lines instead). So, it all depends how the REST of the design of your site looks like. Then, there are problems with compatibility with older browsers who they don't render variable width sites as well as fixed width ones. If backwards compatibility with very old browsers is a consern for you, then fixed size is better. Also, don't forget that fixed size is MUCH faster to render than variable size. Yes, if you have anything more than 500 Mhz PC you WON'T see a difference, but if you are running on a NeXT, BeBox, old Mac, old PC or a PDA, you CAN feel the difference. My husband is working along with a very experienced team for a mobile web browser which is usually runs on 30 and 40 Mhz CPUs for cellphones. And the speed difference between fixed and variable is 2:1 (simply because the browser can pre-calculate where to render what with some fixed width code). So, it all depends how the rest of your design is layed out, and what your intended audience is. There is no black and white. Whoever tells you "yes, it's better only X or only Y", doesn't have a clue.
January 8, 2006 2:42 AM

Leave a Comment

(required)  
(optional)
(required)  
Add

About Jayson Knight

Jayson Knight was clueless to the computer programming world until he took a C++ class in college. The rest is proverbial history. He has been building applications targeting the .Net framework for 7 years, focusing mainly on internet technologies and database driven web application development.

Most recently he left the world of Corporate IT to finish up his degree in Chemistry, with an eye on Medical School and an Anesthesiology residency program. Read this post for more information.

He is also a Community Server MVP: Community Server is the software that runs this site, plus many others on the web. For more information, check out http://csmvps.com.

When he finds time to pry himself away from his computer and university studies, he can be found on the mountain bike trails when it's warm, and on the ski slopes when it's cold.

Copyright © :: JaysonKnight.com
External Content © :: Respective Authors

Terms of Service/Privacy Policy