Website Review and Suggestions

**imnewhere** · 03-18-2009, 06:18 PM

I posted the other day and got some very helpful advice. I've made more revisions and would like some opinions on how the site looks. I'm afraid it looks home-made/generic. Please give me your thoughts.

I've made this in DW and it's a re-design for a security company.

csi.agilityhoster.com

**Physicsguy** · 09:01 AM

Cool, I like the layout, but not really the buttons. I can give you a navmenu like mine, to maybe help organize the links a little more, but you need an external Javascript file to use, which I can give you if you want. The banner is sort of tough to see, I certainly like it, but the font and shadow makes it difficult to read.

The pictures on the homepage are cool, they catch your attention! The headers on every page, the ghosty-whispy ones are neat, they add to the dark ambience of the site!

One thing I would recommend is that you center your site. In the CSS, all you have to do is put the main floated center. I think, but that's what I have on mine.

Hope I could help!

**KML9870** · 03-19-2009, 09:09 AM

You have some html errors to clean up:

Code:

Validation Output:                                    15 Errors                             Line 472, Column 267:         document type does not allow element "body" here.…serv2.png','images/nav/employ2.png')">            ✉     
                  The element named above was found in a context where it is not allowed.       This could mean that you have incorrectly nested elements -- such as a       "style" element in the "body" section instead of inside "head" -- or       two elements that overlap (which is not allowed).     
            One common cause for this error is the use of XHTML syntax in HTML       documents. Due to HTML's rules of implicitly closed elements, this error       can create cascading effects. For instance, using XHTML's "self-closing"       tags for "meta" and "link" in the "head" section of a HTML document may       cause the parser to infer the end of the "head" section and the       beginning of the "body" section (where "link" and "meta" are not       allowed; hence the reported error).
                    Line 473, Column 73:         document type does not allow element "meta" here.…e" content="text/html; charset=iso-8859-1" />           ✉     
                  The element named above was found in a context where it is not allowed.       This could mean that you have incorrectly nested elements -- such as a       "style" element in the "body" section instead of inside "head" -- or       two elements that overlap (which is not allowed).     
            One common cause for this error is the use of XHTML syntax in HTML       documents. Due to HTML's rules of implicitly closed elements, this error       can create cascading effects. For instance, using XHTML's "self-closing"       tags for "meta" and "link" in the "head" section of a HTML document may       cause the parser to infer the end of the "head" section and the       beginning of the "body" section (where "link" and "meta" are not       allowed; hence the reported error).
                    Line 486, Column 6:         document type does not allow element "title" here.<title>CSI Security Inc. Homepage</title>           ✉     
                  The element named above was found in a context where it is not allowed.       This could mean that you have incorrectly nested elements -- such as a       "style" element in the "body" section instead of inside "head" -- or       two elements that overlap (which is not allowed).     
            One common cause for this error is the use of XHTML syntax in HTML       documents. Due to HTML's rules of implicitly closed elements, this error       can create cascading effects. For instance, using XHTML's "self-closing"       tags for "meta" and "link" in the "head" section of a HTML document may       cause the parser to infer the end of the "head" section and the       beginning of the "body" section (where "link" and "meta" are not       allowed; hence the reported error).
                    Line 487, Column 6:         end tag for "body" omitted, but OMITTAG NO was specified.</head>           ✉     
                    You may have neglected to close an element, or perhaps you meant to        "self-close" an element, that is, ending it with "/>" instead of ">".
                    Line 472, Column 0:         start tag was here.<body bgcolor="#000000" onload="MM_preloadImages('images/nav/contact_us2.png','i
                    Line 487, Column 6:         end tag for "head" which is not finished.</head>           ✉     
                  Most likely, you nested tags and closed them in the wrong order. For        example <p><em>...</p> is not acceptable, as <em>       must be closed before <p>. Acceptable nesting is:        <p><em>...</em></p>       
            Another possibility is that you used an element which requires       a child element that you did not include. Hence the parent element       is "not finished", not complete. For instance, in HTML the <head> element       must contain a <title> child element, lists (ul, ol, dl) require list items (li,        or dt, dd), and so on.
                    Line 497, Column 84:         required attribute "alt" not specified.…d_web.gif" width="398" height="266" /></div>           ✉     
                  The attribute given above is required for an element that you've used,       but you have omitted it. For instance, in most HTML and XHTML document       types the "type" attribute is required on the "script" element and the       "alt" attribute is required for the "img" element.     
            Typical values for type are        type="text/css" for <style>       and type="text/javascript" for <script>.
                    Line 503, Column 85:         required attribute "alt" not specified.…e_web.gif" width="345" height="221" /></div>           ✉     
                  The attribute given above is required for an element that you've used,       but you have omitted it. For instance, in most HTML and XHTML document       types the "type" attribute is required on the "script" element and the       "alt" attribute is required for the "img" element.     
            Typical values for type are        type="text/css" for <style>       and type="text/javascript" for <script>.
                    Line 504, Column 84:         required attribute "alt" not specified.…y_web.gif" width="182" height="182" /></div>           ✉     
                  The attribute given above is required for an element that you've used,       but you have omitted it. For instance, in most HTML and XHTML document       types the "type" attribute is required on the "script" element and the       "alt" attribute is required for the "img" element.     
            Typical values for type are        type="text/css" for <style>       and type="text/javascript" for <script>.
                    Line 505, Column 75:         required attribute "alt" not specified.…s/USCF_web.gif" width="806" height="201" /></div>           ✉     
                  The attribute given above is required for an element that you've used,       but you have omitted it. For instance, in most HTML and XHTML document       types the "type" attribute is required on the "script" element and the       "alt" attribute is required for the "img" element.     
            Typical values for type are        type="text/css" for <style>       and type="text/javascript" for <script>.
                    Line 510, Column 305:         there is no attribute "onload".…height="21" border="0" id="h" onload="" /></a></td>           ✉     
                  You have used the attribute named above in your document, but the       document type you are using does not support that attribute for this       element. This error is often caused by incorrect use of the "Strict"       document type with a document that uses frames (e.g. you must use       the "Transitional" document type to get the "target" attribute), or       by using vendor proprietary extensions such as "marginheight" (this       is usually fixed by using CSS to achieve the desired effect instead).     
            This error may also result if the element itself is not supported in       the document type you are using, as an undefined element will have no       supported attributes; in this case, see the element-undefined error       message for further information.     
            How to fix: check the spelling and case of the element and attribute,        (Remember XHTML is all lower-case) and/or        check that they are both allowed in the chosen document type, and/or       use CSS instead of this attribute. If you received this error when using the        <embed> element to incorporate flash media in a Web page, see the        FAQ item on valid flash.
                    Line 521, Column 82:         required attribute "alt" not specified.…ec_web.gif" width="312" height="77" /></div>           ✉     
                  The attribute given above is required for an element that you've used,       but you have omitted it. For instance, in most HTML and XHTML document       types the "type" attribute is required on the "script" element and the       "alt" attribute is required for the "img" element.     
            Typical values for type are        type="text/css" for <style>       and type="text/javascript" for <script>.
                    Line 522, Column 109:         required attribute "alt" not specified.…width="746" height="125" border="0" /></a></div>           ✉     
                  The attribute given above is required for an element that you've used,       but you have omitted it. For instance, in most HTML and XHTML document       types the "type" attribute is required on the "script" element and the       "alt" attribute is required for the "img" element.     
            Typical values for type are        type="text/css" for <style>       and type="text/javascript" for <script>.
                    Line 487, Column 7:         XML Parsing Error:  Opening and ending tag mismatch: body line 472 and head.</head>           ✉
                    Line 525, Column 7:         XML Parsing Error:  Opening and ending tag mismatch: head line 3 and html.</html>           ✉
                    Line 525, Column 7:         XML Parsing Error:  Premature end of data in tag html line 2.</html>

You have typos in your header: "hProviding Exceptional Security For Exceptional Clientsg", the h & g don't belong.

You need to adjust the height of images/grey_back_web.gif on the TSA Project page....it is overlapping your footer

I don't like the red on the contact page. It doesn't fit with the rest of the site and isn't visually appealing.

**imnewhere** · 03-19-2009, 06:05 PM

Awesome, thank you both!

I changed the red to blue in the contact page. It looks a whole lot better.

I'm working on the other problems. Thanks again.

**imnewhere** · 03-19-2009, 06:18 PM

BTW-Those are characters at the beggining and end of the header. Does it show up as letters to some people?

**nativewest** · 03-20-2009, 06:38 PM

I like the site every much, but I can still see it need some fine tuning.

**tim84** · 03-22-2009, 08:47 AM

Decent design. The only suggestion I have is using Arial fonts in place of Times New Romans. Makes reading on a computer screen easier.

**tanapatcha** · 03-22-2009, 11:17 AM

good design and cool

**Corey** · 03-23-2009, 04:14 AM

The buttons for the navigation are a little plain but the hover over gives it a nice look. The site in general seems kind of plain because of all the black. I would change the bottom links to match the site.

Are those crime facts correct? That's crazy.

**ashokyadav** · 03-23-2009, 10:33 AM

nice design and cool ..i love like this,,,,

**imnewhere** · 03-24-2009, 11:02 PM

Thank you-I'm taking everything into consideration.