geo.fr website information.
geo.fr domain name is registered by .FR top-level domain registry. See the other sites registred in .FR domain zone.
Following name servers are specified for geo.fr domain:
- venus.vp-dns.net
- deimos.vp-dns.net
- phobos.vp-dns.net
and probably website geo.fr is hosted by WIKIMEDIA - Wikimedia Foundation Inc., US web hosting company. Check the complete list of other most popular websites hosted by WIKIMEDIA - Wikimedia Foundation Inc., US hosting company.
According to Alexa traffic rank the highest website geo.fr position was 16142 (in the world). The lowest Alexa rank position was 20239. Now website geo.fr ranked in Alexa database as number 16554 (in the world).
Website geo.fr Desktop speed measurement score (66/100) is better than the results of 44.37% of other sites shows that the page desktop performance can be improved.
geo.fr Mobile usability score (94/100) is better than the results of 36.81% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of geo.fr (54/100) is better than the results of 41.82% 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 |
|---|---|---|
| Nov-07-2024 | 16,554 | 33 |
| Nov-06-2024 | 16,587 | -305 |
| Nov-05-2024 | 16,282 | 449 |
| Nov-04-2024 | 16,731 | -589 |
| Nov-03-2024 | 16,142 | 504 |
| Nov-02-2024 | 16,646 | -3 |
| Nov-01-2024 | 16,643 | -471 |
Advertisement
geo.fr 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.
geo.fr 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.
%%
%% 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: geo.fr
status: ACTIVE
eppstatus: active
hold: NO
holder-c: PP1385-FRNIC
admin-c: SCS797-FRNIC
tech-c: SCS797-FRNIC
registrar: SPIE CLOUD SERVICES
Expiry Date: 2025-03-28T13:46:19Z
created: 2008-03-28T13:46:19Z
last-update: 2024-04-30T22:13:27.925273Z
source: FRNIC
nserver: deimos.vp-dns.net
nserver: phobos.vp-dns.net
nserver: venus.vp-dns.net
source: FRNIC
registrar: SPIE CLOUD SERVICES
address: 53 Boulevard de Stalingrad
address: 92247 MALAKOFF CEDEX
country: FR
phone: +33.173038505
fax-no: +33.146050654
e-mail: domain@veepee.com
website: http://www.veepee.com
anonymous: No
registered: 2000-09-18T00:00:00Z
source: FRNIC
nic-hdl: PP1385-FRNIC
type: ORGANIZATION
contact: PRISMA MEDIA
address: 13, rue Henri Barbusse
address: 92230 Genevilliers
country: FR
phone: +33.144153012
e-mail: scs-domaine@spie.com
registrar: SPIE CLOUD SERVICES
changed: 2019-09-03T08:31:03Z
anonymous: NO
obsoleted: NO
eppstatus: associated
eppstatus: active
eligstatus: ok
eligsource: REGISTRAR
eligdate: 2019-09-03T00:00:00Z
reachstatus: not identified
source: FRNIC
nic-hdl: SCS797-FRNIC
type: ORGANIZATION
contact: SPIE CLOUD SERVICES
address: SPIE CLOUD SERVICES
address: 53, boulevard de Stalingrad
address: 92247 Malakoff
country: FR
phone: +33.141464283
e-mail: scs-domaine@spie.com
registrar: SPIE CLOUD SERVICES
changed: 2019-09-03T13:08:03Z
anonymous: NO
obsoleted: NO
eppstatus: associated
eppstatus: active
eligstatus: ok
eligsource: REGISTRAR
eligdate: 2019-09-03T00:00:00Z
reachstatus: ok
reachmedia: email
reachsource: REGISTRAR
reachdate: 2019-09-03T00:00:00Z
source: FRNIC
>>> Last update of WHOIS database: 2024-09-13T08:18:25.557911Z
geo.fr server information
geo.fr desktop page speed rank
Last tested: 2018-05-12
geo.fr Desktop Speed Test Quick Summary
priority - 32 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 308.5KiB (41% reduction).
Compressing and resizing https://geo.img.pmdstatic.net/fit/https.3A.2F.2Fww…ns-les-lagons-geo1.jpg could save 38KiB (73% reduction).
Compressing and resizing https://geo.img.pmdstatic.net/fit/https.3A.2F.2Fww…ns-les-lagons-geo1.jpg could save 38KiB (73% reduction).
Compressing https://geo.img.pmdstatic.net/fit/https.3A.2F.2Fww…uveau-magazine-geo.png could save 22.9KiB (17% reduction).
Compressing https://geo.img.pmdstatic.net/fit/https.3A.2F.2Fww…eau-geo-collection.png could save 21.7KiB (18% reduction).
Compressing https://geo.img.pmdstatic.net/fit/https.3A.2F.2Fww…ture-n-3-est-sorti.png could save 21KiB (19% reduction).
Compressing and resizing https://geo.img.pmdstatic.net/fit/https.3A.2F.2Fww…reapprend-a-nager1.jpg could save 14.8KiB (67% reduction).
Compressing and resizing https://geo.img.pmdstatic.net/fit/https.3A.2F.2Fww…reapprend-a-nager1.jpg could save 14.8KiB (67% reduction).
Compressing https://geo.img.pmdstatic.net/pad/https.3A.2F.2Fph…/logoGEO-xl.png?2.26.5 could save 6.2KiB (66% reduction).
Compressing https://geo.img.pmdstatic.net/fit/https.3A.2F.2Fph…/65/logoAFP.png?2.26.5 could save 730B (23% reduction).
priority - 11 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://cdn.elasticad.net/native/serve/js/quantx/nativeEmbed.gz.js (expiration not specified)
http://cdn.elasticad.net/native/serve/js/quantx/prebid.gz.js (expiration not specified)
https://tag.audience.acpm.fr/js/on-1.0.min.js (expiration not specified)
https://ssl.ligatus.com/rms/rend?id=87505&ua=1382040560&pgw=1366&pgo=l&s=1 (60 seconds)
https://static.hotjar.com/c/hotjar-331291.js?sv=5 (60 seconds)
https://acdn.pulpix.com/api/v1/user/1024/preferenc…onpcb_preferences_1024 (5 minutes)
https://a-ssl.ligatus.com/?ids=87505&t=js&s=1 (10 minutes)
https://cdn.pulpix.com/static/pulpix.js (10 minutes)
http://js.antvoice.com/sr-geo.js (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-23KX (15 minutes)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://connect.facebook.net/fr_FR/sdk.js (20 minutes)
https://connect.facebook.net/signals/config/512688…2829?v=2.8.14&r=stable (20 minutes)
http://cse.google.com/adsense/search/async-ads.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google.com/jsapi?autoload=%7B%22modules…22%3A%22fr%22%7D%5D%7D (60 minutes)
https://gum.criteo.com/sync?c=30&r=2&j=cr_handle_data_a (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
https://js-agent.newrelic.com/nr-1071.min.js (2 hours)
https://ssl.google-analytics.com/ga.js (2 hours)
priority - 5 Reduce server response time
In our test, your server responded in 0.69 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 - 2 Eliminate 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.
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.
Optimize CSS Delivery of the following:
priority - 1 Minify 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 11.3KiB (22% reduction).
Minifying http://pixel.adsafeprotected.com/jload?anId=10090&…423723889&cb=253990804 could save 2KiB (19% reduction) after compression.
Minifying http://pixel.adsafeprotected.com/jload?anId=10090&…43497755&cb=1004695537 could save 2KiB (19% reduction) after compression.
Minifying http://connect.facebook.net/en_US/fbds.js could save 695B (34% reduction) after compression.
priority - 0 Enable 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 4.8KiB (64% reduction).
Compressing https://acdn.pulpix.com/api/v1/user/1024/preferenc…onpcb_preferences_1024 could save 1.8KiB (66% reduction).
priority - 0 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 4.6KiB (35% reduction).
Minifying http://www.google.com/cse/static/style/look/v2/minimalist.css could save 705B (21% reduction) after compression.
geo.fr Desktop Resources
| Total Resources | 197 |
| Number of Hosts | 63 |
| Static Resources | 127 |
| JavaScript Resources | 58 |
| CSS Resources | 5 |
geo.fr Desktop Resource Breakdown
geo.fr mobile page speed rank
Last tested: 2017-11-28
geo.fr Mobile Speed Test Quick Summary
priority - 32 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 1 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:
http://www.geo.fr/js/routing?callback=fos.Router.setData
Optimize CSS Delivery of the following:
priority - 21 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://cdn.elasticad.net/native/serve/js/nativeEmbed.gz.js (expiration not specified)
http://js.agkn.com/prod/v0/tag.js (expiration not specified)
https://cdn.deepsight.io/prisma_media/ds_prisma.js (expiration not specified)
https://d28qf49oqakg8u.cloudfront.net/publisher_sc…pubscript_incontent.js (expiration not specified)
https://ssl.ligatus.com/rms/rend?id=87505&ua=-955689442&pgw=412&pgo=p&s=1 (55 seconds)
https://static.hotjar.com/c/hotjar-331291.js?sv=5 (60 seconds)
http://dmp.theadex.com/d/410/1103/s/adex.js (5 minutes)
https://acdn.pulpix.com/api/v1/user/1024/preferenc…onpcb_preferences_1024 (5 minutes)
https://a-ssl.ligatus.com/?ids=87505&t=js&s=1 (10 minutes)
https://api.pulpix.com/api/v1/ping (10 minutes)
https://cdn.pulpix.com/static/pulpix.js (10 minutes)
http://js.antvoice.com/sr-geo.js (15 minutes)
http://www.googletagmanager.com/gtm.js?id=GTM-23KX (15 minutes)
http://www.googletagservices.com/tag/js/gpt.js (15 minutes)
http://connect.facebook.net/en_US/fbds.js (20 minutes)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://connect.facebook.net/fr_FR/sdk.js (20 minutes)
https://connect.facebook.net/signals/config/512688668902829?v=2.8.1 (20 minutes)
http://c.amazon-adsystem.com/aax2/csm.js.gz (60 minutes)
http://cse.google.com/adsense/search/async-ads.js (60 minutes)
http://pagead2.googlesyndication.com/pagead/osd.js (60 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google.com/jsapi?autoload=%7B%22modules…22%3A%22fr%22%7D%5D%7D (60 minutes)
https://gum.criteo.com/sync?c=30&r=2&j=cr_handle_data_a (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)
https://js-agent.newrelic.com/nr-1044.min.js (2 hours)
https://js-agent.newrelic.com/nr-1059.min.js (2 hours)
priority - 15 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 150.3KiB (23% reduction).
Compressing http://img.geo.pmdstatic.net/fit/http.3A.2F.2Fwww.…ro-du-magazine-geo.png could save 33.7KiB (18% reduction).
Compressing http://img.geo.pmdstatic.net/fit/http.3A.2F.2Fwww.…e-geo-aventure-n-2.png could save 32.4KiB (17% reduction).
Compressing http://img.geo.pmdstatic.net/fit/http.3A.2F.2Fwww.…ro-de-geo-histoire.png could save 24.3KiB (15% reduction).
Compressing https://m.media-amazon.com/images/I/41-I35-LkjL.png could save 18.3KiB (69% reduction).
Compressing http://img.geo.pmdstatic.net/pad/http.3A.2F.2Fphot…/logoGEO-xl.png?2.24.5 could save 6.2KiB (66% reduction).
Compressing http://img.geo.pmdstatic.net/fit/http.3A.2F.2Fphot…/65/logoAFP.png?2.24.5 could save 730B (23% reduction).
priority - 12 Reduce server response time
In our test, your server responded in 0.97 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 - 8 Prioritize 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 - 2 Enable 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 19KiB (66% reduction).
Compressing http://js.agkn.com/prod/v0/tag.js could save 1.6KiB (56% reduction).
Compressing http://i.ligatus.com/fr-placements/containers/prisma/2015/geo/tc-site.js could save 774B (72% reduction).
priority - 1 Minify 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 11.5KiB (24% reduction).
Minifying http://mozoo.ezakus.net/marker/?group=ez101&tjs=1511925622781 could save 1.4KiB (23% reduction) after compression.
Minifying http://pixel.adsafeprotected.com/jload?anId=10090&…28922329&cb=1818228241 could save 1KiB (24% reduction) after compression.
Minifying http://pixel.adsafeprotected.com/jload?anId=10090&…16125249&cb=1574529167 could save 1KiB (24% reduction) after compression.
Minifying http://pixel.adsafeprotected.com/jload?anId=10090&…423723889&cb=269766483 could save 1KiB (24% reduction) after compression.
Minifying http://connect.facebook.net/en_US/fbds.js could save 691B (33% reduction) after compression.
priority - 0 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 4.5KiB (37% reduction).
Minifying http://www.google.com/cse/static/style/look/minimalist.css could save 589B (24% reduction) after compression.
geo.fr Mobile Resources
| Total Resources | 242 |
| Number of Hosts | 77 |
| Static Resources | 157 |
| JavaScript Resources | 89 |
| CSS Resources | 8 |
geo.fr Mobile Resource Breakdown
geo.fr mobile page usability
Last tested: 2017-11-28
geo.fr Mobile Usability Test Quick Summary
priority - 5 Size 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="http://www.pri…n-des-donnees/">notre charte p…personnelles.</a> is close to 1 other tap targets.The tap target
<a href="https://www.fa…iffusee-181854" class="social"></a> and 21 others are close to other tap targets.The tap target
<li class="social-button dots"></li> and 10 others are close to other tap targets.The tap target
<li class="social-button dots"></li> and 10 others are close to other tap targets.The tap target
<a href="http://blogs.geo.fr/" class="white">Découvrir les blogs GEO ></a> and 1 others are close to other tap targets.The tap target
<a href="http://www.geo…imard/geoguide">GEO Guides</a> and 43 others are close to other tap targets.The tap target
<a href="http://www.pri…a.com/cgu-geo/">Conditions d'usage</a> and 3 others are close to other tap targets.geo.fr similar domains
www.geo.net
www.geo.org
www.geo.info
www.geo.biz
www.geo.us
www.geo.mobi
www.eo.fr
www.geo.fr
www.feo.fr
www.gfeo.fr
www.fgeo.fr
www.veo.fr
www.gveo.fr
www.vgeo.fr
www.teo.fr
www.gteo.fr
www.tgeo.fr
www.beo.fr
www.gbeo.fr
www.bgeo.fr
www.yeo.fr
www.gyeo.fr
www.ygeo.fr
www.heo.fr
www.gheo.fr
www.hgeo.fr
www.go.fr
www.gwo.fr
www.gewo.fr
www.gweo.fr
www.gso.fr
www.geso.fr
www.gseo.fr
www.gdo.fr
www.gedo.fr
www.gdeo.fr
www.gro.fr
www.gero.fr
www.greo.fr
www.ge.fr
www.gei.fr
www.geoi.fr
www.geio.fr
www.gek.fr
www.geok.fr
www.geko.fr
www.gel.fr
www.geol.fr
www.gelo.fr
www.gep.fr
www.geop.fr
www.gepo.fr
geo.fr 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.
geo.fr 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.