Intranet Journal Update CIO Update CodeGuru Update CrossNodes Networking Instant Messaging Planet HTML Practically Networked HTML Enterprise Storage Forum HTML Optically Networked HTML Datamation IT Management Careers Datamation IT Management Update DRM Watch Developer.com Update Gamelan Java Update Goodies to Go Javascript.com Text JARS Java Update OpenSource Update SysOpt Tech Notes Grid Computing Planet HTML E-Security Planet HTML

Intranet Design Top Ten Intranet Design Mistakes By Vincent Flanders Printer Friendly Version Mistake #4. Forgetting the Japanese! Many corporations have international employees who must dial into the company Intranet. While U.S.-bound corporations may have access to large quantities of bandwidth, many overseas employees don't -- neither do many US employees who dial into the corporate Intranet from home. Just because a page loads quickly at work doesn't mean it will load quickly from a remote location. To make pages load quickly reduce the physical size of your pages. A good guideline is click on a link and start holding your breath. If you gasp for air before the page loads, it's too big (this test doesn't work for scuba divers who can hold their breath for long periods of time). If no one from the outside needs to connect to your Intranet and you have all the bandwidth in the world, then you probably can ignore what I've said and use every bandwidth-eating technique known. God speed and have fun! Previous Page Mistake #5 Forgetting that the "Top's Gotta Pop" Printer Friendly Version Author The creator of the award-winning site Web Pages That Suck and co-author of the book of the same name, lists the top 10 mistakes he's found while consulting for Fortune 1000 corporations. Hint: the image is one of them. To contact Vincent with topics you'd like to see covered in the Intranet Design Guru Column or for any other reason: vincent@flandersenterprises.com