Naver.jp - Line.naver.jp
Domain Summary
What is the traffic rank for Line.naver.jp?
• Line.naver.jp ranks 2,099 globally on Alexa.
What percent of global Internet users visit Line.naver.jp?
• 0.035% of global Internet users visit Line.naver.jp
How many people visit Line.naver.jp each day?
• Line.naver.jp receives approximately 1.6M visitors and 2,381,531 page impressions per day.
Which countries does Line.naver.jp receive most of its visitors from?
• Line.naver.jp is mostly visited by people located in Japan,Taiwan,United States.
How much Line.naver.jp can earn?
• Line.naver.jp should earn about $7,478.13/day from advertising revenue.
What is Line.naver.jp estimated value?
• Estimated value of Line.naver.jp is $5,459,036.25.
What IP addresses does Line.naver.jp resolve to?
• Line.naver.jp resolves to the IP addresses 203.104.129.195.
Where are Line.naver.jp servers located in?
• Line.naver.jp has servers located in Shinjuku, Tokyo, 160-0023, Japan.
About - line.naver.jp
通話やテキストチャット、動画送受信の可能なインスタントメッセンジャー。機能、オリジナルスタンプ紹介。
LINE is a new communication app which allows you to make FREE voice calls and send FREE messages whenever and wherever you are, 24 hours a day! Edit Site Info
LINE is a new communication app which allows you to make FREE voice calls and send FREE messages whenever and wherever you are, 24 hours a day! Edit Site Info
What technologies does line.naver.jp use?
line.naver.jp Profile
Title: LINE : Free Calls & Messages
Keywords: Japan, Messenger, Talk, LINE, text, message, sms, call, phone, free, voip
Keywords: Japan, Messenger, Talk, LINE, text, message, sms, call, phone, free, voip
Last update was 139 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not linking to, promoting or affiliated with naver.jp in any way. Only publicly available statistics data are displayed.
line.naver.jp Traffic Summary
1.6M daily visitors
Is this your site?
Verify your site's metrics.
Verify your site's metrics.
- Daily Unique Visitors:
- 1,587,687
- Monthly Visits:
- 50,012,141
- Pages per Visitor:
- 1.50
- Daily Pageviews:
- 2,381,531
- Alexa Rank:
- 2,099 visit alexa
- Alexa Reach:
- 0.035% (of global internet users)
- Avg. visit duration:
- 05:26
- Bounce rate:
- 53.49%
Traffic sources
- Direct:
- 14.50%
- Referral:
- 1.19%
- Search:
- 82.88%
- Social:
- 1.20%
- Paid:
- 0.04%
Visitors by country
- Users%Pageviews%Rank
- Japan 96.1%95.8%177
- Taiwan 1.1%0.9%3685
- United States 0.6%0.5%83291
Where do visitors go on line.naver.jp?
- Reach%Pageviews%PerUser
- matome.naver.jp
- 97.94%95.79%1.4
- line.naver.jp
- 2.01%2.90%2
- imgcc.naver.jp
- 1.33%0.96%1
- play.naver.jp
- 0.05%0.15%4
- OTHER
- 0%0.20%0
Competitive Data
- Domain:
- line.naver.jp
- Rank:
(Rank based on keywords, cost and organic traffic) - 12,846
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 198,042
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 190,910
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $3,700.00
- Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results) - 0
- Adwords Traffic:
(Number of visitors brought to the website via paid search results) - 0
- Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation) - $0.00
Backlinks Report
- Total Sites Linking In (Alexa):
- 16,771
- Total Backlinks:
- 203,874,518
- Follow Links:
- 187,257,128
- Nofollow Links:
- 16,617,353
- Referring Domains:
- 91,263
- Referring IPs:
- 103,355
- Authority Domain Score:
- 58
Backlinks by country
- Domains
- United States 42,206
- Japan 20,214
- Canada 3,025
- Taiwan 2,272
- Singapore 643
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 23,899
- .jp
- 7,307
- .tw
- 6,071
- .edu
- 5
- .gov
- 0
+ Moz Data
- Domain Authority:
- 93
- Page Authority:
- 62
- MozRank:
- 6
+ How much would line.naver.jp make?
- Daily Revenue:
- $7,478.13
- Monthly Revenue:
- $224,343.90
- Yearly Revenue:
- $2,729,517.45
Daily earning by country
- PageviewsEarning
- Japan 2,281,507$7,300.82
- United States 11,908$136.58
- Taiwan 21,434$40.72
How much money does line.naver.jp lose due to Adblock?
- Daily Revenue Loss:
- $250.13
- Monthly Revenue Loss:
- $7,503.75
- Yearly Revenue Loss:
- $91,295.65
- Daily Pageviews Blocked:
- 74,018
- Monthly Pageviews Blocked:
- 2,220,540
- Yearly Pageviews Blocked:
- 27,016,564
Daily revenue loss by country
- BlockedLost Money
- Japan 68,445$219.02
- United States 2,143$24.58
- Taiwan 3,429$6.52
How much is line.naver.jp worth?
- Website Value:
- $5,459,036.25
+ Ad Experience Report
Summary of the ad experience rating of a site for a specific platform.
Desktop summary
- Root domain:
- naver.jp
- Last Change Time:
(The last time that the site changed status.) - 2020-02-12 05:46:33
- Region:
(The Ad Standard region to which this site has been assigned.) - C
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Passing
Mobile summary
- Last Change Time:
(The last time that the site changed status.) - 2020-02-12 05:46:33
- Region:
(The Ad Standard region to which this site has been assigned.) - C
- Ad filtering:
(Chrome is not filtering ads on your site.) - Off
- Status:
(The status of the site that is reviewed for the Better Ads Standards.) - Passing
+ Abusive Experience Report
- Root domain:
- naver.jp
- Last Change Time:
(The last time that the site changed status.) - 2020-02-12 05:46:33
- Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.) - Off
- Status:
(The status of the site reviewed for the abusive experiences.) - Passing
+ Where is line.naver.jp hosted?
- Server IP:
- 203.104.129.195
- ASN:
- AS38631
- ISP:
- LINE Corporation
- Server Location:
- Shinjuku
Tokyo, 13
160-0023
Japan, JP
Other sites hosted on 203.104.129.195
+ How fast does line.naver.jp load?
- Average Load Time:
- (1393 ms) 61 % of sites are slower
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a SLOW speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
First Contentful Paint (FCP)1.9s
First Input Delay (FID)3ms
Origin Data
All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
First Contentful Paint (FCP)1.5s
First Input Delay (FID)2ms
Lab Data
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First CPU Idle 0.9 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Timing budget
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.
Time to Interactive 0.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Largest Contentful Paint 1.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn More](https://web.dev/lighthouse-largest-contentful-paint)
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn More](https://web.dev/lighthouse-largest-contentful-paint)
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.
First Contentful Paint (FCP)1.9s
First Input Delay (FID)13ms
Origin Data
All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.
First Contentful Paint (FCP)2.8s
First Input Delay (FID)23ms
Lab Data
Largest Contentful Paint 6.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn More](https://web.dev/lighthouse-largest-contentful-paint/)
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn More](https://web.dev/lighthouse-largest-contentful-paint/)
First Contentful Paint 2.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Time to Interactive 3.1 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy. Learn more.
First CPU Idle 3.0 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
Timing budget
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.
Set a timing budget to help you keep an eye on the performance of your site. Performant sites load fast and respond to user input events quickly. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more.
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more.
First Meaningful Paint 2.5 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Speed Index 5.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First Contentful Paint (3G) 4920 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
+ Does line.naver.jp use compression?
line.naver.jp does not use compression.
Original size: 14.35 KB
Compressed size: n/a
File reduced by: n/a
Compressed size: n/a
File reduced by: n/a
+ Google Safe Browsing
+ SSL Checker - SSL Certificate Verify
line.naver.jp does not support HTTPS
Verifying SSL Support. Please wait...
+ Verify HTTP/2 Support
line.naver.jp does not support HTTP/2
Verifying HTTP/2.0 Support. Please wait...
+ Site Categories (dmoz)
- インターネット/チャット
+ Http Header
Server: nginx
Date: Fri, 09 Oct 2020 09:06:17 GMT
Content-Type: text/html
Content-Length: 178
Connection: keep-alive
Location: http://line.me/
HTTP/1.1 302 Found
Server: nginx
Date: Fri, 09 Oct 2020 09:06:17 GMT
Content-Type: text/html; charset=iso-8859-1
Content-Length: 203
Connection: keep-alive
Location: https://line.me/en/
HTTP/1.1 200 OK
Server: nginx
Date: Fri, 09 Oct 2020 09:06:18 GMT
Content-Type: text/html; charset=UTF-8
Content-Length: 14692
Connection: keep-alive
Cache-Control: private
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
Set-Cookie: ldsuid=4aee441ad9ada89f5bb32fbe99052ff5; path=/; expires=Thu, 07-Jan-21 09:06:18 GMT
+ DNS Lookup
| Type | Ip | Target | TTL |
| A | 203.104.129.195 | 60 |