يومية جزائرية مستقلة ...

al-fadjr.com
  • Domain Name
    al-fadjr.com
  • Favicon
  • Google Page Rank
    6
  • Alexa Rank
    #24561
  • Page Size
    219.9 KB
  • Ip Address
    188.165.196.180
  • Heading
    H1: 2, H2: 2, H3: 139, H4: 17, H5: 0, H6: 0
  • Images
    0 GIF, 48 JPG, 0 PNG

Website Meta Analysis

  • Title
    الفجر - يومية جزائرية مستقلة
  • Meta Keyword
    alger, algeria, al fadjr, alfadjr, alfedjr, journal, presse, press, algerie, algérie,الفجر,الفجر الجزائرية,elfadjr,
  • Meta Description
    يومية جزائرية مستقلة

Technical Analysis

  • Webserver
    Apache/2.2.15 (CentOS)
  • Ip Address
    188.165.196.180
  • Domain Age
    12 Years, 9 Months, 20 days.
  • Javascript Library
    jquery
  • Language used
    HTML, CSS, Javascript

Hyper Text Transfer Protocol (HTTP) header show data header response from al-fadjr.com.

HTML Analysis

  • date: Sun, 30 Nov 2014 20:04:53 GMT
  • server: Apache/2.2.15 (CentOS)
  • x-powered-by: PHP/5.4.14
  • expires: Thu, 19 Nov 1981 08:52:00 GMT
  • cache-control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
  • pragma: no-cache
  • content-encoding: gzip
  • vary: Accept-Encoding
  • connection: close
  • content-type: text/html; charset=UTF-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA
No data whois for al-fadjr.com

DNS Analysis


DNS servers
ns1.marketjuice.com [216.55.153.128]
ns2.marketjuice.com [216.55.153.129]
ns3.marketjuice.com [216.55.153.130]


DNS Records

Answer records
al-fadjr.com A 64.29.151.221 86400s
al-fadjr.com MX
preference: 1
exchange: aspmx.l.google.com
86400s
al-fadjr.com NS  ns1.aplus.net 86400s
al-fadjr.com NS  ns2.aplus.net 86400s
al-fadjr.com SOA
server: ns1.aplus.net
email: hostmaster@aplus.net
serial: 2012112503
refresh: 7200
retry: 86400
expire: 3600000
minimum ttl: 86400
86400s

Authority records
al-fadjr.com NS  ns1.aplus.net 86400s
al-fadjr.com NS  ns2.aplus.net 86400s

Additional records
ns1.aplus.net A 209.235.144.103 300s
ns2.aplus.net A 66.175.41.121 300s
ns1.aplus.net 28 [16 bytes] 300s
ns2.aplus.net 28 [16 bytes] 300s

IP 188.165.196.180 Analysis

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

In Page Analysis

Traffic Analysis

Magestic Backlinks
Daily Ranks
Rank Trend
Visitor Trend
Bounce Trend

HTML Analysis

HTML validation
  • 445 Errors
  • 2 Warnings
Ratio Text/Html
  • 0.757769299441703
Message Error
  • Error Line 44, Column 19: there is no attribute "wmode"
    					<embed wmode="transparent" src="http://www.al-fadjr.com/ar/themes/rtl/img/…

    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 44, Column 37: there is no attribute "src"
    					<embed wmode="transparent" src="http://www.al-fadjr.com/ar/themes/rtl/img/…

    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 44, Column 100: there is no attribute "quality"
    …ar/themes/rtl/img/header.swf" quality="high" pluginspage="http://www.adobe.com…

    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 44, Column 119: there is no attribute "pluginspage"
    …eader.swf" quality="high" pluginspage="http://www.adobe.com/shockwave/download…

    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 44, Column 210: there is no attribute "type"
    …?P1_Prod_Version=ShockwaveFlash" type="application/x-shockwave-flash" width="9…

    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 44, Column 248: there is no attribute "width"
    …=ShockwaveFlash" type="application/x-shockwave-flash" width="959" height="90"> 

    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 44, Column 261: there is no attribute "height"
    …=ShockwaveFlash" type="application/x-shockwave-flash" width="959" height="90"> 

    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 44, Column 265: element "embed" undefined
    …=ShockwaveFlash" type="application/x-shockwave-flash" width="959" height="90"> 

    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 45, Column 13: end tag for "embed" omitted, but OMITTAG NO was specified
    				</object>

    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 44, Column 6: start tag was here
    					<embed wmode="transparent" src="http://www.al-fadjr.com/ar/themes/rtl/img/…
  • Error Line 56, Column 112: element "embed" undefined
    …/files/banners/espace_PUB_437176430.swf" width="959" height="99"></embed></div>

    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 66, Column 263: element "embed" undefined
    …=ShockwaveFlash" type="application/x-shockwave-flash" width="420" height="29"> 

    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 67, Column 12: end tag for "embed" omitted, but OMITTAG NO was specified
    			</object>

    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 66, Column 6: start tag was here
    					<embed wmode="transparent" src="http://www.al-fadjr.com/ar/themes/rtl/img/…
  • Error Line 589, Column 11: ID "banner_top" already defined
    	<div id="banner_top">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 53, Column 12: ID "banner_top" first defined here
    		<div id="banner_top">
  • Error Line 611, Column 85: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    …236725.html"> <a href="assatir/236725.html">  تفاصيل أكثر </a></a></span></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 620, Column 98: document type does not allow element "a" here; missing one of "object", "span", "bdo", "applet", "iframe", "tt", "i", "b", "u", "s", "strike", "big", "small", "font", "em", "strong", "dfn", "code", "q", "samp", "kbd", "var", "cite", "abbr", "acronym", "sub", "sup", "label", "ins", "del" start-tag
    ….html"> <a href="special/jadir/236736.html">  تفاصيل أكثر </a></a></span></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 873, Column 250: element "embed" undefined
    …=ShockwaveFlash" type="application/x-shockwave-flash" width="89" height="415"> 

    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 874, Column 11: end tag for "embed" omitted, but OMITTAG NO was specified
    		</object>

    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 873, Column 4: start tag was here
    			<embed src="http://www.al-fadjr.com/ar/themes/rtl/img/headline_logo.swf" qua…
  • Error Line 881, Column 10: ID "banner_top" already defined
    <div id="banner_top">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 53, Column 12: ID "banner_top" first defined here
    		<div id="banner_top">
  • Error Line 882, Column 155: required attribute "alt" not specified
    …w.al-fadjr.com/ar/files/banners/banniere_vente_paris_214193485.jpg"/></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 907, Column 118: there is no attribute "alt"
    …l-fadjr.com/ar/files.php?force&amp;file=/edition31012013_744012904.pdf" alt="">

    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 945, Column 62: cannot generate system identifier for general entity "showinfo"
    …://www.youtube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel=…

    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 945, Column 62: general entity "showinfo" not defined and no default entity
    …://www.youtube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel=…

    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 945, Column 70: reference not terminated by REFC delimiter
    …outube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel=0" name=…

    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 945, Column 70: reference to external entity in attribute value
    …outube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel=0" name=…

    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 945, Column 70: reference to entity "showinfo" for which no system identifier could be generated
    …outube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel=0" name=…

    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 945, Column 61: entity was defined here
    …p://www.youtube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel…
  • Error Line 945, Column 118: end tag for "param" omitted, but OMITTAG NO was specified
    …m/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel=0" name="movie">  

    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 945, Column 6: start tag was here
    					<param value="http://www.youtube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp…
  • Error Line 946, Column 46: end tag for "param" omitted, but OMITTAG NO was specified
    					<param value="transparent" name="wmode">  

    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 946, Column 6: start tag was here
    					<param value="transparent" name="wmode">  
  • Warning Line 947, Column 150: reference not terminated by REFC delimiter
    …w.youtube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel=0" /> 

    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 947, Column 150: reference to external entity in attribute value
    …w.youtube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel=0" /> 

    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 947, Column 150: reference to entity "showinfo" for which no system identifier could be generated
    …w.youtube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel=0" /> 

    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 945, Column 61: entity was defined here
    …p://www.youtube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel…
  • Error Line 947, Column 186: element "embed" undefined
    …w.youtube.com/v/Y0BFic4HH-g?fs=1&showinfo=0&amp;amp;hl=fr_FR&amp;amp;rel=0" /> 

    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 968, Column 39: document type does not allow element "div" here; assuming missing "li" start-tag
    								<div id="box_most_popular_tab">
  • Error Line 975, Column 12: end tag for "li" omitted, but OMITTAG NO was specified
    							</ul>

    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 968, Column 9: start tag was here
    								<div id="box_most_popular_tab">
  • Error Line 982, Column 13: ID "bloc_mostpopular" already defined
    			<div id="bloc_mostpopular">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 964, Column 13: ID "bloc_mostpopular" first defined here
    			<div id="bloc_mostpopular">
  • Error Line 983, Column 14: ID "bloc_mostpopular_content" already defined
    				<div id="bloc_mostpopular_content">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  • Info Line 965, Column 14: ID "bloc_mostpopular_content" first defined here
    				<div id="bloc_mostpopular_content">
  • Error Line 986, Column 41: document type does not allow element "div" here; assuming missing "li" start-tag
    								<div id="box_most_commented_tab">
  • Error Line 993, Column 12: end tag for "li" omitted, but OMITTAG NO was specified
    							</ul>

    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 986, Column 9: start tag was here
    								<div id="box_most_commented_tab">
  • Error Line 1964, Column 16: there is no attribute "height"
    	<table height="22px;" cellpadding="0" cellspacing="0">

    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.

Visitor Analysis

Daily Visitor
  • 8.750 visits