Andrew Pollack's Blog

Technology, Family, Entertainment, Politics, and Random Noise

Designing your web site for YOUR target browsers - Not just "global" standards

By Andrew Pollack on 10/30/2007 at 08:34 AM EDT

Second Signal's web site has been the focus of a great deal of my time recently. I'd love to use all that screen real estate on the right side that my laptop's wide screen shows, but before even attempting that I needed to understand what other people would see.

There are lots of sites out there declaring that most people are using 1280x1024 screens now that LCD panels have been standardizing on that at 17" for so long. Other sites say the majority are 1024x768 still. Pretty much nobody is running at 800x600 other than the special cases for visually impaired or mobile browsers.

I decided to do my own mini-survey to see what the people browsing MY site were using. To do that, I used (blatantly copied from a demo) the following code:
var myWidth = 0, myHeight = 0;
if( typeof( window.innerWidth ) == 'number' ) {
    	myWidth = window.innerWidth;
    	myHeight = window.innerHeight;
  } else if( document.documentElement 
		&& ( document.documentElement.clientWidth
		 || document.documentElement.clientHeight ) ) {
  	//IE 6+ in 'standards compliant mode'
  	myWidth = document.documentElement.clientWidth;
  	myHeight = document.documentElement.clientHeight;
  } else if( document.body && ( document.body.clientWidth 
		|| document.body.clientHeight ) ) {
  	//IE 4 compatible
  	myWidth = document.body.clientWidth;
  	myHeight = document.body.clientHeight;
document.getElementById('screenwidthpoll').innerHTML = 
		"<img style='visibility:hidden' 
		src='/xxxxx/xxxx.nsf/onepixel.gif?open&screen=" + 
		myWidth  +  "x" +  myHeight  + "'>";

This works with a small "<div>" element with an id of "screenwidthpoll" on the page and causes the browser to download an image using the following relative URL:


I can then parse that in the logs and get pretty good statistics. The numbers aren't exact because I'm measuring "useable screen" rather than native, so depending on the width of scrollbars and things it varies. I'm compensating by rounding down (dropping the least significant digits) to the nearest 100 pixels and categorizing on the result.

So what am I seeing? 44% of browsers to my site have a useable screen width on the browser page of about 1000 pixels. 46% of browsers to my site have a useable screen width of about 1200 pixels. More interesting is that if you draw a dividing line at 1000 pixels, exactly 50% of browsers have 1000 or fewer and exactly 50% have more than 1000.

Unfortunately, content made for 1024x768 monitors looks terrible if you just allow it to expand all the way out past a certain point. My laptop natively wants some crazy number like 1920x1280 but I can't even read that on a 15" screen. I've set it to 1440x900. At that width, the page would look terrible. Since the css value for "Max-Width" doesn't work well across browsers, you have to do some nasty javascript hacking to allow an expandable area that stops at a specific limit. You can do it in Domino though (or PHP) by sensing the browser as you're rendering and keeping their width in a cookie. If you know they're using a wide browser and you know their browser version you could change the "width" attribute as you're rendering a page.

Until then, the smart money says you've got just under 1000 pixels of width to design for.

Note: For a good generalized poll of browser widths, take a look at these two links:

There are  - loading -  comments....

Ironically, or was it deliberately?By Rob McDonagh on 10/30/2007 at 09:34 AM EDT
...this post scrolls off my screen to the right. Heh.

Seriously, though, we (internally) still have people at 800x600. Granted,
that's hardly normal. But yeah, know your customers and don't assume
"everybody" has 19" LCDs.

Try running iNotes 7 or 8 at 800x600, by the way. The message subject shrinks
to an unusable length (and doesn't wrap, just cuts off). I've had a
conversation about that with some people at IBM. They were very surprised to
learn that there were people out there without 10x7 as a minimum resolution.
LOL. Yeah, this blog design doesn't get the attention...By Andrew Pollack on 10/30/2007 at 01:11 PM EDT
that the second signal website does.
Google Analytics reports on resolutionsBy Tim Tripcony on 10/30/2007 at 09:47 AM EDT
According to Google Analytics, here's the top five resolutions of visitors to
my site:

1280x1024: 31.31%
1024x768: 22.9%
1280x800: 7.93%
1400x1050: 7.74%
1680x1050: 7.24%

800x600 comes in 12th with 1.35%, and is the smallest resolution with more than
one page view in the last month. The range this month was 640x480 - 2560x1600,
but for the whole year, the range has been from 320x240 to a whopping
re: Designing your web site for YOUR target browsers - Not just "global" standardsBy Nathan T. Freeman on 10/30/2007 at 10:50 AM EDT
Of course, since you guys are all looking at SCREEN res, rather than actual
client window space, you're designing for a standard browser that's maximized
and has no add-ons that take left/right or top screen real estate.

Which is why your design should always be fluid, preferably shrinking
coherently to 320x240 -- which is the kind of space you get on a Blackberry.

Other Recent Stories...

  1. 01/28/2020Copyright Troll WarningThere's a copyright troll firm that has automated reverse-image searches and goes around looking for any posted images that they can make a quick copyright claim on. This is not quite a scam because it's technically legal, but it's run very much like a scam. This company works with a few "clients" that have vast repositories of copyrighted images. The trolls do a reverse web search on those images looking for hits. When they find one on a site that looks like someone they can scare, they work it like ...... 
  2. 03/26/2019Undestanding how OAUTH scopes will bring the concept of APPS to your Domino serverWhile a full description of OATH is way beyond what I can do in this quick blog entry, I wanted to talk a bit about how "SCOPES" interact with the already rich authorization model used by Domino. Thanks to the fantastic work by John Curtis and his team, the node.js integration with Domino is going to be getting a rich security model. What we know is that a user's authorizations will be respected through the node.js application to the Domino server -- including reader names, ACLs, Roles, and so on. The way ...... 
  3. 02/05/2019Toro Yard Equipment - Not really a premium brand as far as I am concernedDear Toro Customer Service, I arm writing about the following machine: Toro Power Max 1120 OXEModel:38654S/N:31000#### Specifically, bearing part #:63-3450 This is the part ($15 online / $25 at the local dealer) that caused me to raise my objections on-line. This piece of garbage is supposed to be a bearing. It carries the shaft which drives both stages of the auger. The shaft passes through the bearing (which is what bearings do) after the auger drive pulley as the shaft goes through the back (engine ...... 
  4. 10/08/2018Will you be at the NYC Launch Event for HCL Domino v10 -- Find me! 
  5. 09/04/2018With two big projects on hold, I suddenly find myself very available for new short and long term projects.  
  6. 07/13/2018Who is HCL and why is it a good thing that they are now the ones behind Notes and Domino? 
  7. 03/21/2018Domino Apps on IOS is a Game Changer. Quit holding back. 
  8. 02/15/2018Andrew’s Proposed Gun Laws 
  9. 05/05/2016Is the growing social-sourced economy the modern back door into socialism? 
  10. 04/20/2016Want to be whitelisted? Here are some sensible rules for web site advertising 
Click here for more articles.....

pen icon Comment Entry
Your Name
*Your Email
* Your email address is required, but not displayed.
Your thoughts....
Remember Me  

Please wait while your document is saved.