lily.mg website information.
lily.mg domain name is registered by .MG top-level domain registry. See the other sites registred in .MG domain zone.
Following name servers are specified for lily.mg domain:
- ns1.eurodns.com
- ns2.eurodns.com
- ns3.eurodns.com
- ns4.eurodns.com
According to Alexa traffic rank the highest website lily.mg position was 81583 (in the world). The lowest Alexa rank position was 969167. Current position of lily.mg in Alexa rank database is below 1 million.
Website lily.mg 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.
lily.mg Mobile usability score (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed measurement score of lily.mg (58/100) is better than the results of 50.23% 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-18-2024 | N/A | N/A |
Nov-17-2024 | N/A | N/A |
Nov-16-2024 | N/A | N/A |
Nov-15-2024 | N/A | N/A |
Nov-14-2024 | N/A | N/A |
Nov-13-2024 | N/A | N/A |
Nov-12-2024 | N/A | N/A |
Advertisement
lily.mg 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.
lily.mg 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.
Domain Name: lily.mg
Registry Domain ID: 439193-nicmg
Updated Date: 2024-07-29T08:08:58.726Z
Creation Date: 2023-07-27T10:33:35.835Z
Registry Expiry Date: 2025-07-27T10:33:35.991Z
Registrar Registration Expiration Date: 2025-07-27T10:33:35.991Z
Registrar: 3AS Company SARL
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: 0ZTXh-LZKlE
Registrant Name: Redacted | Registry Policy
Registrant Street: Redacted | Registry Policy
Registrant City: Redacted | Registry Policy
Registrant State/Province: Redacted | Registry Policy
Registrant Postal Code: Redacted | Registry Policy
Registrant Country: MG
Registrant Phone: Redacted | Registry Policy
Registrant Email: Redacted | Registry Policy
Name Server: bayan.ns.cloudflare.com
Name Server: cheryl.ns.cloudflare.com
DNSSEC: unsigned
>>> Last update of WHOIS database: 2024-10-18T18:11:20.345Z
lily.mg server information
lily.mg desktop page speed rank
Last tested: 2017-05-21
lily.mg Desktop Speed Test Quick Summary
priority - 13 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://lily.mg/resources/carousel/css/style.css (expiration not specified)
http://lily.mg/resources/carousel/js/jquery.flexisel.js (expiration not specified)
http://lily.mg/resources/css/bootstrap-responsive.min.css (expiration not specified)
http://lily.mg/resources/css/bootstrap.min.css (expiration not specified)
http://lily.mg/resources/css/display-error.css (expiration not specified)
http://lily.mg/resources/css/font-awesome.css (expiration not specified)
http://lily.mg/resources/css/jquery.custombox.css (expiration not specified)
http://lily.mg/resources/css/layout-responsive.css (expiration not specified)
http://lily.mg/resources/css/layout.css (expiration not specified)
http://lily.mg/resources/css/nivo-slider.css (expiration not specified)
http://lily.mg/resources/css/slider-theme/default.css (expiration not specified)
http://lily.mg/resources/img/social-buttons/blog.jpg (expiration not specified)
http://lily.mg/resources/img/social-buttons/fb-grey.png (expiration not specified)
http://lily.mg/resources/img/social-buttons/gg-grey.png (expiration not specified)
http://lily.mg/resources/img/social-buttons/tw-grey.png (expiration not specified)
http://lily.mg/resources/jquery-reveal/reveal.css (expiration not specified)
http://lily.mg/resources/js/autotrack.js (expiration not specified)
http://lily.mg/resources/js/jquery-1.7.2.min.js (expiration not specified)
http://lily.mg/resources/js/jquery.cookie.js (expiration not specified)
http://server1.affiz.net/tracking/ads_display.php?…f426db&rdads=650657214 (1 second)
http://server1.affiz.net/tracking/ads_display.php?…0e3e5d&rdads=246265375 (1 second)
http://server1.affiz.net/tracking/ads_display.php?…ccbcc2&rdads=869289086 (2 seconds)
http://connect.facebook.net/en_US/fbevents.js (20 minutes)
http://connect.facebook.net/signals/config/539178939563902?v=2.7.10 (20 minutes)
https://connect.facebook.net/fr_FR/all.js (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 11 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 106.9KiB (44% reduction).
Compressing and resizing http://res.cloudinary.com/lily/image/upload/c_pad,…dys2_1476799291699.jpg could save 10.7KiB (93% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/c_pad,…33805039553366.jpg?ts= could save 10KiB (66% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/c_pad,…63383164161415.jpg?ts= could save 8KiB (69% reduction).
Compressing and resizing http://res.cloudinary.com/lily/image/upload/c_pad,…bghb_1479824477715.jpg could save 7.9KiB (78% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/f_auto…NIe%CC%80RE_SOMECA.jpg could save 7.8KiB (28% reduction).
Compressing and resizing http://res.cloudinary.com/lily/image/upload/c_pad,…oxd2_1490010697131.jpg could save 6.6KiB (74% reduction).
Compressing and resizing http://res.cloudinary.com/lily/image/upload/c_pad,…bk6u_1481270227631.jpg could save 4.9KiB (78% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/0qvgpg_0.jpg could save 4.7KiB (56% reduction).
Compressing and resizing http://res.cloudinary.com/lily/image/upload/c_pad,…yhx9_1478070860119.jpg could save 3.1KiB (78% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/yrfdkc_0.jpg could save 2.6KiB (30% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/eezj28_0.jpg could save 2.2KiB (34% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/y3o91i_0.jpg could save 2.1KiB (37% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/3781es_0.jpg could save 2KiB (30% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/gmk1yh_0.jpg could save 2KiB (30% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/kzxbow_0.jpg could save 2KiB (31% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/tcph9f_0.jpg could save 1.7KiB (28% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/bu5mdo_0.jpg could save 1.6KiB (31% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/c_pad,…95882958866977.jpg?ts= could save 1.6KiB (39% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…rjr0_1494597988304.jpg could save 1.4KiB (27% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/qs40me_0.jpg could save 1.4KiB (25% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/j2bsh3_0.jpg could save 1.3KiB (24% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/4c7z39_0.jpg could save 1.3KiB (25% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/zm6fxj_0.jpg could save 1.1KiB (32% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/mgehnu_0.jpg could save 1.1KiB (28% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/ycwnaw_0.jpg could save 1,021B (19% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…u455_1467190989605.jpg could save 999B (21% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…h1d2_1467190989805.jpg could save 923B (22% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/c_pad,…76958397639769.jpg?ts= could save 900B (26% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/c_pad,…04662273261923.jpg?ts= could save 839B (24% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…120/asset/t2bgy5_0.jpg could save 832B (22% reduction).
priority - 9 Reduce server response time
In our test, your server responded in 1.1 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 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 81.7KiB (66% reduction).
Compressing http://lily.mg/resources/carousel/js/jquery.flexisel.js could save 12.9KiB (81% reduction).
Compressing http://lily.mg/resources/js/autotrack.js could save 7.4KiB (68% reduction).
Compressing http://lily.mg/resources/js/jquery.cookie.js could save 1.7KiB (56% reduction).
priority - 8 Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 6 blocking script resources and 13 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://lily.mg/resources/js/jquery.cookie.js
http://www.googleadservices.com/pagead/conversion.js
http://server1.affiz.net/tracking/ads_display.php?…ccbcc2&rdads=869289086
http://server1.affiz.net/tracking/ads_display.php?…f426db&rdads=650657214
http://server1.affiz.net/tracking/ads_display.php?…0e3e5d&rdads=246265375
Optimize CSS Delivery of the following:
http://lily.mg/resources/css/bootstrap.min.css
http://lily.mg/resources/css/bootstrap-responsive.min.css
http://lily.mg/resources/css/font-awesome.css
http://lily.mg/resources/css/layout.css
http://lily.mg/resources/css/layout-responsive.css
http://lily.mg/resources/jquery-reveal/reveal.css
http://lily.mg/resources/css/custom.css?t=1
http://lily.mg/resources/css/jquery.custombox.css
http://lily.mg/resources/css/nivo-slider.css
http://lily.mg/resources/css/slider-theme/default.css
http://lily.mg/resources/css/display-error.css
http://lily.mg/resources/ad/css/advertising.css
priority - 2 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 18KiB (31% reduction).
Minifying http://lily.mg/combined.js?id=b49c10f115c1fba could save 7KiB (18% reduction) after compression.
Minifying http://lily.mg/resources/js/jquery.cookie.js could save 1.3KiB (43% reduction).
Minifying http://connect.facebook.net/signals/config/539178939563902?v=2.7.10 could save 630B (79% 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 514B (29% reduction).
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 1.5KiB (14% reduction).
lily.mg Desktop Resources
Total Resources | 79 |
Number of Hosts | 11 |
Static Resources | 65 |
JavaScript Resources | 16 |
CSS Resources | 14 |
lily.mg Desktop Resource Breakdown
lily.mg mobile page speed rank
Last tested: 2017-05-21
lily.mg Mobile Speed Test Quick Summary
priority - 40 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 - 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://m.lily.mg/?
http://tana.lily.mg/?
priority - 4 Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 42.1KiB (44% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…_80/asset/24qh44_0.jpg could save 4KiB (36% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…_80/asset/0qvgpg_0.jpg could save 3.1KiB (31% reduction).
Compressing http://tana.lily.mg/images/insert.png could save 2.9KiB (77% reduction).
Compressing http://tana.lily.mg/images/logo/tana.png could save 1.2KiB (26% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…_80/asset/t2bgy5_0.jpg could save 673B (12% reduction).
Compressing http://res.cloudinary.com/lily/image/upload/d_404.…_80/asset/zm6fxj_0.jpg could save 544B (11% reduction).
priority - 3 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://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/539178939563902?v=2.7.10 (20 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
priority - 2 Reduce server response time
In our test, your server responded in 0.31 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 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 14.4KiB (67% reduction).
Compressing http://tana.lily.mg/js/jquery.timeago.js could save 5.3KiB (69% reduction).
Compressing http://tana.lily.mg/js/jquery.cookie.js could save 1.7KiB (56% 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 5.2KiB (46% reduction).
Minifying http://tana.lily.mg/js/jquery.cookie.js could save 1.3KiB (43% reduction).
Minifying https://connect.facebook.net/signals/config/539178939563902?v=2.7.10 could save 630B (79% 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 826B (19% reduction).
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 772B (17% reduction).
lily.mg Mobile Resources
Total Resources | 55 |
Number of Hosts | 15 |
Static Resources | 30 |
JavaScript Resources | 14 |
CSS Resources | 4 |
lily.mg Mobile Resource Breakdown
lily.mg mobile page usability
Last tested: 2017-05-21
lily.mg Mobile Usability Test Quick Summary
priority - 0 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="/a/insert"></a>
is close to 2 other tap targets.lily.mg similar domains
www.lily.net
www.lily.org
www.lily.info
www.lily.biz
www.lily.us
www.lily.mobi
www.ily.mg
www.lily.mg
www.pily.mg
www.lpily.mg
www.plily.mg
www.oily.mg
www.loily.mg
www.olily.mg
www.kily.mg
www.lkily.mg
www.klily.mg
www.lly.mg
www.luly.mg
www.liuly.mg
www.luily.mg
www.ljly.mg
www.lijly.mg
www.ljily.mg
www.lkly.mg
www.likly.mg
www.loly.mg
www.lioly.mg
www.liy.mg
www.lipy.mg
www.lilpy.mg
www.liply.mg
www.lioy.mg
www.liloy.mg
www.liky.mg
www.lilky.mg
www.lil.mg
www.lilt.mg
www.lilyt.mg
www.lilty.mg
www.lilg.mg
www.lilyg.mg
www.lilgy.mg
www.lilh.mg
www.lilyh.mg
www.lilhy.mg
www.lilu.mg
www.lilyu.mg
www.liluy.mg
lily.mg 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.
lily.mg 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.