1 / 11

5 Reasons Tables for Layouts are BAD

5 Reasons Tables for Layouts are BAD. Makes the site appear outdated Inefficient and cluttered coding Loading time Inflexibility with styles Less efficient for SEOs. By Scott Klingenberg & Sandy Vasquez . Makes the S ite A ppear Outdated.

lukas
Download Presentation

5 Reasons Tables for Layouts are BAD

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 5 Reasons Tables for Layouts are BAD Makes the site appear outdated Inefficient and cluttered coding Loading time Inflexibility with styles Less efficient for SEOs By Scott Klingenberg& Sandy Vasquez

  2. Makes the Site Appear Outdated • Websites in the 90s before the innovation of CSS would solely use tables for layout. • Since then, with CSS we can make webpages look a lot more attractive thus making table layouts obsolete. • So the obvious use of tables for webpage layout is an immediate deterrent for visitors. (Apple homepage from 1997)

  3. Current website for the Puget Sound Skills Center. (Sadly it’s the the first result on Google)

  4. Inefficient and Cluttered Coding • Cluttered with tags and having to set cell widths • A lot more code makes it more difficult for editing.

  5. Loading Time • BECAUSE layouts made entirely out of tables requires so much code, it takes significantly more time to show the information • The biggest drawback to using tables is that both the content (text, images) and visual information (layout, positioning, text sizes, etc) are contained within the same HTML, PHP, or ASP file. • One of the biggest advantages to migrating from a table-based layout to a CSS-based layout is the fact that the content is stored within the HTML, PHP or ASP file and the visual information is stored within a CSS file(s).

  6. Inflexibility With Styles • if you use specified widths for your tables, you end up with a very rigid layout that won't look good on monitors that are sized differently from your own. • Creating flexible layouts that look good in many monitors, browsers, and resolutions is relatively easy. In fact, with CSS media queries, you can create separate designs for different size screens.

  7. Less Efficiency with SEOs • Search engines will not readily find information that’s within table cells. • The most common table created layout has a navigation bar on the left side of the page and the main content on the right. • Search engines categorize pages based upon the content, and many engines determine that content displayed at the top of the page is more important than other content. • So, a page with left-hand navigation first, will appear to have content that is less important than the navigation.

  8. Sites Cited: • Apple 1997 Page : http://macenstein.com/default/2008/01/apples-website-circa-1997/ • Puget Sound Skills Center: http://www.pugetsoundsc.org/ • Government Website that uses excessive tables: http://www.gouvernement.lu/ • Information: • http://www.chromaticsites.com/blog/13-reasons-why-css-is-superior-to-tables-in-website-design/ • http://webdesign.about.com/od/layout/a/aa111102a.htm • http://www.webdesignbyjules.com/04/2011/10-reasons-to-use-css-and-not-tables-for-layout/

More Related