Jump to content

Need input on my website


dink

Recommended Posts

I am revamping my site and would like your opinions on what I have done so far.Visit My WebsiteThere are two pages I am having difficulty with. The forms are not showing and I am working on that.http://adinkado.com/contact.htmhttp://www.adinkado.com/quoterequest.htmYour suggestions and comments are greatly appreciated.dink

Link to comment
Share on other sites

1) The header image is way to heavy- 190K. Even on a broadband connection it takes a noticeable time to fill in. 2) Things like CSS and XHTML "valid" buttons should be placed in the footer so they don't clutter the primary content area.3) The font size used is (in my opinion) too small; I would also use a sans-serif font instead of Times New Roman. 4) The left-side scroller tends to become annoying after a while. 5) The down arrows in the menu bar have unattractive outlines around them, and the menu bar itself looks...odd. I don't think the image hidden in between the menu blocks looks good, but that's just my take on it. 6) The portfolio images in the header should be clickable and lead to larger images, in my opinion.

Link to comment
Share on other sites

It does seem a bit boxy and plain. And the name kinda seems less than inspiring. It seems to be a bit disingenuous to have the HTML/CSS valid icons, when you're page has errors on it. It's also using a transitional DTD....

Link to comment
Share on other sites

It does seem a bit boxy and plain. And the name kinda seems less than inspiring. It seems to be a bit disingenuous to have the HTML/CSS valid icons, when you're page has errors on it. It's also using a transitional DTD....
Thank you for all your comments.I validated all the pages that have the valid icons and did not get any errors. If you could please tell me what errors you found so I can fix them.I will redo the header image, I didn't like it either.What do you mean by it looks boxy? Any suggestions on how to unbox?I will loose the graphics separating the menu items and remove the border.I will enlarge the text size to 1em.Your suggestions were very helpful!I appreciate your time to look and offer advice.dink
Link to comment
Share on other sites

this is from the home page

1. Error Line 17, Column 23: document type does not allow element "br" here pausecontent[0]='<br /><br /><br /><center />$ $ $<p class="info1">We have lowe… ✉ 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). 2. Error Line 17, Column 29: document type does not allow element "br" here pausecontent[0]='<br /><br /><br /><center />$ $ $<p class="info1">We have lowe… ✉ 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). 3. Error Line 17, Column 35: document type does not allow element "br" here pausecontent[0]='<br /><br /><br /><center />$ $ $<p class="info1">We have lowe… ✉ 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). 4. Error Line 17, Column 45: document type does not allow element "center" here …ontent[0]='<br /><br /><br /><center />$ $ $<p class="info1">We have lowered o… ✉ 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). 5. Error Line 17, Column 67: document type does not allow element "p" here …><br /><center />$ $ $<p class="info1">We have lowered our prices again! </p><… ✉ 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). 6. Error Line 17, Column 115: document type does not allow element "center" here … />$ $ $<p class="info1">We have lowered our prices again! </p><center />$ $ $' ✉ 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). 7. Error Line 19, Column 34: document type does not allow element "p" here pausecontent[1]='<p class="info1"><center />Specials</p><p class="info2">End of… ✉ 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). 8. Error Line 19, Column 44: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag …content[1]='<p class="info1"><center />Specials</p><p class="info2">End of Sum… ✉ The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>"). 9. Error Line 19, Column 73: document type does not allow element "p" here …<center />Specials</p><p class="info2">End of Summer </p>End a project by Sept… ✉ 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). 10. Error Line 19, Column 171: document type does not allow element "br" here …ceive an additional 10% discount.<br /><br /><p class="info2"> Halloween Speci… ✉ 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). 11. Error Line 19, Column 177: document type does not allow element "br" here …an additional 10% discount.<br /><br /><p class="info2"> Halloween Special!</p… ✉ 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). 12. Error Line 19, Column 194: document type does not allow element "p" here … discount.<br /><br /><p class="info2"> Halloween Special!</p>October get a 7%… ✉ 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). 13. Error Line 21, Column 23: document type does not allow element "br" here pausecontent[2]='<br /><br /><br /><br /><center />Senior Citzen discount 10%!<… ✉ 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). 14. Error Line 21, Column 29: document type does not allow element "br" here pausecontent[2]='<br /><br /><br /><br /><center />Senior Citzen discount 10%!<… ✉ 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). 15. Error Line 21, Column 35: document type does not allow element "br" here pausecontent[2]='<br /><br /><br /><br /><center />Senior Citzen discount 10%!<… ✉ 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). 16. Error Line 21, Column 41: document type does not allow element "br" here …usecontent[2]='<br /><br /><br /><br /><center />Senior Citzen discount 10%!<b… ✉ 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). 17. Error Line 21, Column 51: document type does not allow element "center" here …[2]='<br /><br /><br /><br /><center />Senior Citzen discount 10%!<br /><br />… ✉ 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). 18. Error Line 21, Column 84: document type does not allow element "br" here …ter />Senior Citzen discount 10%!<br /><br /><br />Churches and nonprofit orga… ✉ 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). 19. Error Line 21, Column 90: document type does not allow element "br" here …Senior Citzen discount 10%!<br /><br /><br />Churches and nonprofit organizati… ✉ 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). 20. Error Line 21, Column 96: document type does not allow element "br" here … Citzen discount 10%!<br /><br /><br />Churches and nonprofit organizations in… ✉ 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). 21. Error Line 23, Column 34: document type does not allow element "p" here pausecontent[3]='<p class="info1"><center />Offering maintenance plans to you a… ✉ 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). 22. Error Line 23, Column 44: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag …content[3]='<p class="info1"><center />Offering maintenance plans to you and/o… ✉ The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>"). 23. Error Line 23, Column 146: document type does not allow element "center" here; missing one of "object", "applet", "map", "iframe", "button", "ins", "del" start-tag …hidden service charges.<br /><center /><br />Daily<br /><br />Weekly<br /><br … ✉ The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element. One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").
I have the web developers toolbar for FF that shows the errors in it and takes you to the validator page. You could also just click the W3C valid icon on your page and it will do the same thing.As far as the boxiness thing goes, maybe try looking up some free CSS templates and gleam what you can from those. Maybe some rounded corners? I guess its not in that its too "boxy", but that it doesn't look inspired. Design is hard though, functionality is (arguably) easy. At least the content on your site is easy to get to. although being able to visit the sites in your portfolio section might be a good feature.
Link to comment
Share on other sites

Oh my gosh!!!! I must have changed something after I validated it. So sorry!dink
The errors have been fixed and it does validate. Again, I am so sorry but thanks for pointing that out.dink
Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...