Mortartokyo.jp
MORTAR TOKYO ONLINE(モータルトーキョー)Domain Summary
What is the traffic rank for Mortartokyo.jp?
• Mortartokyo.jp ranks #1,057,656 globally on HypeStat.
What percent of global Internet users visit Mortartokyo.jp?
• 3.0E-5% of global Internet users visit Mortartokyo.jp
How many people visit Mortartokyo.jp each day?
• Mortartokyo.jp receives approximately 6.7K visitors and 13,413 page impressions per day.
How much Mortartokyo.jp can earn?
• Mortartokyo.jp should earn about $54.72/day from advertising revenue.
What is Mortartokyo.jp estimated value?
• Estimated value of Mortartokyo.jp is $50,272.15.
What IP addresses does Mortartokyo.jp resolve to?
• Mortartokyo.jp resolves to the IP addresses 52.198.169.155.
Where are Mortartokyo.jp servers located in?
• Mortartokyo.jp has servers located in Tokyo, Tokyo, 151-0053, Japan.
mortartokyo.jp Profile
Title:MORTAR TOKYO ONLINE(モータルトーキョー)
What technologies does mortartokyo.jp use?
These are the technologies used at mortartokyo.jp. mortartokyo.jp has a total of 12 technologies installed in 10 different categories.mortartokyo.jp Traffic Analysis
Mortartokyo.jp is ranked #1,057,656 in the world. This website is viewed by an estimated 6.7K visitors daily, generating a total of 13.4K pageviews. This equates to about 203.2K monthly visitors.Daily Visitors6.7K
Monthly Visits203.2K
Pages per Visit2.00
Visit duration02:52
Bounce Rate37.61%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 6,706
- Monthly Visits:
- 203,192
- Pages per Visit:
- 2.00
- Daily Pageviews:
- 13,413
- Avg. visit duration:
- 02:52
- Bounce rate:
- 37.61%
- Global Reach:
- 3.0E-5%
- Monthly Visits (SEMrush):
- 195,332
- Monthly Unique Visitors (SEMrush):
- 37,282
- HypeRank:
- 1,057,656
- SEMrush Rank:
- 8,710,765
Traffic sources
- Direct:
- 50.39%
- Referral:
- 49.37%
- Search:
- 0.24%
- Social:
- 0%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 40.94%
- Mobile:
- 59.06%
Backlinks Report ▼
Mortartokyo.jp has a total of 277 backlinks from 67 referring domains and most of them comes from Singapore.- Total Backlinks:
- 277
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 67
- Referring IPs:
- 47
- Authority Domain Score:
- 10
Backlinks by country
- Country
- Domains
- Singapore 38
- Japan 13
- United States 7
- Finland 2
- Turkey 1
Backlinks by TLDs
- TLD Distribution
- Domains
- .in
- 37
- .com
- 18
- .jp
- 4
- .edu
- 0
- .gov
- 0
Last update was 901 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 mortartokyo.jp in any way. Only publicly available statistics data are displayed.
▼
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:
- mortartokyo.jp
- Rank:
(Rank based on keywords, cost and organic traffic) - 8,710,765
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 104
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 7
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $1.00
Revenue report ▼
Google.com would generate approximately $54.7 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $1.6K and annual gross revenue of approximately $20K. Based on these figures, the site's net worth is estimated at around $50.3K.How much would mortartokyo.jp make?
- Daily Revenue:
- $54.72
- Monthly Revenue:
- $1,641.60
- Yearly Revenue:
- $19,972.80
How much is mortartokyo.jp worth?
- Website Value:
- $50.3K
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- mortartokyo.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:
- mortartokyo.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:
- mortartokyo.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 mortartokyo.jp hosted? ▼
Mortartokyo.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.198.169.155
- ASN:
- AS16509
- ISP:
- Amazon.com, Inc.
- Server Location:
- Tokyo
Tokyo, 13
151-0053
Japan, JP
Other sites hosted on 52.198.169.155
There are no other sites hosted on this IPHow fast does mortartokyo.jp load? ▼
The average loading time of mortartokyo.jp is n/a ms. The Desktop speed index is 91 and mobile speed index is 52.- Average Load Time:
- n/a ms
Page Speed (Google PageSpeed Insights) - Desktop
Field Data
Over the last 30 days, the field data shows that this page has a FAST 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)1ms
Time To First Byte (TTFB)203ms
First Contentful Paint (FCP)625ms
First Input Delay (FID)2ms
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)924ms
Origin Data
All pages served from this origin have an FAST 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)1ms
Time To First Byte (TTFB)409ms
First Contentful Paint (FCP)573ms
First Input Delay (FID)2ms
Interaction To Next Paint (INP)0
Largest Contentful Paint (LCP)782ms
Lab Data
Largest Contentful Paint 1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Largest Contentful Paint marks the time at which the largest text or image is painted. 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
Speed Index 1.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
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
Time to Interactive 1.3 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
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
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
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 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
First Contentful Paint 1.1 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
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 30 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
Avoids `unload` event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. 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
Page Speed (Google PageSpeed Insights) - Mobile
Field Data
Over the last 30 days, the field data shows that this page has a FAST 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)1ms
Time To First Byte (TTFB)376ms
First Contentful Paint (FCP)1.1s
First Input Delay (FID)12ms
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)1.7s
Origin Data
All pages served from this origin have an FAST 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)0ms
Time To First Byte (TTFB)545ms
First Contentful Paint (FCP)896ms
First Input Delay (FID)12ms
Interactive To Next Paint (INP)0
Largest Contentful Paint (LCP)1.3s
Lab Data
Lazy load third-party resources with facades
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more
First Contentful Paint 5.8 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
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
Time to Interactive 7.5 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
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
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
Speed Index 8.5 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) 12298 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
Largest Contentful Paint 7.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more
First Meaningful Paint 5.8 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
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 170 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
Avoids `unload` event listeners
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Use `pagehide` or `visibilitychange` events instead. Learn more
Total Blocking Time 100 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
Does mortartokyo.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 mortartokyo.jp are reduced by 79%.
mortartokyo.jp use gzip compression.
Original size: 34.97 KB
Compressed size: 7.28 KB
File reduced by: 27.69 KB (79%)
Compressed size: 7.28 KB
File reduced by: 27.69 KB (79%)
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. mortartokyo.jp supports HTTPS. mortartokyo.jp supports HTTPS
Verifying SSL Support. Please wait...
Common Name: *.mortartokyo.jp
Organization:
Location:
Issuer: Amazon
Valid from: Jan 11 00:00:00 2022 GMT
Valid until: Feb 9 23:59:59 2023 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Organization:
Location:
Issuer: Amazon
Valid from: Jan 11 00:00:00 2022 GMT
Valid until: Feb 9 23:59:59 2023 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: Amazon
Organization: Amazon, OU = Server CA 1B
Location: US
Issuer: Amazon Root CA 1
Valid from: Oct 22 00:00:00 2015 GMT
Valid until: Oct 19 00:00:00 2025 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: Amazon, OU = Server CA 1B
Location: US
Issuer: Amazon Root CA 1
Valid from: Oct 22 00:00:00 2015 GMT
Valid until: Oct 19 00:00:00 2025 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: Amazon Root CA 1
Organization: Amazon
Location: US
Issuer: Starfield Services Root Certificate Authority - G2
Valid from: May 25 12:00:00 2015 GMT
Valid until: Dec 31 01:00:00 2037 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: Amazon
Location: US
Issuer: Starfield Services Root Certificate Authority - G2
Valid from: May 25 12:00:00 2015 GMT
Valid until: Dec 31 01:00:00 2037 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: Starfield Services Root Certificate Authority - G2
Organization: "Starfield Technologies, Inc."
Location: Scottsdale, Arizona, US
Issuer:
Valid from: Sep 2 00:00:00 2009 GMT
Valid until: Jun 28 17:39:16 2034 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Organization: "Starfield Technologies, Inc."
Location: Scottsdale, Arizona, US
Issuer:
Valid from: Sep 2 00:00:00 2009 GMT
Valid until: Jun 28 17:39:16 2034 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. mortartokyo.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: Mon, 27 Jun 2022 12:38:04 GMT
content-type: text/html; charset=UTF-8
set-cookie: AWSALB=HuzfzJe20cIuzW8c9q3LxdB3D+/NChaI1PbzwTH3isBYbx2GntV9T0pnAMBXMdO78rESSCS+LC5fS/B8bdsuSHnnwJHusBj90Q5B2WCtnaPXYQtMHwIcX50NIsrE; Expires=Mon, 04 Jul 2022 12:38:04 GMT; Path=/
set-cookie: AWSALBCORS=HuzfzJe20cIuzW8c9q3LxdB3D+/NChaI1PbzwTH3isBYbx2GntV9T0pnAMBXMdO78rESSCS+LC5fS/B8bdsuSHnnwJHusBj90Q5B2WCtnaPXYQtMHwIcX50NIsrE; Expires=Mon, 04 Jul 2022 12:38:04 GMT; Path=/; SameSite=None; Secure
server: nginx/1.20.0
x-powered-by: PHP/7.4.29
set-cookie: ECSESSID=oo70k28rtskjdevgpldqu7egpv; path=/; secure; HttpOnly; SameSite=None
set-cookie: legacy-ECSESSID=oo70k28rtskjdevgpldqu7egpv; path=/; secure; HttpOnly
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
vary: User-Agent
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
referrer-policy: no-referrer-when-downgrade
content-security-policy: default-src 'self' http: https: data: blob: 'unsafe-inline'
strict-transport-security: max-age=63072000; includeSubDomains;preload
content-encoding: gzip
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 | 243 | ||
MX | 243 | ||
MX | 243 | ||
SOA | 843 | ||
Mname | ns-1048.awsdns-03.org | ||
Rname | awsdns-hostmaster.amazon.com | ||
Serial Number | 1 | ||
Refresh | 7200 | ||
Retry | 900 | ||
Expire | 1209600 | ||
Minimum TTL | 86400 | ||
NS | 3539 | ||
NS | 3539 | ||
NS | 3539 | ||
NS | 3539 |
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 December 2, 2021 and will expire on December 31, 2022 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on December 5, 2021.- Domain Created:
- 2021-12-02
- Domain Expires:
- 2022-12-31
- Domain Updated:
- 2021-12-05
- Domain Age:
- 3 years 12 days
- Domain Owner:
- Nojiri Motoya
- 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'. ] Domain Information: [Domain Name] MORTARTOKYO.JP [Registrant] Nojiri Motoya [Name Server] ns-1048.awsdns-03.org [Name Server] ns-2042.awsdns-63.co.uk [Name Server] ns-484.awsdns-60.com [Name Server] ns-555.awsdns-05.net [Signing Key] [Created on] 2021/12/02 [Expires on] 2022/12/31 [Status] Active [Last Updated] 2021/12/05 14:34:48 (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]