Tokyotokyo.jp
Tokyo Tokyo Old meets New | Tokyo Tokyo Official Website
Domain Summary
What is the traffic rank for Tokyotokyo.jp?
• Tokyotokyo.jp ranks #3,039,983 globally on HypeStat.
What percent of global Internet users visit Tokyotokyo.jp?
• 8.09E-5% of global Internet users visit Tokyotokyo.jp
How many people visit Tokyotokyo.jp each day?
• Tokyotokyo.jp receives approximately 4K visitors and 5,579 page impressions per day.
Which countries does Tokyotokyo.jp receive most of its visitors from?
• Tokyotokyo.jp is mostly visited by people located in Japan,United States,Viet Nam.
How much Tokyotokyo.jp can earn?
• Tokyotokyo.jp should earn about $6.26/day from advertising revenue.
What is Tokyotokyo.jp estimated value?
• Estimated value of Tokyotokyo.jp is $5,592.14.
What IP addresses does Tokyotokyo.jp resolve to?
• Tokyotokyo.jp resolves to the IP addresses 52.69.226.227.
Where are Tokyotokyo.jp servers located in?
• Tokyotokyo.jp has servers located in Tokyo, Tokyo, 151-0053, Japan.
tokyotokyo.jp Profile

Title:Tokyo Tokyo Old meets New | Tokyo Tokyo Official Website
Description:Tokyo offers unparalleled attractions. The intersection of rich traditions and world-leading technologies, and home to diverse cultures, our city continuously creates new values for visitors.To communicate Tokyo's unique qualities and advance our reputation as the world's premier city for tourism, the Tokyo Metropolitan Government has developed a new brand strategy.
Tags:
Category:Food and Drink / Other Food and Drink
What technologies does tokyotokyo.jp use?
These are the technologies used at tokyotokyo.jp. tokyotokyo.jp has a total of 6 technologies installed in 7 different categories.tokyotokyo.jp Traffic Analysis
Tokyotokyo.jp is ranked #3,039,983 in the world. This website is viewed by an estimated 4K visitors daily, generating a total of 5.6K pageviews. This equates to about 120.9K monthly visitors. Tokyotokyo.jp traffic has increased by 106.28% compared to last month.Daily Visitors4K
26.82%
Monthly Visits120.9K
106.28%
Pages per Visit1.40
17.56%
Visit duration00:33
33.68%
Bounce Rate74.51%
11.43%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 3,990
- Monthly Visits:
- 120,897
- Pages per Visit:
- 1.40
- Daily Pageviews:
- 5,579
- Avg. visit duration:
- 00:33
- Bounce rate:
- 74.51%
- Global Reach:
- 8.09E-5%
- Monthly Visits (SEMrush):
- 251,924
- Monthly Unique Visitors (SEMrush):
- 115,346
- Monthly Visits (SimilarWeb):
- 120,924
- HypeRank:
- 3,039,983
- SEMrush Rank:
- 230,117
- SimilarWeb Rank:
- 538,834
Traffic sources
- Direct:
- 69.30%
- Referral:
- 29.46%
- Search:
- 0.93%
- Social:
- 0.31%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 5.06%
- Mobile:
- 94.94%
Total Visits Last 3 Months
93.8K
AUG
58.6K
SEP
120.9K
OCT
Visitors by country
- Country
- Users%
- Japan 68.53%
- United States 8.04%
- Viet Nam 7.71%
- Germany 3.17%
- India 2.84%
Where do visitors go on tokyotokyo.jp?
- Reach%Pageviews%PerUser
- tokyotokyo.jp
- 100.00%100.00%2
Backlinks Report ▼
Tokyotokyo.jp has a total of 1,851,454 backlinks from 1,090 referring domains and most of them comes from United States.- Total Backlinks:
- 1,851,454
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 1,090
- Referring IPs:
- 1,264
- Authority Domain Score:
- 38
Backlinks by country
- Country
- Domains
- United States 425
- Japan 186
- Korea, Republic of 112
- Singapore 68
- Italy 39
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 470
- .jp
- 134
- .kr
- 65
- .edu
- 0
- .gov
- 0
Last update was 458 days ago
This can take up to 60 seconds. Please wait...
This can take up to 60 seconds. Please wait...
*HypeStat.com is not promoting or affiliated with tokyotokyo.jp in any way. Only publicly available statistics data are displayed.
Search Engine Indexes ▼
Search engine indexes are huge databases or collections of net pages that search engines like google like google and yahoo use to retrieve applicable facts while customers carry out searches. These indexes are created through search engines like google and yahoo through crawling and indexing net pages from throughout the internet.- Bing Index:
- 856
▼
SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.- Domain:
- tokyotokyo.jp
- Rank:
(Rank based on keywords, cost and organic traffic) - 230,117
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 435
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 6,165
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $4,322.00
Revenue report ▼
Google.com would generate approximately $6.3 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $187.8 and annual gross revenue of approximately $2.3K. Based on these figures, the site's net worth is estimated at around $5.6K.How much would tokyotokyo.jp make?
- Daily Revenue:
- $6.26
- Monthly Revenue:
- $187.80
- Yearly Revenue:
- $2,284.90
Daily earning by country
- CountryPageviewsEarning
- United States 449$2.17
- Japan 3,824$1.38
- Germany 177$0.25
- Viet Nam 430$0.20
- India 158$0.06
Loss of money due to Adblock?
- Daily Revenue Loss:
- $0.53
- Monthly Revenue Loss:
- $15.85
- Yearly Revenue Loss:
- $192.83
- Daily Pageviews Blocked:
- 308
- Monthly Pageviews Blocked:
- 9,252
- Yearly Pageviews Blocked:
- 112,569
Daily revenue loss by country
- CountryBlockedLost Money
- United States 81$0.39
- Germany 51$0.07
- Japan 115$0.04
- India 44$0.02
- Viet Nam 17$0.01
How much is tokyotokyo.jp worth?
- Website Value:
- $5.6K
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- tokyotokyo.jp
- 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.) - Not reviewed
Desktop summary
- Root domain:
- tokyotokyo.jp
- 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.) - Not reviewed
Abusive Experience Report ▼
Summary of the abusive experience rating of a website.- Root domain:
- tokyotokyo.jp
- 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.) - Not reviewed
Where is tokyotokyo.jp hosted? ▼
Tokyotokyo.jp may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 52.69.226.227
- ASN:
- AS16509
- ISP:
- Amazon.com, Inc.
- Server Location:
- Tokyo
Tokyo, 13
151-0053
Japan, JP
Other sites hosted on 52.69.226.227
There are no other sites hosted on this IPHow fast does tokyotokyo.jp load? ▼
The average loading time of tokyotokyo.jp is 810 ms. The Desktop speed index is 51 and mobile speed index is 21.- Average Load Time:
- 810 ms
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.
Cumulative Layout Shift (CLS)126ms
Time To First Byte (TTFB)364ms
First Contentful Paint (FCP)1.6s
First Input Delay (FID)4ms
Interaction To Next Paint (INP)136ms
Largest Contentful Paint (LCP)2.8s
Origin Data
All pages served from this origin have an SLOW 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.
Cumulative Layout Shift (CLS)41ms
Time To First Byte (TTFB)607ms
First Contentful Paint (FCP)1.6s
First Input Delay (FID)3ms
Interaction To Next Paint (INP)139ms
Largest Contentful Paint (LCP)2.7s
Lab Data
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Total Blocking Time 190 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Speed Index 2.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
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 about performance budgets
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 about performance budgets
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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 about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Time to Interactive 4.4 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
First Meaningful Paint 2.3 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Largest Contentful Paint 4.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Page Speed (Google PageSpeed Insights) - Mobile
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.
Cumulative Layout Shift (CLS)21ms
Time To First Byte (TTFB)1.4s
First Contentful Paint (FCP)3.9s
First Input Delay (FID)20ms
Interactive To Next Paint (INP)375ms
Largest Contentful Paint (LCP)5.4s
Origin Data
All pages served from this origin have an SLOW 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.
Cumulative Layout Shift (CLS)17ms
Time To First Byte (TTFB)1.4s
First Contentful Paint (FCP)3.1s
First Input Delay (FID)82ms
Interactive To Next Paint (INP)408ms
Largest Contentful Paint (LCP)5.2s
Lab Data
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more about performance budgets
First Meaningful Paint 5.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
First Contentful Paint 4.2 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Preload Largest Contentful Paint image
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
If the LCP element is dynamically added to the page, you should preload the image in order to improve LCP. Learn more about preloading LCP elements
Largest Contentful Paint image was not lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading
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 about performance budgets
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 about performance budgets
Largest Contentful Paint 8.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Max Potential First Input Delay 690 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents . a 300 millisecond delay to user input Learn more about using the viewport meta tag
Time to Interactive 23.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Total Blocking Time 3,210 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Speed Index 14.9 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn how to preconnect to required origins
Does tokyotokyo.jp use compression? ▼
Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on tokyotokyo.jp are reduced by %.
tokyotokyo.jp does not use compression.
Original size: 63.85 KB
Compressed size: n/a
File reduced by: (%)
Compressed size: n/a
File reduced by: (%)
Google Safe Browsing ▼
Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.SSL Checker - SSL Certificate Verify ▼
An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. tokyotokyo.jp supports HTTPS. tokyotokyo.jp supports HTTPS
Verifying SSL Support. Please wait...
Common Name: www.tokyotokyo.jp
Organization:
Location:
Issuer: GlobalSign GCC R3 DV TLS CA 2020
Valid from: Jun 29 02:21:58 2023 GMT
Valid until: Jul 30 02:21:57 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Organization:
Location:
Issuer: GlobalSign GCC R3 DV TLS CA 2020
Valid from: Jun 29 02:21:58 2023 GMT
Valid until: Jul 30 02:21:57 2024 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: GlobalSign GCC R3 DV TLS CA 2020
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Jul 28 00:00:00 2020 GMT
Valid until: Mar 18 00:00:00 2029 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Jul 28 00:00:00 2020 GMT
Valid until: Mar 18 00:00:00 2029 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Verify HTTP/2 Support ▼
HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency. tokyotokyo.jp supports HTTP/2
Verifying HTTP/2.0 Support. Please wait...
Http Header ▼
HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server.date: Thu, 30 Nov 2023 13:32:54 GMT
content-type: text/html; charset=UTF-8
content-length: 65380
server: Apache
last-modified: Wed, 29 Nov 2023 04:53:40 GMT
etag: "ff64-60b43519fb539"
accept-ranges: bytes
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
DNS Lookup ▼
DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.Type | Ip | Target/Txt | TTL |
TXT | 3600 | ||
TXT | 3600 | ||
SOA | 3600 | ||
Mname | ns-67.awsdns-08.com | ||
Rname | awsdns-hostmaster.amazon.com | ||
Serial Number | 1 | ||
Refresh | 7200 | ||
Retry | 900 | ||
Expire | 1209600 | ||
Minimum TTL | 86400 | ||
A | 52.69.226.227 | 60 | |
A | 54.248.165.178 | 60 | |
NS | 86332 | ||
NS | 86332 | ||
NS | 86332 | ||
NS | 86332 |
Whois Lookup ▼
Domain WHOIS is a public database that provides information about domain names, including registered owners, contact information, domain registrars, registration and expiration dates, name servers, and other relevant information. Domain registration for this website began on February 18, 2015 and will expire on February 29, 2024 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on July 20, 2023.- Domain Created:
- 2015-02-18
- Domain Expires:
- 2024-02-29
- Domain Updated:
- 2023-07-20
- Domain Age:
- 10 years 13 days
- Domain Owner:
- (Not displayed by registrant's request)
- WhoIs:
[ JPRS database provides information on network administration. Its use is ] [ restricted to network administration purposes. For further information, ] [ use 'whois -h whois.jprs.jp help'. To suppress Japanese output, add'/e' ] [ at the end of command, e.g. 'whois -h whois.jprs.jp ***/e'. ] [ ] [ Notice -------------------------------------------------------------------- ] [ JPRS will add the [Lock Status] element to the response format of JP domain ] [ name on November 12, 2023. ] [ For further information, please see the following webpage. ] [ https://jprs.jp/whatsnew/notice/2023/231112.html (only in Japanese) ] [ --------------------------------------------------------------------------- ] Domain Information: [Domain Name] TOKYOTOKYO.JP [Registrant] (Not displayed by registrant's request) For details -> https://jprs.jp/about/dom-rule/whois-concealment/ (only in Japanese) [Name Server] ns-998.awsdns-60.net [Name Server] ns-1594.awsdns-07.co.uk [Name Server] ns-67.awsdns-08.com [Name Server] ns-1084.awsdns-07.org [Signing Key] [Created on] 2015/02/18 [Expires on] 2024/02/29 [Status] Active [Last Updated] 2023/07/20 10:59:39 (JST) Contact Information: [Name] Whois Privacy Protection Service by onamae.com [Email][Web Page] [Postal code] 150-8512 [Postal Address] Shibuya-ku 26-1 Sakuragaoka-cho Cerulean Tower 11F [Phone] +81.354562560 [Fax]