eppo.int Website Information
Daily Unique Visits: 24,566
Daily Page Views: 147,396
Income Per Day: $295
Estimated Value: $212,400
This website is located in France and is using following IP address 149.62.159.130. See the complete list of popular websites hosted in France.
eppo.int is registered under .INT top-level domain. Please check other sites in .INT zone.
Website eppo.int is using the following name servers:
- ns1.eppo.int
- ns2.eppo.int
and is probably hosted by NAITWAYS SAS. See the full list of other websites hosted by NAITWAYS SAS.
The highest website eppo.int position in Alexa rank database was 16855 and the lowest rank position was 999665. Current position of eppo.int in Alexa rank database is 58382.
Desktop speed score of eppo.int (87/100) is better than the results of 84.39% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of eppo.int (65/100) is better than the results of 13.11% of other sites and means that the page is not mobile-friendly.
Mobile speed score of eppo.int (74/100) is better than the results of 83.2% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
eppo.int 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.
eppo.int 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.
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object
domain: EPPO.INT
organisation: European and Mediterranean Plant Protection Organization
address: 21 boulevard Richard Lenoir
address: Paris 75011
address: France
contact: administrative
name: Anne-Sophie Roy
organisation: EPPO
address: 21 boulevard Richard Lenoir
address: Paris 75011
address: France
phone: +33145207794
e-mail: roy@eppo.int
contact: technical
name: Damien Griessinger
organisation: EPPO
address: 21 boulevard Richard Lenoir
address: Paris 75011
address: France
phone: +33145207794
e-mail: dgriessinger@eppo.int
nserver: NS1.EPPO.INT 149.62.152.20
nserver: NS2.EPPO.INT 149.62.158.200
created: 2011-05-12
changed: 2014-07-11
source: IANA
eppo.int server information
Servers Location
eppo.int desktop page speed rank
Last tested: 2018-03-22
eppo.int Desktop Speed Test Quick Summary
priority - 7Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 64.8KiB (64% reduction).
Compressing http://eppo.int/images/logoeppo.jpg could save 29.5KiB (82% reduction).
Compressing http://eppo.int/images/pratique.png could save 3.9KiB (15% reduction).
priority - 4Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
priority - 2Leverage 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://eppo.int/images/logoeppo.jpg (5 minutes)
http://eppo.int/images/logofp7.jpg (5 minutes)
http://eppo.int/js/eppo.js (5 minutes)
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 2.6KiB (61% reduction).
eppo.int Desktop Resource Breakdown
| Total Resources | 6 |
| Number of Hosts | 1 |
| Static Resources | 5 |
| JavaScript Resources | 1 |
| CSS Resources | 1 |
eppo.int mobile page speed rank
Last tested: 2018-08-29
eppo.int Mobile Speed Test Quick Summary
priority - 16Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
priority - 8Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 7Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 64.8KiB (64% reduction).
Compressing http://eppo.int/images/logoeppo.jpg could save 29.5KiB (82% reduction).
Compressing http://eppo.int/images/pratique.png could save 3.9KiB (15% reduction).
priority - 3Leverage 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://eppo.int/images/logoeppo.jpg (5 minutes)
http://eppo.int/images/logofp7.jpg (5 minutes)
http://eppo.int/js/eppo.js (5 minutes)
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 2.6KiB (61% reduction).
eppo.int Mobile Resource Breakdown
| Total Resources | 6 |
| Number of Hosts | 1 |
| Static Resources | 5 |
| JavaScript Resources | 1 |
| CSS Resources | 1 |
eppo.int mobile page usability
Last tested: 2018-08-29
eppo.int Mobile Usability Test Quick Summary
priority - 35Use 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.
User login and 1 others render only 5 pixels tall (13 CSS pixels).PRATIQUE Deliverables and 3 others render only 5 pixels tall (13 CSS pixels).Password: and 1 others render only 5 pixels tall (13 CSS pixels).Lost password ? and 1 others render only 5 pixels tall (13 CSS pixels).On this websit…s is provided. renders only 5 pixels tall (14 CSS pixels).Computer software CAPRA and 2 others render only 5 pixels tall (14 CSS pixels).On this page y…pport schemes. and 2 others render only 5 pixels tall (14 CSS pixels).Go to deliverables page and 2 others render only 5 pixels tall (14 CSS pixels).The PRATIQUE p…environments" renders only 5 pixels tall (14 CSS pixels).© 2018 EPPO -…n Sep 02, 2015 renders only 5 pixels tall (14 CSS pixels).Contact EPPO renders only 5 pixels tall (14 CSS pixels).priority - 10Size 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.
<a href="/index.php">Home</a> and 3 others are close to other tap targets.<label for="edit-openid-url">Login :</label> and 1 others are close to other tap targets.<input id="edit-openid-url" type="text" name="login" class="form-text"> and 1 others are close to other tap targets.<input id="edit-submit" type="submit" name="op" class="form-submit"> is close to 4 other tap targets.<a href="/user/password.php">Lost password ?</a> and 1 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.
eppo.int HTML validation
Errors
Obsolete doctype. Expected “<!DOCTYPE html>”.
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html..."
Bad value “Content-Script-Type” for attribute “http-equiv” on element “meta”.
"...f-8" /> <meta http-equiv="Content-Script-Type" content="text/javascript"/> <me..."
Bad value “Content-Style-Type” for attribute “http-equiv” on element “meta”.
"...ript"/> <meta http-equiv="Content-Style-Type" content="text/css"/> <sc..."
The “cellspacing” attribute on the “table” element is obsolete. Use CSS instead.
"...d> <body> <table id="header" border="0" cellspacing="0" cellpadding="0"> <tr..."
The “cellpadding” attribute on the “table” element is obsolete. Use CSS instead.
"...d> <body> <table id="header" border="0" cellspacing="0" cellpadding="0"> <tr..."
The “border” attribute on the “table” element is obsolete. Use CSS instead.
"...d> <body> <table id="header" border="0" cellspacing="0" cellpadding="0"> <tr..."
The “width” attribute on the “td” element is obsolete. Use CSS instead.
"...0"> <tr> <td id="logoeppo" width="1px"><a hre..." Line: 16 Column: 97 - 33
"...</h1></td> <td id="logofp7" width="1px"><a hre..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
"... href="/"><img src="/images/logoeppo.jpg" /></a></..." Line: 16 Column: 101 - 134
"...et="_new"><img src="/images/pratique.png" /></a></..." Line: 91 Column: 1 - 52
"...br /> <p> <img src="/images/logofp7.jpg" style="float:left" /><div s..."
Bad value “_new” for attribute “target” on element “a”: Reserved keyword “new” used.
"...dth="1px"><a href="https://secure.fera.defra.gov.uk/pratique/" target="_new"><img s..."
The “valign” attribute on the “td” element is obsolete. Use CSS instead.
"... </td> <td valign="top"> ..."
Element “style” not allowed as child of element “div” in this context. (Suppressing further errors from this subtree.)
"...> <style type="text/css"> #file..."
No “p” element in scope but a “p” end tag seen.
"...s"</div> </p> <..."
The “align” attribute on the “td” element is obsolete. Use CSS instead.
"...r"> <tr> <td align="left">© 2018..."
Warnings
The “language” attribute on the “script” element is obsolete. You can safely omit it.
".../css"/> <script language="javascript" type="text/javascript" src="/js/eppo.js"></scri..."
eppo.int similar domains
www.eppo.net
www.eppo.org
www.eppo.info
www.eppo.biz
www.eppo.us
www.eppo.mobi
www.ppo.int
www.eppo.int
www.wppo.int
www.ewppo.int
www.weppo.int
www.sppo.int
www.esppo.int
www.seppo.int
www.dppo.int
www.edppo.int
www.deppo.int
www.rppo.int
www.erppo.int
www.reppo.int
www.epo.int
www.eopo.int
www.epopo.int
www.eoppo.int
www.elpo.int
www.eplpo.int
www.elppo.int
www.epoo.int
www.eppoo.int
www.eplo.int
www.epplo.int
www.epp.int
www.eppi.int
www.eppoi.int
www.eppio.int
www.eppk.int
www.eppok.int
www.eppko.int
www.eppl.int
www.eppol.int
www.eppp.int
www.eppop.int
www.epppo.int
eppo.int 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.
eppo.int 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.