|
|
Table-layout versus Tableless & CSS Layout Website Demonstration.
|
|
Why Tableless?
|
|
•
|
Faster loading pages
|
|
•
|
Less code, smaller pages... same content
|
|
•
|
Less expensive redesigns
|
|
•
|
Less expensive site maintenance
|
|
•
|
Quicker maintenance turnaround
|
|
•
|
Greater efficiency
|
|
•
|
Site consistency
|
|
•
|
Better search engine results
|
|
•
|
Less bandwidth usage
|
|
•
|
Less hosting storage needs
|
|
•
|
Greater accessibility
|
|
|
|
Clowning around? No, but this is a demonstration. While this page was taken from an actual site, developed by a real design firm (not just someone who enjoys playing around with HTML on the weekend), it is not meant to attack anyone or any firm.
While the overall table layout was used, the look and content of the page was changed to avoid any copyright infringements and to protect the guilty. Any similarities in look and design are, while highly likely, merely coincidental.
No pages, designers, or code were harmed in anyway during the making of this demonstration. Professional designers at work, do not try this at home..... after all, it's not about websites, it's about your identity.
What's wrong?
Excessively bloated pages with unnecessary code, deprecated code, poor accessibility, hard-coded font sizes with no scalability, multiple nested tables used for layout, etc.
|
What's it all mean?
Even the dummy knows, this can't be good! Pages take longer for the browser to load for your visitors. Make a site wide style change to font sizes or to the font family, colors, or similar and nearly every line of every web page will have to be changed. More storage space and bandwidth from your server is required since the pages contain so much data... though most of the data is code, not content, so you have to pay for larger storage and higher bandwidth transfer rates from your host. Since every page has to be modified for site wide changes, changes are much more labor intensive, take longer, run the risk of losing site-wide consistency and style... essentially, everything costs more over the long haul. Poor searchability by search engines as they have to sort through all of the unnecessary coding. And we could go on.
|
|
|
So why doesn't everyone do it tableless?
It's hard. Maintaining the web design status quo is much easier. The web designer faces many challenges and headaches by trying to do things the right way. Besides, having to change 100 pages of a 100 page site is far more lucrative than having to change 1 page of a 100 page site. This is a very black and white view in a very gray world and there are always exceptions and compromises. Aim high, compromise later, not sooner... it's about your identity.
|
Lose the training wheels.
Identity Developments will be beside you all the way, helping you to reach new limits.
|
|
So what do you get with a CSS & tableless design:
|
•
|
more overall design control
|
|
•
|
more flexibility to make small and large changes
|
|
•
|
easier to update and modify
|
|
•
|
less total cost
|
|
•
|
smaller file sizes meaning: faster loading pages, less storage space needed from your web host
|
|
•
|
more accessible pages for everyone, not just people with disabilities
|
|
•
|
more compliant pages - developed properly, little to no deprecated coding
|
|
|
