hotelguru.ro

Hoteluri, case de oaspeti, apartamente, pachete wellness la cele mai mici preturi garantate. Rezervati la noi, platiti la hotel si beneficiati de reducerile portalului Hotelguru.ro! ...

Display Widget for this domain on your website. Click Here
This data was last updated from 16-07-2013 03:50:47  (update).

Overview Info

  • Domain Name
    hotelguru.ro
  • Favicon
  • Alexa Rank
    #452627
  • Google Page Rank
    PR 4
  • Ip Address
    77.111.91.50
  • Page Size
    68.7 KB
  • Images
    0 GIF, 6 JPG, 1 PNG
  • Heading
    H1 H2 H3 H4 H5 H6
    0 11 9 0 0 0

Website Meta Analysis



  • Title
    Hotelguru.ro - Rezervati la noi, platiti la hotel!
  • Meta Keyword
  • Meta Description
    Hoteluri, case de oaspeti, apartamente, pachete wellness la cele mai mici preturi garantate. Rezervati la noi, platiti la hotel si beneficiati de reducerile portalului Hotelguru.ro!

Technical Analysis



  • Webserver
    nginx
  • Ip Address
    77.111.91.50
  • Domain Age
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from hotelguru.ro.

HTML Analysis

  • server: nginx
  • date: Tue, 16 Jul 2013 03:50:45 GMT
  • content-type: text/html; charset=utf-8
  • connection: keep-alive
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-cache
  • pragma: no-cache
  • w: wm30.sanomaonline.hu
  • content-encoding: gzip
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for hotelguru.ro

DNS Analysis


DNS servers
ns2.szallas.hu [83.137.158.17]
ns1.szallas.hu [83.137.158.16]

DNS Records

Answer records
hotelguru.ro MX
preference: 10
exchange: mail.szallas.hu
3600s
hotelguru.ro A 83.137.158.16 3600s
hotelguru.ro SOA
server: ns1.szallas.hu
email: szallas@szallas.hu
serial: -1093905453
refresh: 86400
retry: 7200
expire: 3600000
minimum ttl: 3600
3600s
hotelguru.ro NS  ns1.szallas.hu 3600s
hotelguru.ro NS  ns2.szallas.hu 3600s

Authority records

Additional records

IP 77.111.91.50 Analysis

  • Country Code
  • Country Code3
  • Country Name
  • City
  • Continent Code
  • Latitude
  • Longitude
  • No whois ip data for 77.111.91.50

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 20 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.6397676103353741
Message Error
  • Error Line 24, Column 75: required attribute "type" not specified
    …script src="http://static.szallas.hu/uncooked/js/jquery-1.9.0.min.js"></script>

    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>.

  • Error Line 26, Column 85: required attribute "type" not specified
    …="http://ajax.googleapis.com/ajax/libs/jqueryui/1.8/jquery-ui.min.js"></script>

    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>.

  • Warning Line 45, Column 37: character "&" is the first character of a delimiter but occurred as data
                                url += '&';

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  • Error Line 166, Column 46: "itemscope" is not a member of a group specified for any attribute
    …dy onload="trackSocNetworks();" itemscope itemtype="http://schema.org/WebPage">
  • Error Line 166, Column 55: there is no attribute "itemtype"
    …dy onload="trackSocNetworks();" itemscope itemtype="http://schema.org/WebPage">

    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.

  • Error Line 171, Column 27: there is no attribute "src"
        <noscript><iframe src="http://www.googletagmanager.com/ns.html?id=GTM-KMV4&…

    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.

  • Warning Line 171, Column 80: cannot generate system identifier for general entity "pageType"
    … src="http://www.googletagmanager.com/ns.html?id=GTM-KMV4&pageType=staticOther"

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 171, Column 80: general entity "pageType" not defined and no default entity
    … src="http://www.googletagmanager.com/ns.html?id=GTM-KMV4&pageType=staticOther"

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 171, Column 88: reference not terminated by REFC delimiter
    … src="http://www.googletagmanager.com/ns.html?id=GTM-KMV4&pageType=staticOther"

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Warning Line 171, Column 88: reference to external entity in attribute value
    … src="http://www.googletagmanager.com/ns.html?id=GTM-KMV4&pageType=staticOther"

    This is generally the sign of an ampersand that was not properly escaped for inclusion in an attribute, in a href for example. You will need to escape all instances of '&' into '&amp;'.

  • Error Line 171, Column 88: reference to entity "pageType" for which no system identifier could be generated
    … src="http://www.googletagmanager.com/ns.html?id=GTM-KMV4&pageType=staticOther"

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 171, Column 79: entity was defined here
    … src="http://www.googletagmanager.com/ns.html?id=GTM-KMV4&pageType=staticOther"
  • Error Line 172, Column 12: there is no attribute "height"
        height="0" width="0" style="display:none;visibility:hidden"></iframe></nosc…

    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.

  • Error Line 172, Column 22: there is no attribute "width"
        height="0" width="0" style="display:none;visibility:hidden"></iframe></nosc…

    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.

  • Error Line 172, Column 32: there is no attribute "style"
        height="0" width="0" style="display:none;visibility:hidden"></iframe></nosc…

    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.

  • Error Line 172, Column 64: element "iframe" undefined
    …eight="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 172, Column 84: end tag for "noscript" which is not finished
    …eight="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>

    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 require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 173, Column 12: required attribute "type" not specified
        <script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':

    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>.

  • Warning Line 175, Column 46: cannot generate system identifier for general entity "l"
        j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  • Error Line 175, Column 46: general entity "l" not defined and no default entity
        j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Warning Line 175, Column 47: reference not terminated by REFC delimiter
        j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  • Error Line 175, Column 47: reference to entity "l" for which no system identifier could be generated
        j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  • Info Line 175, Column 45: entity was defined here
        j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
  • Error Line 257, Column 130: there is no attribute "onMouseOver"
    … <div class="icon_clock"  onMouseOver="document.getElementById('phone_interval…

    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.

  • Error Line 257, Column 209: there is no attribute "onMouseOut"
    …').style.display='block';" onMouseOut="document.getElementById('phone_interval…

    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.

  • Error Line 367, Column 219: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …utton_mainpage_seasonoffer_bgimage_ro">Statiuni de schi, cazari &raquo;</div><…

    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>").

  • Error Line 448, Column 486: there is no attribute "autocomplete"
    …imple_input').addClassName('form_elements_big_inactive') }" autocomplete="off">

    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.

  • Error Line 448, Column 492: end tag for "input" omitted, but OMITTAG NO was specified
    …imple_input').addClassName('form_elements_big_inactive') }" autocomplete="off">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 448, Column 29: start tag was here
                                <input type="text" id="location_simple_input" name=…
  • Error Line 449, Column 87: end tag for "input" omitted, but OMITTAG NO was specified
    …                     <input type="hidden" id="location_simple" name="location">

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 449, Column 29: start tag was here
                                <input type="hidden" id="location_simple" name="loc…
  • Error Line 467, Column 11: document type does not allow element "td" here; assuming missing "tr" start-tag
    							<td><strong class="bigfont_14">Sosire:</strong></td>
  • Error Line 482, Column 40: document type does not allow element "script" here
    					    <script type="text/javascript">

    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).

  • Error Line 508, Column 31: document type does not allow element "script" here
    <script type="text/javascript">

    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).

  • Error Line 524, Column 44: document type does not allow element "div" here
    						<div class="clearboth marginbottom_5"></div>

    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).

  • Error Line 527, Column 157: the name and VI delimiter can be omitted from an attribute specification only if SHORTTAG YES is specified
    …"searchPackages" value="yes" checked /><strong>doresc sa caut si printre ofert…

    "VI delimiter" is a technical term for the equal sign. This error message means that the name of an attribute and the equal sign cannot be omitted when specifying an attribute. A common cause for this error message is the use of "Attribute Minimization" in document types where it is not allowed, in XHTML for instance.

    How to fix: For attributes such as compact, checked or selected, do not write e.g <option selected ... but rather <option selected="selected" ...

  • Error Line 531, Column 154: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …"javascript:performSimpleSearch();"><div class="icon_magnify"></div>Cautare</a>

    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>").

  • Error Line 533, Column 147: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …P();" class="usp_button"><div class="positive_stick"></div>Avantaj garantat</a>

    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>").

  • Error Line 541, Column 41: end tag for "br" omitted, but OMITTAG NO was specified
    …	<p>Garantat cele mai bune preturi<br><span>Pentru tarifele afisate <a href="g…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 541, Column 37: start tag was here
    			<p>Garantat cele mai bune preturi<br><span>Pentru tarifele afisate <a href="…
  • Error Line 547, Column 53: end tag for "br" omitted, but OMITTAG NO was specified
    …cazare, 108.700+ evaluari clienti <br><span> Numarul unitatilor de cazare este…

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 547, Column 49: start tag was here
    …00+ cazare, 108.700+ evaluari clienti <br><span> Numarul unitatilor de cazare …
  • Error Line 553, Column 38: end tag for "br" omitted, but OMITTAG NO was specified
    			<p>Nu exista taxa de rezervare<br><span> In comparatie cu alte site-uri noi …

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 553, Column 34: start tag was here
    			<p>Nu exista taxa de rezervare<br><span> In comparatie cu alte site-uri noi …
  • Error Line 562, Column 35: end tag for "br" omitted, but OMITTAG NO was specified
    			<p>Veti plati doar la hotel<br><span>Fara taxa de rezervare:)</span></p>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 562, Column 31: start tag was here
    			<p>Veti plati doar la hotel<br><span>Fara taxa de rezervare:)</span></p>
  • Error Line 584, Column 50: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …<div class="main_page_simple_box_active_tab"><h2>Categorii de pachet</h2></div>

    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>").

  • Error Line 587, Column 132: document type does not allow element "h2" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …');" class="main_page_simple_box_inactive_tab"><h2>Categorii de pachet</h2></a>

    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>").

  • Error Line 588, Column 50: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …lass="main_page_simple_box_active_tab"><h2>Unitati de cazare vizualizate</h2><…

    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>").

  • Error Line 594, Column 45: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    							<div class="package_icon icon_easter"></div>

    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>").

  • Error Line 598, Column 48: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    							<div class="package_icon icon_valentine"></div>

    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>").

  • Error Line 602, Column 47: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    							<div class="package_icon icon_wellness"></div>

    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>").

  • Error Line 606, Column 45: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    							<div class="package_icon icon_winter"></div>

    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>").

  • Error Line 610, Column 43: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    							<div class="package_icon icon_none"></div>

    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>").

  • Error Line 614, Column 45: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    							<div class="package_icon icon_spring"></div>

    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>").

  • Error Line 618, Column 48: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    							<div class="package_icon icon_giftnight"></div>

    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>").

  • Error Line 625, Column 17: end tag for "table" which is not finished
    									</table>

    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 require appropriate list items (<ul> and <ol> require <li>; <dl> requires <dt> and <dd>), and so on.

  • Error Line 633, Column 150: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    …p" class="main_page_package_offer_slide_arrow"><div class="arrow_up"></div></a>

    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>").

  • Error Line 637, Column 351: required attribute "alt" not specified
    …mages.szallas.hu/packages/1153768/80x60/708065.jpg" class="pictures"></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>.

  • Error Line 637, Column 355: end tag for "img" omitted, but OMITTAG NO was specified
    …mages.szallas.hu/packages/1153768/80x60/708065.jpg" class="pictures"></a></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 637, Column 265: start tag was here
    …ferte-pentru-weekend/1-martie2013');"><img src="http://images.szallas.hu/packa…
  • Error Line 650, Column 417: required attribute "alt" not specified
    …mages.szallas.hu/packages/1153690/80x60/707989.jpg" class="pictures"></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>.

  • Error Line 650, Column 421: end tag for "img" omitted, but OMITTAG NO was specified
    …mages.szallas.hu/packages/1153690/80x60/707989.jpg" class="pictures"></a></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 650, Column 331: start tag was here
    …norama-panzio-tusnadfurdo-1153690');"><img src="http://images.szallas.hu/packa…
  • Error Line 663, Column 361: required attribute "alt" not specified
    …/images.szallas.hu/hotels/466504/80x60/2943620.jpg" class="pictures"></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>.

  • Error Line 663, Column 365: end tag for "img" omitted, but OMITTAG NO was specified
    …/images.szallas.hu/hotels/466504/80x60/2943620.jpg" class="pictures"></a></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 663, Column 277: start tag was here
    …erte-ce-nu-puteti-pierde/reducere');"><img src="http://images.szallas.hu/hotel…
  • Error Line 676, Column 357: required attribute "alt" not specified
    …/images.szallas.hu/hotels/472578/80x60/3022639.jpg" class="pictures"></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>.

  • Error Line 676, Column 361: end tag for "img" omitted, but OMITTAG NO was specified
    …/images.szallas.hu/hotels/472578/80x60/3022639.jpg" class="pictures"></a></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 676, Column 273: start tag was here
    …r-bran/oferta-de-paste/paste-2013');"><img src="http://images.szallas.hu/hotel…
  • Error Line 688, Column 154: document type does not allow element "div" here; missing one of "button", "map", "object", "ins", "del", "noscript" start-tag
    … class="main_page_package_offer_slide_arrow"><div class="arrow_down"></div></a>

    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>").

  • Error Line 704, Column 28: there is no attribute "width"
    	                <td width="180" align="right">

    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.

  • Error Line 815, Column 278: there is no attribute "target"
    …lte detalii va rugam cititi <a target="_blank" href="/declaratie-de-confidenti…

    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.

  • Error Line 836, Column 31: there is no attribute "width"
    				                <th width="70" align="right">Oras</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.

  • Error Line 836, Column 58: end tag for element "td" which is not open
    				                <th width="70" align="right">Oras</td>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 837, Column 50: document type does not allow element "th" here
    				                <th width="110" align="right">Cand</td>

    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).

  • Error Line 837, Column 59: end tag for element "td" which is not open
    				                <th width="110" align="right">Cand</td>

    The Validator found an end tag for the above element, but that element is not currently open. This is often caused by a leftover end tag from an element that was removed during editing, or by an implicitly closed element (if you have an error related to an element being used where it is not allowed, this is almost certainly the case). In the latter case this error will disappear as soon as you fix the original problem.

    If this error occurred in a script section of your document, you should probably read this FAQ entry.

  • Error Line 838, Column 21: end tag for "th" omitted, but OMITTAG NO was specified
    				            </tr>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 837, Column 21: start tag was here
    				                <th width="110" align="right">Cand</td>
  • Error Line 838, Column 21: end tag for "th" omitted, but OMITTAG NO was specified
    				            </tr>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 836, Column 21: start tag was here
    				                <th width="70" align="right">Oras</td>
  • Error Line 1009, Column 260: end tag for "img" omitted, but OMITTAG NO was specified
    ….szallas.hu/hotels/472034/80x60/3021754.jpg" alt="" class="pictures"></a></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1009, Column 165: start tag was here
    …_0_hotelurl', 'rigo-villa-szovata');"><img src="http://images.szallas.hu/hotel…
  • Error Line 1026, Column 262: end tag for "img" omitted, but OMITTAG NO was specified
    ….szallas.hu/hotels/465280/80x60/2930445.jpg" alt="" class="pictures"></a></div>

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  • Info Line 1026, Column 167: start tag was here
    …1_hotelurl', 'vila-select-predeal');"><img src="http://images.szallas.hu/hotel…
  • Error Line 1098, Column 301: there is no attribute "scrolling"
    …&amp;appId=120536731373428" scrolling="no" frameborder="0" style="border:none;…

    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.

  • Error Line 1098, Column 318: there is no attribute "frameborder"
    …731373428" scrolling="no" frameborder="0" style="border:none; overflow:hidden;…

    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.

  • Error Line 1098, Column 404: there is no attribute "allowTransparency"
    …erflow:hidden; width:100%; height:258px;" allowTransparency="true"></iframe>');

    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.

  • Error Line 1098, Column 410: element "iframe" undefined
    …erflow:hidden; width:100%; height:258px;" allowTransparency="true"></iframe>');

    You have used the element named above in your document, but the document type you are using does not define an element of that name. 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 "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  • Error Line 1168, Column 30: there is no attribute "noshade"
    		<hr class="dotted" noshade="noshade" />

    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.

  • Error Line 1169, Column 14: there is no attribute "align"
    		<div align="center">Copyright 2008-2013.

    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.

  • Error Line 1176, Column 161: document type does not allow element "a" here; missing one of "ins", "del", "h1", "h2", "h3", "h4", "h5", "h6", "p", "div", "pre", "address", "fieldset" start-tag
    …h=450,height=420,resizable=0,dependent=1,status=0')" class="feedback_icon"></a>

    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>").

Visitor Analysis

Daily Visitor
  • 280 visits

In Page Analysis