philolog.fr Website Information

Daily Unique Visits: 883

Daily Page Views: 1,766

Income Per Day: $5

Estimated Value: $1,200

This website is located in France and is using following IP address 195.154.181.224. See the complete list of popular websites hosted in France.

philolog.fr is registered under .FR top-level domain. Please check other sites in .FR zone.

Website philolog.fr is using the following name servers:

dns10.ovh.net
ns10.ovh.net

and is probably hosted by o2switch SARL. See the full list of other websites hosted by o2switch SARL.

The highest website philolog.fr position in Alexa rank database was 15642 and the lowest rank position was 999964. Current position of philolog.fr in Alexa rank database is 812370.

Desktop speed score of philolog.fr (81/100) is better than the results of 71.91% of other sites and shows that the page is performing great on desktop computers.

Mobile usability score of philolog.fr (59/100) is better than the results of 2.69% of other sites and means that the page is not mobile-friendly.

Mobile speed score of philolog.fr (70/100) is better than the results of 76.43% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

philolog.fr Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.

philolog.fr whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.

%%
%% This is the AFNIC Whois server.
%%
%% complete date format: YYYY-MM-DDThh:mm:ssZ
%%
%% Rights restricted by copyright.
%% See https://www.afnic.fr/en/domain-names-and-support/everything-there-is-to-know-about-domain-names/find-a-domain-name-or-a-holder-using-whois/
%%
%%

domain: philolog.fr
status: ACTIVE
eppstatus: clientTransferProhibited
hold: NO
holder-c: PI16220-FRNIC
admin-c: O2798-FRNIC
tech-c: O2798-FRNIC
registrar: SCALEWAY
Expiry Date: 2025-04-03T22:10:22Z
created: 2007-10-04T07:23:37Z
last-update: 2024-03-27T15:41:30.111768Z
source: FRNIC

nserver: ns1.o2switch.net
nserver: ns2.o2switch.net
source: FRNIC

registrar: SCALEWAY
address: 8, rue de la ville l'Eveque
address: 75008 PARIS
country: FR
phone: +33.184130069
fax-no: +33.173502901
e-mail: frnic-admin@free.org
website: https://www.bookmyname.com
anonymous: No
registered: 1999-03-29T00:00:00Z
source: FRNIC

nic-hdl: O2798-FRNIC
type: ORGANIZATION
contact: O2SWITCH
address: Chemin des Pardiaux
address: 63000 CLERMONT FERRAND
country: FR
phone: +33.444446040
fax-no: +33.444446041
e-mail: dns-nospam@o2switch.fr
registrar: SCALEWAY
changed: 2022-09-18T10:04:59Z
anonymous: NO
obsoleted: NO
eppstatus: associated
eppstatus: active
eligstatus: not identified
reachstatus: not identified
source: FRNIC

nic-hdl: PI16220-FRNIC
type: ORGANIZATION
contact: Proxy Informatique
address: Proxy Informatique
address: 50 bis chemin du sous-bois
address: 73000 Barberaz
country: FR
phone: +33.631128272
e-mail: dns-nospam@o2switch.fr
registrar: SCALEWAY
changed: 2024-06-06T01:33:57.08945Z
anonymous: NO
obsoleted: NO
eppstatus: associated
eppstatus: active
eligstatus: not identified
reachstatus: ok
reachmedia: email
reachsource: REGISTRAR
reachdate: 2024-06-06T01:33:57.089451Z
source: FRNIC

>>> Last update of WHOIS database: 2024-11-08T20:14:03.604404Z

philolog.fr server information

Servers Location

philolog.fr desktop page speed rank

Last tested: 2019-07-06

Desktop Speed Medium

81/100

philolog.fr Desktop Speed Test Quick Summary

priority - 10Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 99.5KiB (67% reduction).

Compressing https://platform.twitter.com/widgets.js could save 65.6KiB (70% reduction).
Compressing https://platform.twitter.com/widgets/tweet_button.…58149bd3f6ecb8.en.html could save 20.3KiB (62% reduction).
Compressing https://platform.twitter.com/widgets/widget_iframe…A%2F%2Fwww.philolog.fr could save 9.2KiB (61% reduction).
Compressing https://platform.twitter.com/js/button.509719336ca39171c37a321231ccaf83.js could save 4.5KiB (66% reduction).

priority - 6Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

https://www.philolog.fr/wp-content/themes/mistylook/style.css
https://www.philolog.fr/wp-content/plugins/yet-ano…e/widget.css?ver=5.2.2
https://www.philolog.fr/wp-includes/css/dist/block…tyle.min.css?ver=5.2.2

priority - 4Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

https://assets.pinterest.com/js/pinit.js (5 minutes)
https://assets.pinterest.com/js/pinit_main.js?0.4805502842646092 (5 minutes)
https://syndication.twitter.com/settings (10 minutes)
https://widgets.pinterest.com/v1/urls/count.json?u…43868044.f.callback[0] (14.8 minutes)
https://connect.facebook.net/en_GB/all.js (20 minutes)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
https://platform.twitter.com/widgets.js (30 minutes)
https://platform.linkedin.com/in.js (60 minutes)

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1.6KiB (20% reduction).

Minifying https://www.google-analytics.com/urchin.js could save 975B (15% reduction) after compression.
Minifying https://connect.facebook.net/en_GB/all.js could save 672B (39% reduction) after compression.

priority - 0Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 1KiB (45% reduction).

Compressing https://www.philolog.fr/wp-content/themes/mistylook/img/underline1.jpg could save 463B (50% reduction).
Compressing https://www.philolog.fr/wp-content/themes/mistylook/img/icon_feed.gif could save 408B (39% reduction).
Compressing https://static.xx.fbcdn.net/rsrc.php/v3/y5/r/OqOE21UvWe3.png could save 201B (50% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 583B (22% reduction).

Minifying https://www.philolog.fr/wp-content/themes/mistylook/style.css could save 583B (22% reduction) after compression.

philolog.fr Desktop Resource Breakdown

Total Resources	42
Number of Hosts	17
Static Resources	30
JavaScript Resources	21
CSS Resources	4

philolog.fr mobile page speed rank

Last tested: 2019-01-20

Mobile Speed Medium

70/100

philolog.fr Mobile Speed Test Quick Summary

priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://ajax.googleapis.com/ajax/libs/mootools/1.2.…ompressed.js?ver=1.2.3
http://www.philolog.fr/wp-content/plugins/mootools…/lazyload.js?ver=1.2.3

Optimize CSS Delivery of the following:

http://www.philolog.fr/wp-content/themes/mistylook/style.css
http://www.philolog.fr/wp-content/plugins/yet-anot…e/widget.css?ver=4.2.2

priority - 7Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://assets.pinterest.com/js/pinit_main.js (3.2 minutes)
http://assets.pinterest.com/js/pinit.js (3.5 minutes)
https://widgets.pinterest.com/v1/urls/count.json?u…21390948.f.callback[0] (14.8 minutes)
http://cdn.syndication.twitter.com/widgets/tweetbu…k=__twttr.receiveCount (15 minutes)
http://connect.facebook.net/en_GB/all.js (20 minutes)
http://apis.google.com/js/plusone.js (30 minutes)
http://platform.twitter.com/widgets.js (30 minutes)
https://apis.google.com/js/api.js (30 minutes)
https://oauth.googleusercontent.com/gadgets/js/cor…om:shindig.sha1.js?c=2 (60 minutes)

priority - 3Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 33.7KiB (74% reduction).

Compressing http://assets.pinterest.com/js/pinit_main.js could save 33.7KiB (74% reduction).

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 4.7KiB (3% reduction).

Minifying https://platform.linkedin.com/js/secureAnonymousFr…0.2000-RC8.49447-1428& could save 2KiB (5% reduction) after compression.
Minifying https://fbstatic-a.akamaihd.net/rsrc.php/v2/yP/r/olh5WBad-Df.js could save 1.1KiB (2% reduction) after compression.
Minifying http://www.google-analytics.com/urchin.js could save 975B (15% reduction) after compression.
Minifying https://oauth.googleusercontent.com/gadgets/js/cor…om:shindig.sha1.js?c=2 could save 661B (3% reduction) after compression.

priority - 0Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 3.7KiB (4% reduction).

Losslessly compressing http://www.philolog.fr/wp-content/themes/mistylook/img/profile.jpg could save 2.4KiB (8% reduction).
Losslessly compressing http://www.philolog.fr/wp-content/themes/mistylook/img/misty.jpg could save 1.3KiB (2% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 718B (10% reduction).

Minifying http://www.philolog.fr/ could save 718B (10% reduction) after compression.

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 583B (22% reduction).

Minifying http://www.philolog.fr/wp-content/themes/mistylook/style.css could save 583B (22% reduction) after compression.

philolog.fr Mobile Resource Breakdown

Total Resources	49
Number of Hosts	24
Static Resources	30
JavaScript Resources	23
CSS Resources	4

philolog.fr mobile page usability

Last tested: 2019-01-20

Mobile Usability Bad

59/100

philolog.fr Mobile Usability Test Quick Summary

priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Introduction renders only 3 pixels tall (12 CSS pixels).

Cours de Philosophie and 4 others render only 3 pixels tall (12 CSS pixels).

PhiloLog renders only 7 pixels tall (22 CSS pixels).

Cours de philosophie renders only 3 pixels tall (12 CSS pixels).

Flux pour and 1 others render only 3 pixels tall (12 CSS pixels).

Commentaires and 1 others render only 3 pixels tall (12 CSS pixels).

Introduction renders only 5 pixels tall (18 CSS pixels).

26 sept 2007 par renders only 3 pixels tall (11 CSS pixels).

La Mission laï…G. Guy-Grand. and 82 others render only 3 pixels tall (11 CSS pixels).

Car c’est un b…e universelle. and 4 others render only 4 pixels tall (14 CSS pixels).

Comment se rep…dans ce blog » renders only 6 pixels tall (21 CSS pixels).

Partager : renders only 4 pixels tall (13 CSS pixels).

Share and 1 others render only 3 pixels tall (11 CSS pixels).

693 renders only 3 pixels tall (11 CSS pixels).

Tweet renders only 3 pixels tall (11 CSS pixels).

31 renders only 3 pixels tall (11 CSS pixels).

24 renders only 3 pixels tall (12 CSS pixels).

Share renders only 3 pixels tall (11 CSS pixels).

Les commentaires sont fermés renders only 3 pixels tall (11 CSS pixels).

Entrées complémentaires and 9 others render only 5 pixels tall (16 CSS pixels).

Il n’y a pas d…rée similaire. renders only 3 pixels tall (11 CSS pixels).

Professeur de philosophie and 2 others render only 3 pixels tall (11 CSS pixels).

dans and 9 others render only 3 pixels tall (11 CSS pixels).
Wojciechowski Rosemonde and 4 others render only 3 pixels tall (11 CSS pixels).
© 2015 Tous droits réservés. renders only 3 pixels tall (12 CSS pixels).
Propulsé par and 2 others render only 3 pixels tall (11 CSS pixels).

priority - 24Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

The tap target <a href="http://www.philolog.fr/index/">Index</a> is close to 1 other tap targets.

The tap target <input id="s" type="text" name="s" class="textbox"> is close to 1 other tap targets.

The tap target <input id="searchsubmit" type="submit"> is close to 2 other tap targets.

The tap target <a href="http://www.philolog.fr/feed/">Articles</a> and 1 others are close to other tap targets.

The tap target <div class="pluginButton p…onDisconnected">Like</div> is close to 3 other tap targets.

The tap target <button type="submit"></button> and 2 others are close to other tap targets.

The tap target <div class="pluginButton pluginButtonSmall">Share</div> is close to 2 other tap targets.

The tap target <a id="b" href="https://twitte…philolog.fr%2F" class="btn">Tweet</a> is close to 1 other tap targets.

The tap target <a id="count" href="https://twitte…philolog.fr%2F">31</a> is close to 2 other tap targets.

The tap target <div id="plusone" class="Jg">24</div> is close to 1 other tap targets.

The tap target <a href="http://www.phi…-dans-ce-blog/">Comment se rep…dans ce blog ?</a> and 113 others are close to other tap targets.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

philolog.fr HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 121
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."

The “profile” attribute on the “head” element is obsolete. To declare which “meta” terms are used in the document, instead register the names as meta extensions. To trigger specific UA behaviors, use a “link” element instead.

Line: 4 Column: 44 - 39
"...99/xhtml"> <head profile="http://gmpg.org/xfn/11"> <meta..."

Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.

Line: 33 Column: 1 - 73
"...='all' /> <link rel='https://api.w.org/' href='https://www.philolog.fr/wp-json/' /> <link..."

The “cellpadding” attribute on the “table” element is obsolete. Use CSS instead.

Line: 151 Column: 6 - 98
"...</p> <table border="0" cellpadding="0" cellspacing="8" style="margin: 0 auto" id="social_buttons"> ..."

The “cellspacing” attribute on the “table” element is obsolete. Use CSS instead.

Line: 151 Column: 6 - 98
"...</p> <table border="0" cellpadding="0" cellspacing="8" style="margin: 0 auto" id="social_buttons"> ..."

The “border” attribute on the “table” element is obsolete. Use CSS instead.

Line: 151 Column: 6 - 98
"...</p> <table border="0" cellpadding="0" cellspacing="8" style="margin: 0 auto" id="social_buttons"> ..."

Bad value “http://www.linkedin.com/shareArticle?mini=true&url=http%3A%2F%2Fwww.philolog.fr%2F&title= - PhiloLog” for attribute “href” on element “a”: Illegal character in query: space is not allowed.

Line: 175 Column: 10 - 248
"... <a href="http://www.linkedin.com/shareArticle?mini=true&url=http%3A%2F%2Fwww.philolog.fr%2F&title= - PhiloLog" class="socialite linkedin-share" data-url="http://www.philolog.fr/" data-counter="right" rel="nofollow" target="_blank"> ..."

Warnings

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

Line: 208 Column: 1 - 105
"...iberte/"> <img border="0" alt="10 leçons sur la lierté" src="https://www.philolog.fr/documents/LaLiberte.174.jpg" > </a> ..."

This document appears to be written in French. Consider adding “lang="fr"” (or variant) to the “html” start tag.

Line: 2 Column: 122 - 43
"...onal.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <hea..."

philolog.fr similar domains

Similar domains:

www.philolog.com
www.philolog.net
www.philolog.org
www.philolog.info
www.philolog.biz
www.philolog.us
www.philolog.mobi
www.hilolog.fr
www.philolog.fr
www.ohilolog.fr
www.pohilolog.fr
www.ophilolog.fr
www.lhilolog.fr
www.plhilolog.fr
www.lphilolog.fr
www.pilolog.fr
www.pbilolog.fr
www.phbilolog.fr
www.pbhilolog.fr
www.pgilolog.fr
www.phgilolog.fr
www.pghilolog.fr
www.pyilolog.fr
www.phyilolog.fr
www.pyhilolog.fr
www.puilolog.fr
www.phuilolog.fr
www.puhilolog.fr
www.pjilolog.fr
www.phjilolog.fr
www.pjhilolog.fr
www.pnilolog.fr
www.phnilolog.fr
www.pnhilolog.fr
www.phlolog.fr
www.phulolog.fr
www.phiulolog.fr
www.phjlolog.fr
www.phijlolog.fr
www.phklolog.fr
www.phiklolog.fr
www.phkilolog.fr
www.phololog.fr
www.phiololog.fr
www.phoilolog.fr
www.phiolog.fr
www.phipolog.fr
www.philpolog.fr
www.phiplolog.fr
www.phioolog.fr
www.philoolog.fr
www.phikolog.fr
www.philkolog.fr
www.phillog.fr
www.phililog.fr
www.philoilog.fr
www.philiolog.fr
www.philklog.fr
www.philoklog.fr
www.philllog.fr
www.philollog.fr
www.phillolog.fr
www.philplog.fr
www.philoplog.fr
www.philoog.fr
www.philopog.fr
www.philolpog.fr
www.philooog.fr
www.philoloog.fr
www.philokog.fr
www.philolkog.fr
www.philolg.fr
www.philolig.fr
www.philoloig.fr
www.philoliog.fr
www.philolkg.fr
www.philolokg.fr
www.philollg.fr
www.philololg.fr
www.philolpg.fr
www.philolopg.fr
www.philolo.fr
www.philolof.fr
www.philologf.fr
www.philolofg.fr
www.philolov.fr
www.philologv.fr
www.philolovg.fr
www.philolot.fr
www.philologt.fr
www.philolotg.fr
www.philolob.fr
www.philologb.fr
www.philolobg.fr
www.philoloy.fr
www.philology.fr
www.philoloyg.fr
www.philoloh.fr
www.philologh.fr
www.philolohg.fr

philolog.fr Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.

philolog.fr TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.

PHILOLOG.FR - PhiloLog

philolog.fr Website Information

Advertisement

philolog.fr Alexa Rank

philolog.fr whois

philolog.fr server information

Servers Location

philolog.fr desktop page speed rank

philolog.fr Desktop Speed Test Quick Summary

priority - 10Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 99.5KiB (67% reduction).

priority - 6Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

priority - 4Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 0Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 1.6KiB (20% reduction).

priority - 0Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 1KiB (45% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 583B (22% reduction).

philolog.fr Desktop Resource Breakdown

philolog.fr mobile page speed rank

philolog.fr Mobile Speed Test Quick Summary

priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 2 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

Optimize CSS Delivery of the following:

priority - 7Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

priority - 3Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 33.7KiB (74% reduction).

priority - 1Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 4.7KiB (3% reduction).

priority - 0Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 3.7KiB (4% reduction).

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 718B (10% reduction).

priority - 0Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 583B (22% reduction).

philolog.fr Mobile Resource Breakdown

philolog.fr mobile page usability

philolog.fr Mobile Usability Test Quick Summary

priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

priority - 24Size tap targets appropriately

Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.

The following tap targets are close to other nearby tap targets and may need additional spacing around them.

priority - 10Configure the viewport

Your page does not have a viewport specified. This causes mobile devices to render your page as it would appear on a desktop browser, scaling it down to fit on a mobile screen. Configure a viewport to allow your page to render properly on all devices.

philolog.fr HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

The “profile” attribute on the “head” element is obsolete. To declare which “meta” terms are used in the document, instead register the names as meta extensions. To trigger specific UA behaviors, use a “link” element instead.

Bad value “https://api.w.org/” for attribute “rel” on element “link”: The string “https://api.w.org/” is not a registered keyword.

The “cellpadding” attribute on the “table” element is obsolete. Use CSS instead.

The “cellspacing” attribute on the “table” element is obsolete. Use CSS instead.

The “border” attribute on the “table” element is obsolete. Use CSS instead.

Bad value “http://www.linkedin.com/shareArticle?mini=true&url=http%3A%2F%2Fwww.philolog.fr%2F&title= - PhiloLog” for attribute “href” on element “a”: Illegal character in query: space is not allowed.

Warnings

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

This document appears to be written in French. Consider adding “lang="fr"” (or variant) to the “html” start tag.

philolog.fr similar domains

philolog.fr Ping

philolog.fr TRACEROUTE