File Size
With one of my sites with a somewhat complex layout, I saw page size go from 60k to only 6k for the on page code. This was done by simply changing from a table-based, to a CSS-based layout. If you run a heavily traffic'd website, with thousands of visitors a day, this can save you huge on hosting fees.
Not only does it save you bandwidth, it also cuts way down on the user's download time per page, which increases the user-experience.
Placement of Content within Code
By using floating block elements (divs), or absolutely positioned elements. You can control exactly where you content shows up in your code, despite where it is displayed to the user.
The advantages of this are arguable in terms of SEO, but has a clear advantage for usability to disabled users or users with text-based browsers.
Code:Content Ratio
By cutting down on your on-page layout code, you increase your code to content ratio. This is another debatable topic, but the less the SE spider has to sort through, the more content from your site it will digest.
Ease of Editing
If you keep all your layout styles in one CSS file (which you should), if you want to change anything on your website, it should be as simple as editing that single file. While if you have a large database driven site with a table based layout, you will have to go though each dynamic page, and manually edit the layout.
Besides the benefits above, you get to display that ultra-cool "VALID XHTML 1.0 STRICT" image on your up-to-date, cutting edge website. w00t!
With one of my sites with a somewhat complex layout, I saw page size go from 60k to only 6k for the on page code. This was done by simply changing from a table-based, to a CSS-based layout. If you run a heavily traffic'd website, with thousands of visitors a day, this can save you huge on hosting fees.
Not only does it save you bandwidth, it also cuts way down on the user's download time per page, which increases the user-experience.
Placement of Content within Code
By using floating block elements (divs), or absolutely positioned elements. You can control exactly where you content shows up in your code, despite where it is displayed to the user.
The advantages of this are arguable in terms of SEO, but has a clear advantage for usability to disabled users or users with text-based browsers.
Code:Content Ratio
By cutting down on your on-page layout code, you increase your code to content ratio. This is another debatable topic, but the less the SE spider has to sort through, the more content from your site it will digest.
Ease of Editing
If you keep all your layout styles in one CSS file (which you should), if you want to change anything on your website, it should be as simple as editing that single file. While if you have a large database driven site with a table based layout, you will have to go though each dynamic page, and manually edit the layout.
Besides the benefits above, you get to display that ultra-cool "VALID XHTML 1.0 STRICT" image on your up-to-date, cutting edge website. w00t!