produits-casino.fr

Tout savoir sur l'actualité des produits à marque Casino. Des jeux, des conseils nutrition, mais aussi forme et bien-être.

Content Analysis

produits-casino.fr has Alexa Rank 0 and Google Page Rank is 5

Title

Page Size

44.6 KB

Meta Keywords

Casino, produit casino, Bien pour vous, Casino Délice, Ysiance, offres promotionnelles casino, nouveautés produits casino, casino, geant casino, magasin casino, supermarché casino, smiles, carte casino

Images

  • 3 GIF, 15 JPG, 36 PNG

Heading

  • H1: 1, H2: 0, H3: 3, H4: 0, H5: 0, H6: 0

Meta Description

Tout savoir sur l'actualité des produits à marque Casino. Des jeux, des conseils nutrition, mais aussi forme et bien-être.

Visitor Analysis

Daily Visitor

  • 0 visits

Traffic Analysis

Daily Ranks

Rank Trend

Visitor Trend

Bounce Trend

Http Header Analysis

Hyper Text Transfer Protocol (HTTP) header show data header response from produits-casino.fr .

HTML Analysis

  • date: Thu, 03 Apr 2014 21:13:49 GMT
  • server: Apache
  • x-powered-by: PHP/5.3.26
  • vary: Cookie,Accept-Encoding
  • composed-by: SPIP @ www.spip.net
  • x-spip-cache: 86400
  • last-modified: Thu, 03 Apr 2014 10:42:38 GMT
  • content-type: text/html; charset=utf-8
  • x-google-cache-control: remote-fetch
  • via: HTTP/1.1 GWA

Site Technical Analysis

Web server

  • Apache

Javascript Library

  • jquery

Ip Address

Language used

  • HTML
  • CSS
  • JAVASCRIPT

Domain Age

Check speed

  • Check Speed

Site same Ip 213.139.127.49(View more...)

Whois Analysis

Whois Ip

(View more...) % This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
% To receive output for a database update, use the "-B" flag.

% Information related to '213.139.112.0 - 213.139.127.255'

% Abuse contact for '213.139.112.0 - 213.139.127.255' is 'ripe@mgn.net'

inetnum: 213.139.112.0 - 213.139.127.255
netname: FR-PROSODIE-ZH-GDR
descr: Prosodie
country: FR
admin-c: MM7262-RIPE
tech-c: MM7262-RIPE
status: ASSIGNED PA
mnt-by: MGN-MNT
source: RIPE # Filtered
remarks:



person: Michel Moriniaux
address: 78000 Versailles
address: France
phone: +33 (0)1 34 49 10 73
nic-hdl: MM7262-RIPE
mnt-by: MM7262-MNT
source: RIPE # Filtered

% Information related to '213.139.96.0/19AS8784'

route: 213.139.96.0/19
descr: Prosodie
origin: AS8784
mnt-by: MGN-MNT
source: RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.72 (DBC-WHOIS4)

HTML Analysis

HTML validation

  • 82 Errors
  • 37 Warnings

Ratio Text/Html

  • 0.6926311179240119

Message Error

(View more...)
  1. Error Line 109, Column 16: there is no attribute "property"
    <meta property="og:site_name" content="Produits-Casino.fr "/>

    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.

  2. Error Line 116, Column 7: end tag for "head" which is not finished
    </head>

    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.

  3. Error Line 119, Column 8: required attribute "type" not specified
    <script>(function(d, s, id) {

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

  4. Warning Line 123, Column 57: cannot generate system identifier for general entity "appId"
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=188144927904528";

    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.

  5. Error Line 123, Column 57: general entity "appId" not defined and no default entity
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=188144927904528";

    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.

  6. Warning Line 123, Column 62: reference not terminated by REFC delimiter
      js.src = "//connect.facebook.net/fr_FR/all.js#xfbml=1&appId=188144927904528";

    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.

This data was last updated from 03-04-2014  (update data).