Yahoo.co.jp - Info 
Domain Summary
What is the traffic rank for Yahoo.co.jp?
• Yahoo.co.jp ranks 33 globally on Alexa.
What percent of global Internet users visit Yahoo.co.jp?
• 1.29% of global Internet users visit Yahoo.co.jp
How many people visit Yahoo.co.jp each day?
• Yahoo.co.jp receives approximately 63.6M visitors and 566,004,826 page impressions per day.
Which countries does Yahoo.co.jp receive most of its visitors from?
• Yahoo.co.jp is mostly visited by people located in Japan,United States,Korea, Republic of.
How much Yahoo.co.jp can earn?
• Yahoo.co.jp should earn about $1,884,926.25/day from advertising revenue.
What is Yahoo.co.jp estimated value?
• Estimated value of Yahoo.co.jp is $1,376,003,030.94.
What IP addresses does Yahoo.co.jp resolve to?
• Yahoo.co.jp resolves to the IP addresses 182.22.16.251.
Where are Yahoo.co.jp servers located in?
• Yahoo.co.jp has servers located in Tokyo, Tokyo, 102-0082, Japan.
About - yahoo.co.jp

日本最大級のポータルサイト。検索、オークション、ニュース、メール、コミュニティ、ショッピング、など80以上のサービスを展開。あなたの生活をより豊かにする「ライフ・エンジン」を目指していきます。 Edit Site Info
What technologies does yahoo.co.jp use?
yahoo.co.jp Profile
Title: ページが表示できません - Yahoo! JAPAN
Description: Japanese version of popular portal site.
Description: Japanese version of popular portal site.
Last update was 29 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 yahoo.co.jp in any way. Only publicly available statistics data are displayed.
yahoo.co.jp Traffic Summary
63.6M daily visitors
Is this your site?
Verify your site's metrics.
Verify your site's metrics.
- Daily Unique Visitors:
- 63,596,048
- Monthly Visits:
- 2,003,275,512
- Pages per Visitor:
- 8.90
- Daily Pageviews:
- 566,004,826
- Monthly Visits (SEMrush):
- 1,234,630,741
- Monthly Unique Visitors (SEMrush):
- 60,305,718
- Monthly Visits (SimilarWeb):
- 2,262,065,489
- Alexa Rank:
- 33
- Alexa Reach:
- 1.29% (of global internet users)
- Avg. visit duration:
- 13:51
- Bounce rate:
- 29.48%
Traffic sources
- Direct:
- 39.35%
- Referral:
- 49.84%
- Search:
- 8.32%
- Social:
- 2.43%
- Paid:
- 0.06%
Desktop vs Mobile
- Desktop:
- 5.57%
- Mobile:
- 94.43%
Visitors by country
- Users%Pageviews%Rank
- Japan 92.5%95.0%3
- United States 3.5%2.1%252
- Korea, Republic of 2.3%1.8%55
- Taiwan 0.6%0.4%138
Where do visitors go on yahoo.co.jp?
- Reach%Pageviews%PerUser
- yahoo.co.jp
- 45.76%5.27%1.00
- news.yahoo.co.jp
- 40.64%30.81%6.61
- search.yahoo.co.jp
- 20.93%4.90%2.04
- auctions.yahoo.co.jp
- 19.33%18.46%8.32
- login.yahoo.co.jp
- 15.68%2.23%1.2
- mail.yahoo.co.jp
- 15.38%8.22%4.66
- chiebukuro.yahoo.co.jp
- 13.56%3.55%2.28
- shopping.yahoo.co.jp
- 13.14%7.14%4.74
- finance.yahoo.co.jp
- 8.19%2.43%2.6
- weather.yahoo.co.jp
- 3.65%0.84%2.0
- paypaymall.yahoo.co.jp
- 2.77%0.73%2.3
- sports.yahoo.co.jp
- 2.74%0.54%1.7
- store.yahoo.co.jp
- 2.56%3.84%13
- article.yahoo.co.jp
- 2.29%0.37%1.4
- business.yahoo.co.jp
- 1.83%1.06%5.0
- premium.yahoo.co.jp
- 1.71%0.22%1.1
- gyao.yahoo.co.jp
- 1.70%0.67%3.4
- bizmanager.yahoo.co.jp
- 1.66%0.21%1.1
- realestate.yahoo.co.jp
- 1.31%0.38%2.5
- tv.yahoo.co.jp
- 1.30%0.24%1.6
- transit.yahoo.co.jp
- 1.23%0.28%2.0
- paypayfleamarket.yahoo.co.jp
- 1.22%0.63%4.5
- headlines.yahoo.co.jp
- 1.11%0.13%1.0
- baseball.yahoo.co.jp
- 1.09%0.24%1.9
- edit.yahoo.co.jp
- 1.06%0.16%1.3
- card.yahoo.co.jp
- 0.95%0.30%2.8
- accounts.yahoo.co.jp
- 0.88%0.12%1.2
- map.yahoo.co.jp
- 0.83%0.13%1.4
- fortune.yahoo.co.jp
- 0.80%0.12%1.3
- toku.yahoo.co.jp
- 0.79%0.13%1.4
- soccer.yahoo.co.jp
- 0.78%0.35%3.9
- wallet.yahoo.co.jp
- 0.70%0.12%1.5
- takarabako.yahoo.co.jp
- 0.69%0.08%1.0
- loco.yahoo.co.jp
- 0.65%0.18%2.3
- kantanpay.yahoo.co.jp
- 0.63%0.07%1.0
- ebookjapan.yahoo.co.jp
- 0.62%0.33%4.7
- travel.yahoo.co.jp
- 0.56%0.19%3.0
- ads.yahoo.co.jp
- 0.54%0.42%6.7
- about.yahoo.co.jp
- 0.50%0.07%1.2
- points.yahoo.co.jp
- 0.48%0.06%1.1
- store-info.yahoo.co.jp
- 0.48%0.19%3.4
- profile.yahoo.co.jp
- 0.46%0.16%3.0
- carview.yahoo.co.jp
- 0.45%0.10%2.0
- creators.yahoo.co.jp
- 0.40%0.06%1.2
- lohaco.yahoo.co.jp
- 0.35%0.11%2.6
- typhoon.yahoo.co.jp
- 0.34%0.06%1.6
- jobcatalog.yahoo.co.jp
- 0.28%0.05%1.6
- movies.yahoo.co.jp
- 0.28%0.14%4.3
- console-news.yahoo.co.jp
- 0.27%0.11%3.6
- ops.yahoo.co.jp
- 0.13%0.39%26
- ynwp.yahoo.co.jp
- 0.13%0.13%8.6
- ynwl.yahoo.co.jp
- 0.07%0.07%8
- OTHER
- 0%2.20%0
Competitive Data
- Domain:
- yahoo.co.jp
- Rank:
(Rank based on keywords, cost and organic traffic) - 1,847
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 1,451,542
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 2,224,867
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $740,227.00
- Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results) - 6
- Adwords Traffic:
(Number of visitors brought to the website via paid search results) - 2
- 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):
- 98,405
- Total Backlinks:
- 44,751,978
- Follow Links:
- 35,014,341
- Nofollow Links:
- 9,737,636
- Referring Domains:
- 7,426
- Referring IPs:
- 6,080
- Authority Domain Score:
- 0
Backlinks by country
- Domains
- Japan 4,001
- United States 2,247
- Singapore 157
- Ireland 128
- Germany 113
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 4,165
- .jp
- 1,257
- .net
- 751
- .edu
- 7
- .gov
- 0
Search Engine Indexes
- Google Index:
- 99,200,000
- Bing Index:
- 211,000,000
- Yahoo Index:
- 387,000,000
- Yandex Index:
- 3,070
- Baidu Index:
- 14,940
+ Moz Data
- Domain Authority:
- 93
- Page Authority:
- 74
- MozRank:
- 7
+ How much would yahoo.co.jp make?
- Daily Revenue:
- $1,884,926.25
- Monthly Revenue:
- $56,547,787.50
- Yearly Revenue:
- $687,998,081.25
Daily earning by country
- PageviewsEarning
- Japan 537,704,585$1,720,654.67
- United States 11,886,101$136,333.58
- Korea, Republic of 10,188,087$23,636.36
- Taiwan 2,264,019$4,301.64
How much money does yahoo.co.jp lose due to Adblock?
- Daily Revenue Loss:
- $77,793.40
- Monthly Revenue Loss:
- $2,333,802.04
- Yearly Revenue Loss:
- $28,394,591.47
- Daily Pageviews Blocked:
- 19,040,402
- Monthly Pageviews Blocked:
- 571,212,070
- Yearly Pageviews Blocked:
- 6,949,746,857
Daily revenue loss by country
- BlockedLost Money
- Japan 16,131,138$51,619.64
- United States 2,139,498$24,540.04
- Korea, Republic of 407,523$945.45
- Taiwan 362,243$688.26
How much is yahoo.co.jp worth?
- Website Value:
- $1,376,003,030.94
+ Ad Experience Report
Summary of the ad experience rating of a site for a specific platform.
Desktop summary
- Root domain:
- yahoo.co.jp
- Last Change Time:
(The last time that the site changed status.) - 2021-11-10 04:38:53
- 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.) - 2021-11-10 04:38:53
- 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:
- yahoo.co.jp
- Last Change Time:
(The last time that the site changed status.) - 2021-11-10 04:38:53
- 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 yahoo.co.jp hosted?
- Server IP:
- 182.22.16.251
- ASN:
- AS23816
- ISP:
- Yahoo Japan Corporation
- Server Location:
- Tokyo
Tokyo, 13
102-0082
Japan, JP
Other sites hosted on 182.22.16.251
+ How fast does yahoo.co.jp load?
- Average Load Time:
- (1468 ms) 54 % 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 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.4s
First Input Delay (FID)4ms
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.4s
First Input Delay (FID)4ms
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.
Speed Index 2.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.
Largest Contentful Paint 1.8 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/)
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.
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.
Total Blocking Time 50 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 1.3 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.
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn more.
Animations which are not composited can be janky and increase CLS. 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.
Estimated Input Latency 20 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.
Max Potential First Input Delay 120 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 2.4 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.
First CPU Idle 2.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.
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.6s
First Input Delay (FID)76ms
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.6s
First Input Delay (FID)79ms
Lab Data
Speed Index 10.1 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 CPU Idle 11.2 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.
Time to Interactive 13.7 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.
Total Blocking Time 1,660 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.
Estimated Input Latency 300 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.
Avoid non-composited animations
Animations which are not composited can be janky and increase CLS. Learn more.
Animations which are not composited can be janky and increase CLS. Learn more.
Largest Contentful Paint 6.5 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 6.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.
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 Meaningful Paint 6.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.
First Contentful Paint (3G) 15750 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.
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.
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.
Max Potential First Input Delay 790 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.
+ Does yahoo.co.jp use compression?
yahoo.co.jp does not use compression.
Original size: 6.59 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
yahoo.co.jp supports HTTPS

Verifying SSL Support. Please wait...
Common Name: edge01.yahoo.co.jp
Organization: Yahoo Japan Corporation
Location: Chiyoda-ku, Tokyo, JP
Issuer: Cybertrust Japan SureServer CA G4
Valid from: Apr 6 10:01:27 2022 GMT
Valid until: May 5 14:59:00 2023 GMT
Authority: Is not a CA
Keysize:
Organization: Yahoo Japan Corporation
Location: Chiyoda-ku, Tokyo, JP
Issuer: Cybertrust Japan SureServer CA G4
Valid from: Apr 6 10:01:27 2022 GMT
Valid until: May 5 14:59:00 2023 GMT
Authority: Is not a CA
Keysize:
Common Name: Cybertrust Japan SureServer CA G4
Organization: Cybertrust Japan Co., Ltd.
Location: JP
Issuer:
Valid from: Sep 27 01:54:23 2019 GMT
Valid until: May 29 05:00:39 2029 GMT
Authority: Is a CA
Keysize: 2048 Bits
Organization: Cybertrust Japan Co., Ltd.
Location: JP
Issuer:
Valid from: Sep 27 01:54:23 2019 GMT
Valid until: May 29 05:00:39 2029 GMT
Authority: Is a CA
Keysize: 2048 Bits
Common Name:
Organization: SECOM Trust Systems CO.,LTD., OU=Security Communication RootC
Location: JP
Issuer:
Valid from: Mar 24 02:22:35 2015 GMT
Valid until: Sep 29 02:22:35 2023 GMT
Authority: Is a CA
Keysize: 2048 Bits
Organization: SECOM Trust Systems CO.,LTD., OU=Security Communication RootC
Location: JP
Issuer:
Valid from: Mar 24 02:22:35 2015 GMT
Valid until: Sep 29 02:22:35 2023 GMT
Authority: Is a CA
Keysize: 2048 Bits
+ Verify HTTP/2 Support
yahoo.co.jp supports HTTP/2

Verifying HTTP/2.0 Support. Please wait...
+ Site Categories (dmoz)
- ウェブ上の情報/ポータル
+ Http Header
Date: Sat, 30 Apr 2022 03:54:01 GMT
Connection: close
Server: ATS
Cache-Control: no-store
Content-Type: text/html
Content-Language: en
Content-Length: 6744
+ DNS Lookup
Type | Ip | Target | TTL |
TXT | 899 | ||
TXT | 899 | ||
MX | mx2.mail.yahoo.co.jp | 899 | |
MX | mx1.mail.yahoo.co.jp | 899 | |
MX | mx5.mail.yahoo.co.jp | 899 | |
MX | mx3.mail.yahoo.co.jp | 899 | |
CAA | 899 | ||
CAA | 899 | ||
CAA | 899 | ||
CAA | 899 | ||
SOA | 899 | ||
Mname | yahoo.co.jp | ||
Rname | postmaster.yahoo.co.jp | ||
Serial Number | 2204280030 | ||
Refresh | 1800 | ||
Retry | 900 | ||
Expire | 86400 | ||
Minimum TTL | 0 | ||
A | 183.79.250.251 | 295 | |
A | 182.22.28.252 | 295 | |
A | 183.79.217.124 | 295 | |
A | 183.79.250.123 | 295 | |
A | 183.79.219.252 | 295 | |
A | 182.22.16.251 | 295 | |
A | 182.22.25.124 | 295 | |
A | 182.22.25.252 | 295 | |
NS | ns12.yahoo.co.jp | 899 | |
NS | ns11.yahoo.co.jp | 899 | |
NS | ns01.yahoo.co.jp | 899 | |
NS | ns02.yahoo.co.jp | 899 |
+ Whois Lookup
- WhoIs:
+ How is socially engaged yahoo.co.jp?