LINE.ME LINE : Free Calls & Messages


line.me website information.

line.me website servers are located in Japan and are responding from following IP address 203.104.138.138. Check the full list of most visited websites located in Japan.

line.me domain name is registered by .ME top-level domain registry. See the other sites registred in .ME domain zone.

Following name servers are specified for line.me domain:

  • ns1.naver.jp
  • ns2.naver.jp
  • adns2.naver.com
  • adns1.naver.com

and probably website line.me is hosted by naver.jp web hosting company. Check the complete list of other most popular websites hosted by naver.jp hosting company.

According to Alexa traffic rank the highest website line.me position was 222 (in the world). The lowest Alexa rank position was 1531. Now website line.me ranked in Alexa database as number 222 (in the world).

Website line.me Desktop speed measurement score (71/100) is better than the results of 54.13% of other sites shows that the page desktop performance can be improved.

line.me 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 line.me (60/100) is better than the results of 54.57% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Weekly Rank Report

DateRankChange
May-23-2019 N/AN/A
May-22-2019 22253
May-21-2019 27513
May-20-2019 288-41
May-19-2019 247-12
May-18-2019 2358
May-17-2019 243-4

Advertisement

line.me 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.


line.me 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: LINE.ME
Registry Domain ID: D108500000000003866-AGRS
Registrar WHOIS Server:
Registrar URL: http://www.1api.net
Updated Date: 2017-10-02T13:58:43Z
Creation Date: 2008-04-29T18:01:09Z
Registry Expiry Date: 2019-04-29T18:01:09Z
Registrar Registration Expiration Date:
Registrar: 1API GmbH
Registrar IANA ID: 1387
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant Organization: LINE Corporation
Registrant State/Province: Tokyo
Registrant Country: JP
Name Server: NS1.NAVER.JP
Name Server: NS2.NAVER.JP
Name Server: ADNS1.NAVER.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2018-06-05T14:44:41Z

line.me server information

Servers Location

line.me desktop page speed rank

Last tested: 2017-04-28


Desktop Speed Medium
71/100

line.me Desktop Speed Test Quick Summary


priority - 14 Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 3 blocking script resources and 2 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:

https://static.line.naver.jp/line_lp/js/html5_1492657837.js
https://static.line.naver.jp/line_lp/js/lc.line.lp.pc.common_1492657837.js
https://static.line.naver.jp/line_lp/js/lc.line.lp.pc.line_1492657837.js

Optimize CSS Delivery of the following:

https://static.line.naver.jp/line_lp/css/line_lp_pc_1492657837.css
https://fonts.googleapis.com/css?family=Roboto:700,300,400,100,500

priority - 11 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 109.6KiB (15% reduction).

Compressing https://d.line-scdn.net/stf/line-lp/PC_Game_Play_en_123123.png could save 68.4KiB (14% reduction).
Compressing https://d.line-scdn.net/stf/line-lp/PC_banner_440_en.png could save 21.2KiB (16% reduction).
Compressing https://d.line-scdn.net/stf/line-lp/PC_LINE_Store_en_1231231.png could save 13.4KiB (15% reduction).
Compressing https://d.line-scdn.net/stf/line-lp/en_2016_08.png could save 3KiB (14% reduction).
Compressing https://static.line.naver.jp/line_lp/img/commonPC/…SelectLayer.png?140218 could save 2.7KiB (97% reduction).
Compressing https://static.line.naver.jp/line_lp/img/spacer.gif could save 1KiB (93% reduction).

priority - 11 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 103.3KiB (68% reduction).

Compressing https://static.line.naver.jp/line_lp/js/lc.line.lp.pc.common_1492657837.js could save 68.7KiB (65% reduction).
Compressing https://static.line.naver.jp/line_lp/css/line_lp_pc_1492657837.css could save 20.8KiB (81% reduction).
Compressing https://line.me/en/ could save 9.2KiB (69% reduction).
Compressing https://static.line.naver.jp/line_lp/js/lc.line.lp.pc.line_1492657837.js could save 3.2KiB (63% reduction).
Compressing https://static.line.naver.jp/line_lp/js/html5_1492657837.js could save 1.3KiB (50% reduction).

priority - 2 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.

Only about 2% of the final above-the-fold content could be rendered with the full HTML response.

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:

https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://d.line-scdn.net/stf/line-lp/en_2016_04.png (5.1 hours)
https://d.line-scdn.net/stf/line-lp/PC_visual_01_en_0802.png (6.2 hours)
https://d.line-scdn.net/stf/line-lp/en_2016_02.png (7.4 hours)
https://d.line-scdn.net/stf/line-lp/PC_banner_440_en.png (8.7 hours)

line.me Desktop Resources

Total Resources33
Number of Hosts8
Static Resources24
JavaScript Resources5
CSS Resources2

line.me Desktop Resource Breakdown

line.me mobile page speed rank

Last tested: 2017-04-26


Mobile Speed Bad
60/100

line.me Mobile Speed Test Quick Summary


priority - 48 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:

https://static.line.naver.jp/line_lp/js/lc.line.lp.sp.common_1492657837.js
https://static.line.naver.jp/line_lp/js/lc.line.lp.sp.line_1492657837.js

Optimize CSS Delivery of the following:

https://static.line.naver.jp/line_lp/css/line_lp_sp_1492657837.css

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.

Only about 32% of the final above-the-fold content could be rendered with the full HTML response.

priority - 7 Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 71.1KiB (13% reduction).

Compressing https://d.line-scdn.net/stf/line-lp/SP_Game_Play_en_123123.png could save 40.5KiB (12% reduction).
Compressing https://d.line-scdn.net/stf/line-lp/SP_banner_main_en.png could save 17.8KiB (17% reduction).
Compressing https://d.line-scdn.net/stf/line-lp/SP_LINE_Store_en_1231231.png could save 12.7KiB (16% reduction).

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 54.5KiB (67% reduction).

Compressing https://static.line.naver.jp/line_lp/js/lc.line.lp.sp.common_1492657837.js could save 30.8KiB (65% reduction).
Compressing https://static.line.naver.jp/line_lp/css/line_lp_sp_1492657837.css could save 10.6KiB (77% reduction).
Compressing https://line.me/en/ could save 7KiB (67% reduction).
Compressing https://static.line.naver.jp/line_lp/js/lc.line.lp.sp.line_1492657837.js could save 6.1KiB (65% reduction).

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:

https://www.google-analytics.com/plugins/ua/linkid.js (60 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://d.line-scdn.net/stf/line-lp/SP_visual_01_en_0802.png (3.7 hours)
https://d.line-scdn.net/stf/line-lp/SP_LINE_Store_en_1231231.png (4.6 hours)

line.me Mobile Resources

Total Resources17
Number of Hosts6
Static Resources12
JavaScript Resources4
CSS Resources1

line.me Mobile Resource Breakdown

line.me mobile page usability

Last tested: 2017-04-26


Mobile Usability Good
100/100

line.me Mobile Resources

Total Resources17
Number of Hosts6
Static Resources12
JavaScript Resources4
CSS Resources1

line.me Mobile Resource Breakdown

line.me similar domains

Similar domains:
www.line.com
www.line.net
www.line.org
www.line.info
www.line.biz
www.line.us
www.line.mobi
www.ine.me
www.line.me
www.pine.me
www.lpine.me
www.pline.me
www.oine.me
www.loine.me
www.oline.me
www.kine.me
www.lkine.me
www.kline.me
www.lne.me
www.lune.me
www.liune.me
www.luine.me
www.ljne.me
www.lijne.me
www.ljine.me
www.lkne.me
www.likne.me
www.lone.me
www.lione.me
www.lie.me
www.libe.me
www.linbe.me
www.libne.me
www.lihe.me
www.linhe.me
www.lihne.me
www.lije.me
www.linje.me
www.lime.me
www.linme.me
www.limne.me
www.lin.me
www.linw.me
www.linew.me
www.linwe.me
www.lins.me
www.lines.me
www.linse.me
www.lind.me
www.lined.me
www.linde.me
www.linr.me
www.liner.me
www.linre.me

line.me 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.


line.me 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.