liligo.fr website information.
liligo.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 liligo.fr domain:
- dns1.cscdns.net
- dns2.cscdns.net
and probably website liligo.fr is hosted by FASTLY - Fastly, US web hosting company. Check the complete list of other most popular websites hosted by FASTLY - Fastly, US hosting company.
According to Alexa traffic rank the highest website liligo.fr position was 193344 (in the world). The lowest Alexa rank position was 243203. Now website liligo.fr ranked in Alexa database as number 242167 (in the world).
Website liligo.fr Desktop speed measurement score (71/100) is better than the results of 52.66% of other sites shows that the page desktop performance can be improved.
liligo.fr 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 liligo.fr (51/100) is better than the results of 35.73% 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-18-2024 | 242,167 | -9,230 |
| Apr-17-2024 | 232,937 | 4,673 |
| Apr-16-2024 | 237,610 | -2,669 |
| Apr-15-2024 | 234,941 | 6,795 |
| Apr-14-2024 | 241,736 | -6,300 |
| Apr-13-2024 | 235,436 | 4,307 |
| Apr-12-2024 | 239,743 | 738 |
Advertisement
liligo.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.
liligo.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
%% short date format : DD/MM
%% version : FRNIC-2.5
%%
%% Rights restricted by copyright.
%% See https://www.afnic.fr/en/products-and-services/services/whois/whois-special-notice/
%%
%% Use '-h' option to obtain more information about this service.
%%
%% [YOUR REQUEST] >> liligo.fr
%%
domain: liligo.fr
status: ACTIVE
hold: NO
holder-c: DA10702-FRNIC
admin-c: DA10621-FRNIC
tech-c: DA6025-FRNIC
zone-c: NFC1-FRNIC
nsl-id: NSL19570-FRNIC
registrar: CSC CORPORATE DOMAINS INC.
Expiry Date: 2021-05-26T11:36:13Z
created: 2005-08-16T06:40:54Z
last-update: 2020-05-22T05:20:11Z
source: FRNIC
ns-list: NSL19570-FRNIC
nserver: dns1.cscdns.net
nserver: dns2.cscdns.net
source: FRNIC
registrar: CSC CORPORATE DOMAINS INC.
type: Isp Option 1
address: 251 Little Falls Drive
address: DE 19808 WILMINGTON
country: US
phone: +1 302 636 5400
fax-no: +1 302 636 5454
e-mail: tldsupport@cscglobal.com
website: https://www.cscdigitalbrand.services
anonymous: NO
registered: 2006-10-17T12:00:00Z
source: FRNIC
nic-hdl: DA10702-FRNIC
type: ORGANIZATION
contact: Domain Administrator
address: Odigeo Paris Meta
address: 9, rue rougemont
address: 75009 Paris
country: FR
phone: +33 1 78 41 82 00
fax-no: +33 1 78 41 82 00
e-mail: dns-admin@odigeo.com
registrar: CSC CORPORATE DOMAINS INC.
changed: 2014-05-26T11:37:32Z nic@nic.fr
anonymous: NO
obsoleted: NO
eligstatus: ok
eligsource: REGISTRAR
eligdate: 2014-05-21T13:52:55Z
reachstatus: not identified
source: FRNIC
nic-hdl: DA10621-FRNIC
type: PERSON
contact: Domain Administrator
address: Odigeo Paris Meta
address: 9, rue rougemont
address: 75009 Paris
country: FR
phone: +33 1 78 41 82 00
fax-no: +33 1 78 41 82 00
e-mail: dns-admin@odigeo.com
registrar: CSC CORPORATE DOMAINS INC.
changed: 2014-05-09T17:57:10Z nic@nic.fr
anonymous: NO
obsoleted: NO
eligstatus: not identified
reachstatus: not identified
source: FRNIC
nic-hdl: DA6025-FRNIC
type: PERSON
contact: Dns Administrator
address: CSC Corporate Domains, Inc.
address: 251 Little Falls Drive
address: 19808 Wilmington
address: DE
country: US
phone: +1 3026365400
fax-no: +1 3026365454
e-mail: dns-admin@cscglobal.com
registrar: CSC CORPORATE DOMAINS INC.
changed: 2018-10-04T13:58:09Z nic@nic.fr
anonymous: NO
obsoleted: NO
eligstatus: ok
eligsource: REGISTRAR
eligdate: 2018-10-04T13:58:09Z
reachmedia: email
reachstatus: ok
reachsource: REGISTRAR
reachdate: 2018-10-04T13:58:09Z
source: FRNIC
liligo.fr server information
liligo.fr desktop page speed rank
Last tested: 2016-07-13
liligo.fr Desktop Speed Test Quick Summary
priority - 15 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 143.5KiB (69% reduction).
Compressing http://static.liligo.com/servlet/pp/v6/liligo/full.js?r=1463697326000 could save 48.5KiB (65% reduction).
Compressing https://api.boxever.com/v1.2/boxever-cross-domain.…%2F%2Fwww.liligo.fr%2F could save 17.4KiB (69% reduction).
Compressing https://api.boxever.com/v1.2/boxever-min.js?client…pkwgctbd5wdgmnjdg05dif could save 17.1KiB (68% reduction).
Compressing http://www.liligo.fr/servlet/l/FrontendHPv5?h=ffffffff944a67d6&siteFolder= could save 7.1KiB (66% reduction).
Compressing http://www.liligo.fr/servlet/l/FrontendSmartAppBan…ffaa056828&siteFolder= could save 1.3KiB (77% reduction).
Compressing http://tag.yieldoptimizer.com/ps/ps?p=2567&t=s&pg=hm&cr=fr&tc=93735080 could save 661B (54% reduction).
priority - 14 Eliminate 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.
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:
http://static.liligo.com/servlet/pp/v6/homepage/cs…7929478000&l=fr&v=5619
http://static.liligo.com/v6/homepage/fonts/lilifont-legacy.css
priority - 10 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://www.googletagmanager.com/gtm.js?id=GTM-TZQ57Z&l=_gtmDataLayer (15 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://static.liligo.com/v6/homepage/fonts/lilifont-legacy.css (2 hours)
http://static.liligo.com/v6/homepage/img/bg-beach.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…ight/fr/Nice-Paris.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…t/fr/Paris-Bangkok.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…fr/Paris-Barcelone.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…ht/fr/Paris-Berlin.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…fr/Paris-Marrakech.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…fr/Paris-Marseille.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…/fr/Paris-Montreal.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…t/fr/Paris-NewYork.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…ight/fr/Paris-Nice.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…ight/fr/Paris-Rome.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…/fr/Paris-Toulouse.jpg (2 hours)
http://static.liligo.com/v6/homepage/modules/botto…/fr/Toulouse-Paris.jpg (2 hours)
http://www.google-analytics.com/analytics.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)
http://www.liligo.fr/a/api/comparesite/src/index.js?r=93cc6056c89f12baae8e (2 hours)
priority - 2 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 18.3KiB (73% reduction).
priority - 1 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 8.9KiB (13% reduction).
Losslessly compressing http://static.liligo.com/v6/homepage/modules/botto…fr/Paris-Marseille.jpg could save 916B (12% reduction).
Losslessly compressing http://static.liligo.com/v6/homepage/modules/botto…/fr/Toulouse-Paris.jpg could save 915B (13% reduction).
Losslessly compressing http://static.liligo.com/v6/homepage/modules/botto…ight/fr/Nice-Paris.jpg could save 914B (15% reduction).
Losslessly compressing http://static.liligo.com/v6/homepage/modules/botto…fr/Paris-Marrakech.jpg could save 911B (11% reduction).
Losslessly compressing http://static.liligo.com/v6/homepage/modules/botto…/fr/Paris-Toulouse.jpg could save 910B (14% reduction).
Losslessly compressing http://static.liligo.com/v6/homepage/modules/botto…t/fr/Paris-Bangkok.jpg could save 907B (11% reduction).
Losslessly compressing http://static.liligo.com/v6/homepage/modules/botto…t/fr/Paris-NewYork.jpg could save 907B (14% reduction).
Losslessly compressing http://static.liligo.com/v6/homepage/modules/botto…/fr/Paris-Montreal.jpg could save 906B (13% reduction).
Losslessly compressing http://static.liligo.com/v6/homepage/modules/botto…ight/fr/Paris-Rome.jpg could save 906B (11% reduction).
liligo.fr Desktop Resources
| Total Resources | 77 |
| Number of Hosts | 30 |
| Static Resources | 29 |
| JavaScript Resources | 19 |
| CSS Resources | 3 |
liligo.fr Desktop Resource Breakdown
liligo.fr mobile page speed rank
Last tested: 2017-05-03
liligo.fr Mobile Speed Test Quick Summary
priority - 56 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 2 blocking script resources and 7 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://m.liligo.fr/servlet/l/FrontendMobileWebV5Ho…h=50a55e87&siteFolder=
Optimize CSS Delivery of the following:
http://static.liligo.com/a/mobileweb_v4/app/forms/forms.css?r=1493741726000
http://static.liligo.com/mobileweb_v4/brand/base/assets/fonts/lilifont2.css
http://static.liligo.com/mobileweb_v4/brand/base/assets/fonts/logofont.css
http://static.liligo.com/a/mobileweb_v4/app/forms//forms.css
http://static.liligo.com/a/mobileweb_v4/app/common…ter//widthSplitter.css
http://static.liligo.com/a/mobileweb_v4/app/common…tAppBanner//banner.css
priority - 26 Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
http://www.liligo.fr/
http://m.liligo.fr/
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 - 8 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:
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/1741335339466782?v=stable (20 minutes)
http://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
http://static.liligo.com/a/mobileweb_v4/app/common…tAppBanner//banner.css (2 hours)
http://static.liligo.com/a/mobileweb_v4/app/common…ter//widthSplitter.css (2 hours)
http://static.liligo.com/a/mobileweb_v4/app/forms//forms.css (2 hours)
http://static.liligo.com/mobileweb_v4/brand/base/assets/fonts/lilifont2.css (2 hours)
http://static.liligo.com/mobileweb_v4/brand/base/assets/fonts/logofont.css (2 hours)
http://static.liligo.com/v6/homepage/img/bg-beach.jpg (2 hours)
http://www.google-analytics.com/analytics.js (2 hours)
http://www.google-analytics.com/ga.js (2 hours)
priority - 6 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 55.1KiB (68% reduction).
Compressing https://api.boxever.com/v1.2/boxever-cross-domain.….liligo.fr%2F%23%2Fair could save 17.4KiB (69% reduction).
Compressing https://api.boxever.com/v1.2/boxever-min.js?client…4xhDV9rsny82DvKa1iYFBN could save 17.1KiB (68% reduction).
Compressing http://dis.eu.criteo.com/dis/dis.aspx?p=1265&cb=27…32&sc_d=24&site_type=m could save 828B (53% reduction).
Compressing http://tag.yieldoptimizer.com/ps/ps?tc=222374487&t=s&p=2567&pg=m-hm&cr=fr could save 682B (55% reduction).
priority - 2 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 18.3KiB (73% reduction).
priority - 1 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 7.8KiB (16% reduction).
Minifying http://static.liligo.com/a/mobileweb_v4/app/forms/forms.css?r=1493741726000 could save 3.9KiB (16% reduction) after compression.
liligo.fr Mobile Resources
| Total Resources | 65 |
| Number of Hosts | 33 |
| Static Resources | 19 |
| JavaScript Resources | 17 |
| CSS Resources | 7 |
liligo.fr Mobile Resource Breakdown
liligo.fr mobile page usability
Last tested: 2017-05-03
liligo.fr similar domains
www.liligo.net
www.liligo.org
www.liligo.info
www.liligo.biz
www.liligo.us
www.liligo.mobi
www.iligo.fr
www.liligo.fr
www.piligo.fr
www.lpiligo.fr
www.pliligo.fr
www.oiligo.fr
www.loiligo.fr
www.oliligo.fr
www.kiligo.fr
www.lkiligo.fr
www.kliligo.fr
www.lligo.fr
www.luligo.fr
www.liuligo.fr
www.luiligo.fr
www.ljligo.fr
www.lijligo.fr
www.ljiligo.fr
www.lkligo.fr
www.likligo.fr
www.loligo.fr
www.lioligo.fr
www.liigo.fr
www.lipigo.fr
www.lilpigo.fr
www.lipligo.fr
www.lioigo.fr
www.liloigo.fr
www.likigo.fr
www.lilkigo.fr
www.lilgo.fr
www.lilugo.fr
www.liliugo.fr
www.liluigo.fr
www.liljgo.fr
www.lilijgo.fr
www.liljigo.fr
www.lilkgo.fr
www.lilikgo.fr
www.lilogo.fr
www.liliogo.fr
www.lilio.fr
www.lilifo.fr
www.liligfo.fr
www.lilifgo.fr
www.lilivo.fr
www.liligvo.fr
www.lilivgo.fr
www.lilito.fr
www.liligto.fr
www.lilitgo.fr
www.lilibo.fr
www.liligbo.fr
www.lilibgo.fr
www.liliyo.fr
www.liligyo.fr
www.liliygo.fr
www.liliho.fr
www.liligho.fr
www.lilihgo.fr
www.lilig.fr
www.liligi.fr
www.liligoi.fr
www.liligio.fr
www.liligk.fr
www.liligok.fr
www.liligko.fr
www.liligl.fr
www.liligol.fr
www.liliglo.fr
www.liligp.fr
www.liligop.fr
www.liligpo.fr
liligo.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.
liligo.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.