fr.cr Website Information
Daily Unique Visits: 9,733
Daily Page Views: 48,665
Income Per Day: $122
Estimated Value: $73,200
fr.cr is registered under .CR top-level domain. Please check other sites in .CR zone.
No name server records were found.
and is probably hosted by OVH SAS. See the full list of other websites hosted by OVH SAS.
The highest website fr.cr position in Alexa rank database was 21310 and the lowest rank position was 992104. Current position of fr.cr in Alexa rank database is 139989.
Desktop speed score of fr.cr (83/100) is better than the results of 76.15% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of fr.cr (61/100) is better than the results of 5.47% of other sites and means that the page is not mobile-friendly.
Mobile speed score of fr.cr (79/100) is better than the results of 87.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
fr.cr 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.
fr.cr 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.
% *The information provided by WHOIS is supplied by NIC Costa Rica's database of registered domains. This option has the sole intention of showing information about the domains registered under the CR Top level domain for name assignation purposes. It is absolutely forbidden to collect, store, use or transmit any information displayed by WHOIS for commercial and advertising purposes without prior notice to the persons involved and to NIC Costa Rica. NIC Costa Rica does not guarantee the accuracy of the information displayed by this option. Since it is provided by the contacts, the accuracy is their responsibility. The National Academy of Sciences is not liable for the use of the information here revealed. The National Academy of Sciences undertakes to comply with the terms set forth in the Data Protection laws of the Republic of Costa Rica and therefore protects the data collected from NIC Costa Rica users, regardless of whether they are Costa Rican citizens or not. If you are a contact of a .cr domain name and wish to use the WHOIS Privacy service, select this option in "Edit account" once your login with your username and password, or access the following link:
% https://www.nic.cr/iniciar-sesion/?next=/my-account/
%
%
% *La información mostrada a través de la opción WHOIS es provista de la base de datos de los dominios registrados en NIC Costa Rica. Esta opción tiene el propósito exclusivo de mostrar información sobre los dominios registrados bajo el Dominio Superior .CR para los fines de la delegación de los nombs. Queda absolutamente prohibido compilar, almacenar, usar y/o trasmitir la información mostrada mediante la opción WHOIS para fines comerciales y publicitarios, sin la previa autorización de los afectados y de NIC Costa Rica. NIC Costa Rica no garantiza la exactitud de la información desplegada mediante esta opción, ya que ésta proviene de los contactos, y su veracidad es responsabilidad de estos últimos. La Academia Nacional de Ciencias no se responsabiliza por el uso que se le dé a la información aquí mostrada. La Academia Nacional de Ciencias se compromete a cumplir con los términos establecidos en las leyes de Protección de Datos de la República de Costa Rica y por lo tanto protege los datos recolectados de todos los usuarios de NIC Costa Rica que sean ciudadanos o no de la República de Costa Rica. Si un contacto de un dominio .cr desea hacer uso del servicio de Privacidad WHOIS puede escoger esta opción en "Editar cuenta" con su usuario y clave, o ingresar al siguiente link:
% https://www.nic.cr/iniciar-sesion/?next=/mi-cuenta/
%
% Whoisd Server Version: 3.12.2
% Timestamp: Mon Dec 11 02:35:08 2023
domain: fr.cr
registrant: CN_1262
admin-c: CN_1262
nsset: NS_FR_CR
registrar: NIC-REG1
registered: 24.04.2008 06:07:59
changed: 24.04.2021 03:38:37
expire: 01.05.2024
contact: CN_1262
org: Azote
name: Guilbault Jírímy
address: 22 rue de la guimellerie
address: Beaupreau
address: 1000
address: Otro
address: FR
phone: +1.123456789
e-mail: theboutik@free.fr
registrar: NIC-REG1
created: 03.06.2011 23:21:31
changed: 09.04.2019 04:06:58
nsset: NS_FR_CR
nserver: ns2.azote.org
nserver: ns1.azote.org
tech-c: CN_1262
registrar: NIC-REG1
created: 03.06.2011 12:49:31
% https://www.nic.cr/iniciar-sesion/?next=/my-account/
%
%
% *La información mostrada a través de la opción WHOIS es provista de la base de datos de los dominios registrados en NIC Costa Rica. Esta opción tiene el propósito exclusivo de mostrar información sobre los dominios registrados bajo el Dominio Superior .CR para los fines de la delegación de los nombs. Queda absolutamente prohibido compilar, almacenar, usar y/o trasmitir la información mostrada mediante la opción WHOIS para fines comerciales y publicitarios, sin la previa autorización de los afectados y de NIC Costa Rica. NIC Costa Rica no garantiza la exactitud de la información desplegada mediante esta opción, ya que ésta proviene de los contactos, y su veracidad es responsabilidad de estos últimos. La Academia Nacional de Ciencias no se responsabiliza por el uso que se le dé a la información aquí mostrada. La Academia Nacional de Ciencias se compromete a cumplir con los términos establecidos en las leyes de Protección de Datos de la República de Costa Rica y por lo tanto protege los datos recolectados de todos los usuarios de NIC Costa Rica que sean ciudadanos o no de la República de Costa Rica. Si un contacto de un dominio .cr desea hacer uso del servicio de Privacidad WHOIS puede escoger esta opción en "Editar cuenta" con su usuario y clave, o ingresar al siguiente link:
% https://www.nic.cr/iniciar-sesion/?next=/mi-cuenta/
%
% Whoisd Server Version: 3.12.2
% Timestamp: Mon Dec 11 02:35:08 2023
domain: fr.cr
registrant: CN_1262
admin-c: CN_1262
nsset: NS_FR_CR
registrar: NIC-REG1
registered: 24.04.2008 06:07:59
changed: 24.04.2021 03:38:37
expire: 01.05.2024
contact: CN_1262
org: Azote
name: Guilbault Jírímy
address: 22 rue de la guimellerie
address: Beaupreau
address: 1000
address: Otro
address: FR
phone: +1.123456789
e-mail: theboutik@free.fr
registrar: NIC-REG1
created: 03.06.2011 23:21:31
changed: 09.04.2019 04:06:58
nsset: NS_FR_CR
nserver: ns2.azote.org
nserver: ns1.azote.org
tech-c: CN_1262
registrar: NIC-REG1
created: 03.06.2011 12:49:31
fr.cr server information
Servers Location
fr.cr desktop page speed rank
Last tested: 2017-12-03
Desktop Speed
Medium
83/100
fr.cr Desktop Speed Test Quick Summary
priority - 14Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 131.7KiB (79% reduction).
Compressing http://www.azote.org/files/images/header.jpg could save 127.1KiB (82% reduction).
Compressing http://www.azote.org/files/images/footer.jpg could save 1.9KiB (50% reduction).
Compressing http://www.azote.org/files/images/bg.jpg could save 1.8KiB (37% reduction).
Compressing http://www.azote.org/files/images/fondbtn.jpg could save 946B (38% reduction).
Compressing http://www.azote.org/files/images/footer.jpg could save 1.9KiB (50% reduction).
Compressing http://www.azote.org/files/images/bg.jpg could save 1.8KiB (37% reduction).
Compressing http://www.azote.org/files/images/fondbtn.jpg could save 946B (38% reduction).
priority - 2Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
http://www.azote.org/files/style.css
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://www.azote.org/facebook.png (expiration not specified)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
http://www.google-analytics.com/ga.js (2 hours)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
http://www.google-analytics.com/ga.js (2 hours)
priority - 1Enable 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 6.5KiB (78% reduction).
Compressing http://www.azote.org/files/style.css could save 6.5KiB (78% 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 1KiB (13% reduction).
Minifying http://www.azote.org/files/style.css could save 1KiB (13% reduction).
fr.cr Desktop Resource Breakdown
| Total Resources | 26 |
| Number of Hosts | 6 |
| Static Resources | 21 |
| JavaScript Resources | 8 |
| CSS Resources | 1 |
fr.cr mobile page speed rank
Last tested: 2017-12-03
Mobile Speed
Medium
79/100
fr.cr Mobile Speed Test Quick Summary
priority - 14Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 131.7KiB (79% reduction).
Compressing http://www.azote.org/files/images/header.jpg could save 127.1KiB (82% reduction).
Compressing http://www.azote.org/files/images/footer.jpg could save 1.9KiB (50% reduction).
Compressing http://www.azote.org/files/images/bg.jpg could save 1.8KiB (37% reduction).
Compressing http://www.azote.org/files/images/fondbtn.jpg could save 946B (38% reduction).
Compressing http://www.azote.org/files/images/footer.jpg could save 1.9KiB (50% reduction).
Compressing http://www.azote.org/files/images/bg.jpg could save 1.8KiB (37% reduction).
Compressing http://www.azote.org/files/images/fondbtn.jpg could save 946B (38% reduction).
priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
http://www.azote.org/files/style.css
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://www.azote.org/facebook.png (expiration not specified)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
http://www.google-analytics.com/ga.js (2 hours)
https://apis.google.com/js/plusone.js (30 minutes)
https://apis.google.com/js/rpc:shindig_random.js?onload=init (30 minutes)
http://www.google-analytics.com/ga.js (2 hours)
priority - 1Enable 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 6.5KiB (78% reduction).
Compressing http://www.azote.org/files/style.css could save 6.5KiB (78% reduction).
priority - 0Reduce server response time
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 1KiB (13% reduction).
Minifying http://www.azote.org/files/style.css could save 1KiB (13% reduction).
fr.cr Mobile Resource Breakdown
| Total Resources | 26 |
| Number of Hosts | 6 |
| Static Resources | 21 |
| JavaScript Resources | 8 |
| CSS Resources | 1 |
fr.cr mobile page usability
Last tested: 2017-12-03
Mobile Usability
Bad
61/100
fr.cr 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.
Enregistrer un domaine and 4 others render only 4 pixels tall (11 CSS pixels).Domaine gratuit and 2 others render only 5 pixels tall (13 CSS pixels).Hebergratuit.com and 9 others render only 4 pixels tall (11 CSS pixels).Abuse Report renders only 4 pixels tall (11 CSS pixels).353253 domaines and 4 others render only 4 pixels tall (11 CSS pixels).dont : and 3 others render only 4 pixels tall (11 CSS pixels).... suite renders only 4 pixels tall (11 CSS pixels).Dernières news and 2 others render only 5 pixels tall (13 CSS pixels).la disponibilité d'un domaine and 2 others render only 5 pixels tall (13 CSS pixels).Bénéficiez Gra…ous la forme : and 6 others render only 4 pixels tall (11 CSS pixels).Votre adresse…ww.site.fr.nf/ and 7 others render only 4 pixels tall (11 CSS pixels).( Nouveau ) renders only 4 pixels tall (11 CSS pixels).N'hésitez pas,…c'est GRATUIT renders only 4 pixels tall (11 CSS pixels).Le nom de doma…associations! and 4 others render only 5 pixels tall (12 CSS pixels).testez le ! and 1 others render only 5 pixels tall (12 CSS pixels).( 05/07/2017 à 15:17:09 ) and 4 others render only 4 pixels tall (10 CSS pixels).Premiers arriv…miers servis ! and 2 others render only 5 pixels tall (12 CSS pixels).... toutes les news renders only 5 pixels tall (12 CSS pixels).( 10 news ) renders only 4 pixels tall (10 CSS pixels).1. Entrer un nom and 1 others render only 4 pixels tall (11 CSS pixels).(exemple: compagnie) renders only 3 pixels tall (9 CSS pixels)..asso.st renders only 5 pixels tall (12 CSS pixels)..infos.st and 2 others render only 5 pixels tall (12 CSS pixels).3. Vérifier renders only 4 pixels tall (11 CSS pixels).priority - 18Size 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="enregistrer-no…e-domaine.html">Enregistrer un domaine</a> and 3 others are close to other tap targets.The tap target
<a href="index.html">Accueil</a> and 9 others are close to other tap targets.The tap target
<a href="report.html">Abuse Report</a> is close to 2 other tap targets.The tap target
<a href="https://www.fa…81738478552606"></a> is close to 2 other tap targets.The tap target
<a href="//plus.google.…w.azote.org%2F"></a> is close to 2 other tap targets.The tap target
<a href="news-30.html">Nous lancons u…e, testez le !</a> and 4 others are close to other tap targets.The tap target
<a href="news-30.html">Nous lancons u…e, testez le !</a> and 1 others are close to other tap targets.The tap target
<a href="news-27.html">NOUVEAU : Les domaines CNAME</a> and 2 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.
fr.cr HTML validation
Errors
Malformed byte sequence: “e9”.
Line: 5 Column: - 71
"......" Line: 5 Column: - 79
"......" Line: 63 Column: - 73
"......" Line: 65 Column: - 72
"......" Line: 65 Column: - 90
"......" Line: 67 Column: - 70
"......" Line: 67 Column: - 87
"......" Line: 69 Column: - 67
"......" Line: 102 Column: - 56
"......" Line: 102 Column: - 70
"......" Line: 116 Column: - 90
"......" Line: 121 Column: - 13
"......" Line: 121 Column: - 43
"......" Line: 139 Column: - 33
"......"
"......" Line: 5 Column: - 79
"......" Line: 63 Column: - 73
"......" Line: 65 Column: - 72
"......" Line: 65 Column: - 90
"......" Line: 67 Column: - 70
"......" Line: 67 Column: - 87
"......" Line: 69 Column: - 67
"......" Line: 102 Column: - 56
"......" Line: 102 Column: - 70
"......" Line: 116 Column: - 90
"......" Line: 121 Column: - 13
"......" Line: 121 Column: - 43
"......" Line: 139 Column: - 33
"......"
Malformed byte sequence: “a9”.
Line: 10 Column: - 33
"......"
"......"
Obsolete doctype. Expected “<!DOCTYPE html>”.
Line: 1 Column: 1 - 109
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html..."
"...<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html..."
Internal encoding declaration “iso-8859-1” disagrees with the actual encoding of the document (“utf-8”).
Line: 12 Column: 1 - 74
"... days" /> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <meta..."
"... days" /> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <meta..."
Bad value “text/html; charset=iso-8859-1” for attribute “content” on element “meta”: “iso-8859-1” is not a preferred encoding name. The preferred label for this encoding is “windows-1252”.
Line: 12 Column: 1 - 74
"... days" /> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <meta..."
"... days" /> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <meta..."
Malformed byte sequence: “e0”.
Line: 29 Column: - 51
"......" Line: 108 Column: - 146
"......" Line: 110 Column: - 109
"......" Line: 112 Column: - 88
"......" Line: 112 Column: - 145
"......" Line: 114 Column: - 166
"......" Line: 116 Column: - 156
"......"
"......" Line: 108 Column: - 146
"......" Line: 110 Column: - 109
"......" Line: 112 Column: - 88
"......" Line: 112 Column: - 145
"......" Line: 114 Column: - 166
"......" Line: 116 Column: - 156
"......"
Malformed byte sequence: “e8”.
Line: 67 Column: - 125
"......"
"......"
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
Line: 79 Column: 87 - 119
"...="_blank"><img border=0 src="facebook.png"></a> ..."
"...="_blank"><img border=0 src="facebook.png"></a> ..."
The text content of element “script” was not in the required format: Expected space, tab, newline, or slash but found “{” instead.
Line: 80 Column: 94 - 102
"...ang: 'fr'}</script> ..."
"...ang: 'fr'}</script> ..."
Element “g:plusone” not allowed as child of element “span” in this context. (Suppressing further errors from this subtree.)
Line: 81 Column: 5 - 72
"...t> <g:plusone size="medium" count="false" href="http://www.azote.org/"></g:pl..."
"...t> <g:plusone size="medium" count="false" href="http://www.azote.org/"></g:pl..."
Warnings
The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.
Line: 79 Column: 87 - 119
"...="_blank"><img border=0 src="facebook.png"></a> ..."
"...="_blank"><img border=0 src="facebook.png"></a> ..."
Element name “g:plusone” cannot be represented as XML 1.0.
Line: 81 Column: 5 - 72
"...t> <g:plusone size="medium" count="false" href="http://www.azote.org/"></g:pl..."
"...t> <g:plusone size="medium" count="false" href="http://www.azote.org/"></g:pl..."
fr.cr similar domains
Similar domains:
www.fr.com
www.fr.net
www.fr.org
www.fr.info
www.fr.biz
www.fr.us
www.fr.mobi
www.r.cr
www.fr.cr
www.cr.cr
www.fcr.cr
www.cfr.cr
www.dr.cr
www.fdr.cr
www.dfr.cr
www.rr.cr
www.frr.cr
www.rfr.cr
www.tr.cr
www.ftr.cr
www.tfr.cr
www.gr.cr
www.fgr.cr
www.gfr.cr
www.vr.cr
www.fvr.cr
www.vfr.cr
www.f.cr
www.fe.cr
www.fre.cr
www.fer.cr
www.fd.cr
www.frd.cr
www.ff.cr
www.frf.cr
www.ffr.cr
www.ft.cr
www.frt.cr
www.fr.net
www.fr.org
www.fr.info
www.fr.biz
www.fr.us
www.fr.mobi
www.r.cr
www.fr.cr
www.cr.cr
www.fcr.cr
www.cfr.cr
www.dr.cr
www.fdr.cr
www.dfr.cr
www.rr.cr
www.frr.cr
www.rfr.cr
www.tr.cr
www.ftr.cr
www.tfr.cr
www.gr.cr
www.fgr.cr
www.gfr.cr
www.vr.cr
www.fvr.cr
www.vfr.cr
www.f.cr
www.fe.cr
www.fre.cr
www.fer.cr
www.fd.cr
www.frd.cr
www.ff.cr
www.frf.cr
www.ffr.cr
www.ft.cr
www.frt.cr
fr.cr 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.
fr.cr 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.