food-tokyo.jp Food-tokyo.jp

   
トップページ - FOOD and MUSCLE｜食品と筋トレの専門サイト

Domain Summary

What is the traffic rank for Food-tokyo.jp?

• Food-tokyo.jp ranks #3,322,412 globally on HypeStat.

What percent of global Internet users visit Food-tokyo.jp?

• 6.0E-6% of global Internet users visit Food-tokyo.jp

How many people visit Food-tokyo.jp each day?

• Food-tokyo.jp receives approximately 11.4K visitors and 13,609 page impressions per day.

Which countries does Food-tokyo.jp receive most of its visitors from?

• Food-tokyo.jp is mostly visited by people located in Japan.

How much Food-tokyo.jp can earn?

• Food-tokyo.jp should earn about $4.90/day from advertising revenue.

What is Food-tokyo.jp estimated value?

• Estimated value of Food-tokyo.jp is $4,302.54.

What IP addresses does Food-tokyo.jp resolve to?

• Food-tokyo.jp resolves to the IP addresses 216.239.32.21.

Where are Food-tokyo.jp servers located in?

• Food-tokyo.jp has servers located in California, United States.

food-tokyo.jp Profile

Title: トップページ - FOOD and MUSCLE｜食品と筋トレの専門サイト
Description:各種食品技術研究の紹介。研究内容・技術開発や委託業務の案内。
Tags:
Edit Site Info

What technologies does food-tokyo.jp use?

These are the technologies used at food-tokyo.jp. food-tokyo.jp has a total of 8 technologies installed in 6 different categories.
Blogs
Blogger Blogger
Advertising
Google AdSense Google AdSense
CDN
Google Hosted Libraries Google Hosted Libraries
JavaScript Libraries
jQuery jQuery
Underscore.js Underscore.js
Web Servers
OpenGSE OpenGSE
Programming Languages
Python Python
Java Java

food-tokyo.jp Traffic Analysis

Food-tokyo.jp is ranked #3,322,412 in the world. This website is viewed by an estimated 11.4K visitors daily, generating a total of 13.6K pageviews. This equates to about 344.5K monthly visitors. Food-tokyo.jp traffic has increased by 293.22% compared to last month.
Daily Visitors11.4K
293.22%
Monthly Visits344.5K
293.22%
Pages per Visit1.20
Visit duration00:19
Bounce Rate86.97%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
11,368
Monthly Visits:
344,450
Pages per Visit:
1.20
Daily Pageviews:
13,609
Avg. visit duration:
00:19
Bounce rate:
86.97%
Global Reach:
6.0E-6%
Monthly Visits (SEMrush):
39,141
Monthly Unique Visitors (SEMrush):
39,141
Monthly Visits (SimilarWeb):
337,667
HypeRank:
3,322,412
SEMrush Rank:
7,504,789
SimilarWeb Rank:
288,546
*All traffic values are estimates only.

Traffic sources

Direct:
0%
Referral:
0%
Search:
100.00%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
0%
Mobile:
100.00%

Total Visits Last 3 Months

388
JUL
87.6K
AUG
344.5K
SEP

Visitors by country

Country
Users%
 
Japan 100.00%
Last update was 877 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with food-tokyo.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.
SemRushSemRush
Domain:
  food-tokyo.jp
Rank:
(Rank based on keywords, cost and organic traffic)
  7,504,789
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  64
Organic Traffic:
(Number of visitors coming from top 20 search results)
  10
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Full SEMrush Report >>

Revenue report ▼

Google.com would generate approximately $4.9 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $147 and annual gross revenue of approximately $1.8K. Based on these figures, the site's net worth is estimated at around $4.3K.

How much would food-tokyo.jp make?

Daily Revenue:
$4.90
Monthly Revenue:
$147.00
Yearly Revenue:
$1,788.50
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Japan 13,609$4.90

Loss of money due to Adblock?

Daily Revenue Loss:
$0.15
Monthly Revenue Loss:
$4.41
Yearly Revenue Loss:
$53.65
Daily Pageviews Blocked:
408
Monthly Pageviews Blocked:
12,248
Yearly Pageviews Blocked:
149,019

Daily revenue loss by country

 
CountryBlockedLost Money
 
Japan 408$0.15

How much is food-tokyo.jp worth?

Website Value:
$4.3K

Ad Experience Report ▼

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
food-tokyo.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:
food-tokyo.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:
food-tokyo.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 food-tokyo.jp hosted? ▼

Food-tokyo.jp may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
216.239.32.21
ASN:
AS15169 
ISP:
Google LLC 
Server Location:
California, CA
United States, US
 

Other sites hosted on 216.239.32.21

How fast does food-tokyo.jp load? ▼

The average loading time of food-tokyo.jp is n/a ms. The Desktop speed index is 89 and mobile speed index is 44.
Average Load Time:
n/a ms

Page Speed (Google PageSpeed Insights) - Desktop

89
0-49 50-89 90-100 i

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.

Cumulative Layout Shift (CLS)15ms 64% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 64% 22% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 22% 12% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 12%
Time To First Byte (TTFB)676ms 82% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 82% 15% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 15% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.4s 82% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 82% 13% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 13% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)2ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 1% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.8s 88% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 88% 9% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 9% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

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.

Cumulative Layout Shift (CLS)15ms 64% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 64% 22% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 22% 12% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 12%
Time To First Byte (TTFB)676ms 82% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 82% 15% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 15% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.4s 82% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 82% 13% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 13% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)2ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 1% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 1% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.8s 88% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 88% 9% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 9% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

Lab Data

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
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
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Speed Index 1.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Total Blocking Time 150 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. 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
First Contentful Paint 0.8 s
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
Largest Contentful Paint 1.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. 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
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
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more

Page Speed (Google PageSpeed Insights) - Mobile

44
0-49 50-89 90-100 i

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.

Cumulative Layout Shift (CLS)1ms 64% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 89% 2% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 2% 7% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 7%
Time To First Byte (TTFB)841ms 82% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 73% 24% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 24% 1% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)1.4s 82% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 88% 8% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 8% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)18ms 94% of loads for this page have a fast (<100ms) First Input Delay (FID) 94% 3% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 3% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.7s 88% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 90% 6% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 6% 2% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 2%

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.

Cumulative Layout Shift (CLS)1ms 89% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 89% 2% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 2% 7% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 7%
Time To First Byte (TTFB)841ms 73% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 73% 24% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 24% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)1.4s 88% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 88% 8% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 8% 3% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 3%
First Input Delay (FID)18ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 94% 3% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 3% 1% of loads for this page have a slow (>300ms) First Input Delay (FID) 1%
Interactive To Next Paint (INP)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.7s 90% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 90% 6% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 6% 2% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 2%

Lab Data

First Contentful Paint (3G) 5850 ms
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
Total Blocking Time 1,070 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more
Max Potential First Input Delay 460 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more
Speed Index 6.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more
Time to Interactive 9.7 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more
First Contentful Paint 3.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more
First Meaningful Paint 3.0 s
First Meaningful Paint measures when the primary content of a page is visible. 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
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
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
Largest Contentful Paint 4.3 s
Largest Contentful Paint marks the time at which the largest 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

Does food-tokyo.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 food-tokyo.jp are reduced by 73%.
food-tokyo.jp use gzip compression.
Original size: 70.7 KB
Compressed size: 18.92 KB
File reduced by: 51.78 KB (73%)

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.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites. food-tokyo.jp has 66 Safety Reputations.
Status:
  UNKNOWN
Safety Reputations:
  66
Safety Confidence:
  6

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. food-tokyo.jp supports HTTPS.
 food-tokyo.jp supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: www.food-tokyo.jp
Organization:
Location:
Issuer: GTS CA 1D4
Valid from: Oct 9 12:48:00 2022 GMT
Valid until: Jan 7 12:47:59 2023 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: GTS CA 1D4
Organization: Google Trust Services LLC
Location: US
Issuer: GTS Root R1
Valid from: Aug 13 00:00:42 2020 GMT
Valid until: Sep 30 00:00:42 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: GTS Root R1
Organization: Google Trust Services LLC
Location: US
Issuer: GlobalSign Root CA
Valid from: Jun 19 00:00:42 2020 GMT
Valid until: Jan 28 00:00:42 2028 GMT
Authority: CA:TRUE
Keysize: 4096 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.
 food-tokyo.jp supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Site Categories ▼

Website categories are used to classify websites based on their content or purpose. These categories provide a way to organize and filter websites, allowing users to find relevant information or ensure compliance with specific regulations or policies.
工学/食品科学

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. 
location: https://www.food-tokyo.jp/
date: Sat, 05 Nov 2022 06:21:03 GMT
content-type: text/html; charset=UTF-8
server: ghs
content-length: 223
x-xss-protection: 0
x-frame-options: SAMEORIGIN

HTTP/2 301 
content-type: text/html; charset=UTF-8
location: /p/top.html
content-encoding: gzip
date: Sat, 05 Nov 2022 06:21:03 GMT
expires: Sat, 05 Nov 2022 06:21:03 GMT
cache-control: private, max-age=0
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
content-length: 161
server: GSE

HTTP/2 200 
content-type: text/html; charset=UTF-8
expires: Sat, 05 Nov 2022 06:21:03 GMT
date: Sat, 05 Nov 2022 06:21:03 GMT
cache-control: private, max-age=0
last-modified: Fri, 14 Oct 2022 08:29:42 GMT
etag: W/"a2f1c8c0d558c239301df048bbfbea3d7f751420a4e57a18f1e6874219bed075"
content-encoding: gzip
x-content-type-options: nosniff
x-xss-protection: 1; mode=block
content-length: 19375
server: GSE

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
A 216.239.36.21 3547
A 216.239.38.21 3547
A 216.239.32.21 3547
A 216.239.34.21 3547
SOA 3547
Mname 01.dnsv.jp
Rname hostmaster.dnsv.jp
Serial Number 1655361051
Refresh 3600
Retry 900
Expire 604800
Minimum TTL 300
NS 02.dnsv.jp 3545
NS 01.dnsv.jp 3545
NS 04.dnsv.jp 3545
NS 03.dnsv.jp 3545

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 May 1, 2022 and will expire on May 31, 2023 if not renewed. This website is now assigned through the registrar . The WHOIS data for this website's domain was last updated on June 16, 2022.
Domain Created:
2022-05-01
Domain Expires:
2023-05-31
Domain Updated:
2022-06-16
Domain Age:
2 years 10 months 30 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'.                 ]

Domain Information:
[Domain Name]                   FOOD-TOKYO.JP

[Registrant]                    (Not displayed by registrant's request)
                                For details -> https://jprs.jp/about/dom-rule/whois-concealment/ (only in Japanese)

[Name Server]                   03.dnsv.jp
[Name Server]                   02.dnsv.jp
[Name Server]                   01.dnsv.jp
[Name Server]                   04.dnsv.jp
[Signing Key]                   

[Created on]                    2022/05/01
[Expires on]                    2023/05/31
[Status]                        Active
[Last Updated]                  2022/06/16 18:10:38 (JST)

Contact Information:
[Name]                          Whois Privacy Protection Service by onamae.com
[Email]                         email
[Web Page]                       
[Postal code]                   150-8512
[Postal Address]                Shibuya-ku
                                26-1 Sakuragaoka-cho
                                Cerulean Tower 11F
[Phone]                         +81.354562560
[Fax]