Errors found while checking this document as HTML5!

Result: 26 Errors, 6 warning(s)
:
: utf-8
: HTML5
Root Element: html
Options

Help on the options is available.

Notes and Potential Issues

The following notes and warnings highlight missing or conflicting information which caused the validator to perform some guesswork prior to validation, or other things affecting the output below. If the guess or fallback is incorrect, it could make validation results entirely incoherent. It is highly recommended to check these potential issues, and, if necessary, fix them and re-validate the document.

  1. Info Using experimental feature: HTML5 Conformance Checker.

    The validator checked your document with an experimental feature: HTML5 Conformance Checker. This feature has been made available for your convenience, but be aware that it may be unreliable, or not perfectly up to date with the latest development of some cutting-edge technologies. If you find any issues with this feature, please report them. Thank you.

↑ Top

Validation Output: 26 Errors

  1. Warning Line 9, Column 3: Comments seen before doctype. Internet Explorer will go into the quirks mode.
    -->

  2. Error Line 32, Column 26: Consecutive hyphens did not terminate a comment. -- is not permitted inside a comment, but e.g. - - is.
    		<!--<base href="/" />--

  3. Warning Line 32, Column 26: The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.
    		<!--<base href="/" />--

  4. Error Line 33, Column 7: Consecutive hyphens did not terminate a comment. -- is not permitted inside a comment, but e.g. - - is.
    		<!-- For less capable mobile browsers

  5. Warning Line 33, Column 7: The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.
    		<!-- For less capable mobile browsers

  6. Error Line 41, Column 53: Attribute content not allowed on element meta at this point.
    		<meta property="og:title" content="1020concepts" />
  7. Error Line 42, Column 47: Attribute content not allowed on element meta at this point.
    		<meta property="og:type" content="company" />
  8. Error Line 43, Column 61: Attribute content not allowed on element meta at this point.
    		<meta property="og:url" content="http://1020concepts.nl" />
  9. Error Line 44, Column 95: Attribute content not allowed on element meta at this point.
    …="og:image" content="http://1020concepts.nl/images/logo_1020concepts.nl.png" />
  10. Error Line 45, Column 57: Attribute content not allowed on element meta at this point.
    		<meta property="og:site_name" content="1020concepts" />
  11. Error Line 46, Column 52: Attribute content not allowed on element meta at this point.
    		<meta property="fb:admins" content="1521993711" />
  12. Error Line 47, Column 58: Attribute content not allowed on element meta at this point.
    		<meta property="fb:page_id" content="130173817019531" />
  13. Error Line 51, Column 66: & did not start a character reference. (& probably should have been escaped as &amp;.)
    …ts.googleapis.com/css?family=Josefin+Slab&v2' rel='stylesheet' type='text/css'>

  14. Error Line 68, Column 80: Bad value publisher for attribute rel on element link: Keyword publisher is not registered.
    		<link href="https://plus.google.com/104957245611994122067/" rel="publisher" />
    Syntax of link type valid for <link>:
    A whitespace-separated list of link types listed as allowed on <link> in the HTML specification or listed as an allowed on <link> on the Microformats wiki without duplicate keywords in the list. You can register link types on the Microformats wiki yourself.
  15. Error Line 80, Column 64: Bad value X-UA-Compatible for attribute http-equiv on element meta.
    		<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">

  16. Error Line 95, Column 82: Element nowrap not allowed as child of element a in this context. (Suppressing further errors from this subtree.)
    …e="Call us" class="call">Call us: <nowrap>+31 (0)6 484 282 56</nowrap></a></li>
    Content model for element a:
    Transparent, but there must be no interactive content descendant.
  17. Error Line 123, Column 186: Bad value tel:+31 6 484 282 56 for attribute href on element a: Whitespace in path component. Use %20 in place of spaces.
    …ref="tel:+31 6 484 282 56" title="call 1020concepts">+ 31 6 484 282 56</a>.</p>
    Syntax of IRI reference:
    Any URL. For example: /hello, #canvas, or http://example.org/. Characters should be represented in NFC and spaces should be escaped as %20.
  18. Warning Line 335, Column 19: The name attribute is obsolete. Consider putting an id attribute on the nearest container instead.
    				<a name="send"></a>

  19. Error Line 352, Column 146: Bad value https://twitter.com/intent/tweet?text=1020concepts, mobile webdesign %26 development, Rotterdam - http://1020concepts.nl/ for attribute href on element a: Whitespace in query component. Use %20 in place of spaces.
    …%26 development, Rotterdam - http://1020concepts.nl/" >Tweet this page</a></li>
    Syntax of IRI reference:
    Any URL. For example: /hello, #canvas, or http://example.org/. Characters should be represented in NFC and spaces should be escaped as %20.
  20. Error Line 353, Column 149: Bad value https://www.facebook.com/sharer/sharer.php?u=1020concepts, mobile webdesign %26 development, Rotterdam - http://1020concepts.nl/ for attribute href on element a: Whitespace in query component. Use %20 in place of spaces.
    …ment, Rotterdam - http://1020concepts.nl/">Share this page on Facebook</a></li>
    Syntax of IRI reference:
    Any URL. For example: /hello, #canvas, or http://example.org/. Characters should be represented in NFC and spaces should be escaped as %20.
  21. Error Line 354, Column 66: & did not start a character reference. (& probably should have been escaped as &amp;.)
    …ww.linkedin.com/shareArticle?mini=true&url= &title=1020concepts&summary=Mobile…

  22. Error Line 354, Column 72: & did not start a character reference. (& probably should have been escaped as &amp;.)
    …kedin.com/shareArticle?mini=true&url= &title=1020concepts&summary=Mobile webde…

  23. Error Line 354, Column 91: & did not start a character reference. (& probably should have been escaped as &amp;.)
    …cle?mini=true&url= &title=1020concepts&summary=Mobile webdesign %26 developmen…

  24. Error Line 354, Column 169: & did not start a character reference. (& probably should have been escaped as &amp;.)
    …t, Rotterdam - http://1020concepts.nl/&source=http://1020concepts.nl">Share th…

  25. Error Line 354, Column 200: Bad value http://www.linkedin.com/shareArticle?mini=true&url= &title=1020concepts&summary=Mobile webdesign %26 development, Rotterdam - http://1020concepts.nl/&source=http://1020concepts.nl for attribute href on element a: Whitespace in query component. Use %20 in place of spaces.
    …oncepts.nl/&source=http://1020concepts.nl">Share this page on LinkedIN</a></li>
    Syntax of IRI reference:
    Any URL. For example: /hello, #canvas, or http://example.org/. Characters should be represented in NFC and spaces should be escaped as %20.
  26. Warning Line 360, Column 48: Element name g:plusone cannot be represented as XML 1.0.
    			    		<g:plusone count="false" size="medium"></g:plusone>

  27. Error Line 360, Column 48: Element g:plusone not allowed as child of element div in this context. (Suppressing further errors from this subtree.)
    			    		<g:plusone count="false" size="medium"></g:plusone>
    Content model for element div:
    Flow content.
  28. Error Line 361, Column 174: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
    …ttps://ssl.gstatic.com/images/icons/gplus-32.png" width="20" height="20" /></a>

  29. Error Line 394, Column 11: End tag div seen, but there were open elements.
    					</div>

  30. Error Line 392, Column 24: Unclosed element span.
    						<span class="adr"><span class="street-address">Lombardkade 48D</span>, <s…

  31. Error Line 397, Column 143: Bad value http://www.technorati.com/tag/Mobile webdesign Rotterdam for attribute href on element a: Whitespace in path component. Use %20 in place of spaces.
    …w.technorati.com/tag/Mobile webdesign Rotterdam">Mobile webdesign Rotterdam</a>
    Syntax of IRI reference:
    Any URL. For example: /hello, #canvas, or http://example.org/. Characters should be represented in NFC and spaces should be escaped as %20.

↑ Top