oiv.int website information.
oiv.int domain name is registered by .INT top-level domain registry. See the other sites registred in .INT domain zone.
Following name servers are specified for oiv.int domain:
- ns1.dynafi.fr
- ns2.dynafi.fr
and probably website oiv.int is hosted by GOOGLE - Google LLC, US web hosting company. Check the complete list of other most popular websites hosted by GOOGLE - Google LLC, US hosting company.
According to Alexa traffic rank the highest website oiv.int position was 20244 (in the world). The lowest Alexa rank position was 991449. Now website oiv.int ranked in Alexa database as number 38601 (in the world).
Website oiv.int Desktop speed measurement score (35/100) is better than the results of 11.34% of other sites shows that the page desktop performance can be improved.
oiv.int Mobile usability score (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of oiv.int (34/100) is better than the results of 12.98% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Weekly Rank Report
| Date | Rank | Change |
|---|---|---|
| Apr-29-2024 | 38,601 | 1,195 |
| Apr-28-2024 | 39,796 | -1,047 |
| Apr-27-2024 | 38,749 | 1,006 |
| Apr-26-2024 | 39,755 | -2,008 |
| Apr-25-2024 | 37,747 | 0 |
| Apr-24-2024 | 37,747 | 0 |
| Apr-23-2024 | 37,747 | 980 |
Advertisement
oiv.int Rank History
Alexa can identify the popularity of a website as well as its competitors. It is important for website owners and bloggers to know their Alexa ranking because it shows how many visitors have viewed their web page. It gives them a clear idea of how popular their website is on the internet and the ranking of their competitors.
oiv.int whois
WHOIS is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system, but is also used for a wider range of other information.
% IANA WHOIS server
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object
domain: OIV.INT
organisation: Organisation International de la Vigne et du Vin
address: 18, rue d'Aguesseau
address: PARIS 75008
address: FRANCE
contact: administrative
name: Federico CASTELLUCCI
address: 18, rue d'Aguesseau
address: PARIS 75008
address: FRANCE
phone: +33(0)1.44.94.80.80
fax-no: +33 (0)1.42.66.90.63
e-mail: dgeneral@oiv.int
contact: technical
name: Sylvain PASSEMAR
address: 18, rue d'Aguesseau
address: PARIS 75008
address: FRANCE
phone: +33(0)1.44.94.80.80
fax-no: +33 (0)1.42.66.90.63
e-mail: si@oiv.int
nserver: NS1.DYNAFI.FR 87.98.209.102
nserver: NS2.DYNAFI.FR 87.98.209.103
created: 2001-09-10
changed: 2019-04-22
source: IANA
oiv.int server information
oiv.int desktop page speed rank
Last tested: 2017-04-27
oiv.int Desktop Speed Test Quick Summary
priority - 190 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1.8MiB (78% reduction).
Compressing and resizing http://oiv.int/public/medias/5255/cp-oiv-avril-2017-524.jpg could save 121.7KiB (94% reduction).
Compressing and resizing http://oiv.int/public/medias/5237/export-vin-en-vrac-fr-524.png could save 121.3KiB (88% reduction).
Compressing and resizing http://oiv.int/public/medias/52/invitation-confere…seoiv-sep-2014-524.jpg could save 115.5KiB (94% reduction).
Compressing and resizing http://oiv.int/public/medias/5266/oiv-fivs-aurand-2017-524.jpg could save 106.6KiB (93% reduction).
Compressing http://oiv.int/public/medias/5255/cp-oiv-avril-2017-550.jpg could save 99.5KiB (73% reduction).
Compressing http://oiv.int/img/frontend/visuel-1.jpg could save 44.8KiB (61% reduction).
Compressing http://oiv.int/img/frontend/visuel-3.jpg could save 39KiB (65% reduction).
Compressing http://oiv.int/img/frontend/visuel-2.jpg could save 33.5KiB (63% reduction).
Compressing http://oiv.int/img/frontend/masque2.png could save 3.4KiB (20% reduction).
Compressing http://oiv.int/img/frontend/icon-eye.png could save 1.1KiB (70% reduction).
Compressing http://oiv.int/img/frontend/logo-small.png could save 1.1KiB (39% reduction).
Compressing http://oiv.int/img/frontend/icon-search.png could save 1KiB (48% reduction).
Compressing http://oiv.int/img/frontend/logo-footer.png could save 1,008B (48% reduction).
Compressing http://oiv.int/img/frontend/icon-btn-loupe-mobile.png could save 996B (70% reduction).
Compressing http://oiv.int/img/frontend/icon-tw-w-mobile.png could save 951B (71% reduction).
Compressing http://oiv.int/img/frontend/icon-tw.png could save 951B (75% reduction).
Compressing http://oiv.int/img/frontend/icon-loupe.png could save 942B (73% reduction).
Compressing http://oiv.int/img/frontend/search-white.png could save 930B (73% reduction).
Compressing http://oiv.int/img/frontend/icon-fb.png could save 920B (82% reduction).
Compressing http://oiv.int/img/frontend/icon-eye-button.png could save 912B (76% reduction).
Compressing http://oiv.int/img/frontend/icon-fb-w-mobile.png could save 910B (81% reduction).
Compressing http://oiv.int/img/frontend/logo-tw2.png could save 908B (62% reduction).
Compressing http://oiv.int/img/frontend/icon-eye-min.png could save 907B (82% reduction).
Compressing http://oiv.int/img/frontend/icon-arrow-bottom-red-min.png could save 893B (84% reduction).
Compressing http://oiv.int/img/frontend/logo-fb2.png could save 890B (72% reduction).
Compressing http://oiv.int/img/frontend/fleche-bottom-mobile.png could save 856B (75% reduction).
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
http://oiv.int/css/frontend/knacss-unminified.css
http://oiv.int/css/frontend/master.fixed.css
http://oiv.int/citrus-debug/css/citrus.min.css
priority - 3 Minify 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 27.5KiB (50% reduction).
Minifying http://oiv.int/css/frontend/knacss-unminified.css could save 3.6KiB (43% reduction) after compression.
priority - 2 Leverage 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://oiv.int/citrus-debug/js/debug.js (3 days)
http://oiv.int/js/frontend/lib/Chart.min.js (3 days)
http://oiv.int/js/frontend/lib/jquery.colorbox.min.js (3 days)
http://oiv.int/js/frontend/main.min.js (3 days)
http://oiv.int/js/lib/jQuery/chosen.jquery.min.js (3 days)
http://oiv.int/js/lib/jQuery/jquery-2.1.4.min.js (3 days)
http://oiv.int/js/lib/pdfjs/build/pdf.js (3 days)
priority - 0 Reduce server response time
In our test, your server responded in 0.22 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 0 Minify 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 555B (12% reduction).
oiv.int Desktop Resources
| Total Resources | 53 |
| Number of Hosts | 3 |
| Static Resources | 47 |
| JavaScript Resources | 9 |
| CSS Resources | 4 |
oiv.int Desktop Resource Breakdown
oiv.int mobile page speed rank
Last tested: 2017-04-27
oiv.int Mobile Speed Test Quick Summary
priority - 173 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 1.6MiB (71% reduction).
Compressing http://oiv.int/public/medias/5255/cp-oiv-avril-2017-550.jpg could save 99.5KiB (73% reduction).
Compressing http://oiv.int/public/medias/5255/cp-oiv-avril-2017-524.jpg could save 94.4KiB (73% reduction).
Compressing http://oiv.int/public/medias/52/invitation-confere…seoiv-sep-2014-524.jpg could save 90.5KiB (74% reduction).
Compressing http://oiv.int/public/medias/5266/oiv-fivs-aurand-2017-524.jpg could save 82.8KiB (72% reduction).
Compressing http://oiv.int/img/frontend/visuel-1.jpg could save 44.8KiB (61% reduction).
Compressing http://oiv.int/img/frontend/visuel-3.jpg could save 39KiB (65% reduction).
Compressing http://oiv.int/img/frontend/visuel-2.jpg could save 33.5KiB (63% reduction).
Compressing http://oiv.int/public/medias/5237/export-vin-en-vrac-fr-524.png could save 29KiB (22% reduction).
Compressing http://oiv.int/img/frontend/icon-eye.png could save 1.1KiB (70% reduction).
Compressing http://oiv.int/img/frontend/logo-small.png could save 1.1KiB (39% reduction).
Compressing http://oiv.int/img/frontend/icon-search.png could save 1KiB (48% reduction).
Compressing http://oiv.int/img/frontend/logo-footer.png could save 1,008B (48% reduction).
Compressing http://oiv.int/img/frontend/icon-btn-loupe-mobile.png could save 996B (70% reduction).
Compressing http://oiv.int/img/frontend/icon-tw-w-mobile.png could save 951B (71% reduction).
Compressing http://oiv.int/img/frontend/icon-tw.png could save 951B (75% reduction).
Compressing http://oiv.int/img/frontend/icon-loupe.png could save 942B (73% reduction).
Compressing http://oiv.int/img/frontend/search-white.png could save 930B (73% reduction).
Compressing http://oiv.int/img/frontend/icon-fb.png could save 920B (82% reduction).
Compressing http://oiv.int/img/frontend/icon-eye-button.png could save 912B (76% reduction).
Compressing http://oiv.int/img/frontend/icon-fb-w-mobile.png could save 910B (81% reduction).
Compressing http://oiv.int/img/frontend/logo-tw2.png could save 908B (62% reduction).
Compressing http://oiv.int/img/frontend/icon-eye-min.png could save 907B (82% reduction).
Compressing http://oiv.int/img/frontend/select-bottom.png could save 905B (89% reduction).
Compressing http://oiv.int/img/frontend/icon-arrow-bottom-red-min.png could save 893B (84% reduction).
Compressing http://oiv.int/img/frontend/logo-fb2.png could save 890B (72% reduction).
Compressing http://oiv.int/img/frontend/burger.png could save 856B (90% reduction).
Compressing http://oiv.int/img/frontend/fleche-bottom-mobile.png could save 856B (75% reduction).
priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.
None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
http://oiv.int/css/frontend/knacss-unminified.css
http://oiv.int/css/frontend/master.fixed.css
http://oiv.int/citrus-debug/css/citrus.min.css
priority - 4 Leverage 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://oiv.int/citrus-debug/js/debug.js (3 days)
http://oiv.int/js/frontend/lib/Chart.min.js (3 days)
http://oiv.int/js/frontend/lib/jquery.colorbox.min.js (3 days)
http://oiv.int/js/frontend/main.min.js (3 days)
http://oiv.int/js/lib/jQuery/chosen.jquery.min.js (3 days)
http://oiv.int/js/lib/jQuery/jquery-2.1.4.min.js (3 days)
http://oiv.int/js/lib/pdfjs/build/pdf.js (3 days)
priority - 3 Minify 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 27.5KiB (50% reduction).
Minifying http://oiv.int/css/frontend/knacss-unminified.css could save 3.6KiB (43% reduction) after compression.
priority - 0 Reduce server response time
In our test, your server responded in 0.22 seconds. There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.
priority - 0 Minify 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 531B (11% reduction).
oiv.int Mobile Resources
| Total Resources | 53 |
| Number of Hosts | 3 |
| Static Resources | 46 |
| JavaScript Resources | 9 |
| CSS Resources | 4 |
oiv.int Mobile Resource Breakdown
oiv.int mobile page usability
Last tested: 2017-04-27
oiv.int similar domains
www.oiv.net
www.oiv.org
www.oiv.info
www.oiv.biz
www.oiv.us
www.oiv.mobi
www.iv.int
www.oiv.int
www.iiv.int
www.oiiv.int
www.ioiv.int
www.kiv.int
www.okiv.int
www.koiv.int
www.liv.int
www.oliv.int
www.loiv.int
www.piv.int
www.opiv.int
www.poiv.int
www.ov.int
www.ouv.int
www.oiuv.int
www.ouiv.int
www.ojv.int
www.oijv.int
www.ojiv.int
www.okv.int
www.oikv.int
www.oov.int
www.oiov.int
www.ooiv.int
www.oi.int
www.oic.int
www.oivc.int
www.oicv.int
www.oif.int
www.oivf.int
www.oifv.int
www.oig.int
www.oivg.int
www.oigv.int
www.oib.int
www.oivb.int
www.oibv.int
oiv.int Ping
Ping is a networking utility tool to test if a particular host is reachable. It is a diagnostic that checks reachability of a host on an Internet Protocol (IP) network. In a computer network, a ping test is a way of sending messages from one host to another. Aside from checking if the host is connected to a network, ping also gives indicators of the reliability and general speed of the connection.
oiv.int TRACEROUTE
Traceroute is a network diagnostic tool used to track the pathway taken by a packet on an IP network from source to destination. Traceroute also records the time taken for each hop the packet makes during its route to the destination. Traceroute uses ICMP (Internet Control Message Protocol) echo packets with variable time to live values. The response time of each hop is calculated. To guarantee accuracy, each hop is queried multiple times (usually three times) to better measure the response of that particular hop.