Please help me to find ma errors in this page also suggest any ideas in design Site :http://www.synod.in/
Check your all errors in w3c validator it will give your all errors related codding and for checking a good design part visit @ Google Analytic tool > in page analytic it will give you the information about which part is most clicked according to this you can give user friendly options in your site.
Well, you have errors that even the validator wouldn't pick up -- mostly due to the age of the markup; or at least what I'm assuming is the age given it's built with fifteen year out of date methodologies. The very first line declares that proudly -- transitional; which is to say the code is in transition from 1997 to 1998 coding practices... This is borne out by the HTML 3.2 tags (uppercase) in a XHTML doctype... You've got a whole slew of endless pointless META tags that nothing actually uses, and even some outright fictional made-up ones like "keyphrases" -- which seems to be a copy of keywords, which is massively overstuffed with phrases that don't even match the document content. It's called keyWORDS. that means six to eight WORDS, preferably under 128 characters, that exist inside BODY. Not keyphrases, not keysentences, keyWORDS! It gets worse from there -- Endless pointless javascript for christmas only knows what, static scripting and static style inlined in the markup, endless pointless DIV for not reason, non-semantic markup, and even nonsensical use of numbered headings... <h2 >Welcome to</h2> <h1>synod bioscience</h1> For example -- H2 preceding a H1? That makes no sense, what even makes those two separate headings? They're not starting two separate subsections... and I'm willing to bet that H1 shouldn't even be in the mix there since EVERY h2 is supposed to be the start of a subsection of the H1... just as h3 mark the start of subsections of the h2, h4 are subsections of the H3's... which is why your skipping to H4's without any H3's and immediately following a H1 is also gibberish... Of course that giant grey area where the blocked plugin would go, likely being some giant flashtard nonsense that has no business on websites in the first place... Not good. You've got inline-level tags wrapping block level tags, tags nested in places they can't even go like putting a DIV wrapping LI inside a UL, etc, etc... ... and that's before even talking about the "not viable for web deployment if you care about accessibility" layout -- with the equal-width equal-height three across section, fixed width, absurdly undersized fixed metric (px) fonts, illegible color contrasts (black on dark grey? REALLY?)... It's just another "throw it all away and star over", preferably building with techniques from sometime over the past decade instead of the decade before that -- there's nothing worth trying to save from that in terms of design or code.