aromafudge.tokyo Aromafudge.tokyo

   
メンエス怪獣のメンズエステ中毒ブログ – 年間150店舗訪問！アクシデント多数！三度の飯より紙パンツが好き。メンズエステに通い続け約4年の中で起きた数々のアクシデント(本番、フェラ、おっぱいスタンプなど)、築き上げてきた店舗データを面白おかしくシェアします！東京は麻布十番、恵比寿、渋谷、池袋、新宿から、横浜や川崎まで。地方遠征の際は、中洲やすすきの。大阪、名古屋の情報もお届けします。

Domain Summary

What is the traffic rank for Aromafudge.tokyo?

• Aromafudge.tokyo ranks #261,820 globally on HypeStat.

What percent of global Internet users visit Aromafudge.tokyo?

• 9.73E-5% of global Internet users visit Aromafudge.tokyo

How many people visit Aromafudge.tokyo each day?

• Aromafudge.tokyo receives approximately 4.8K visitors and 14,803 page impressions per day.

Which countries does Aromafudge.tokyo receive most of its visitors from?

• Aromafudge.tokyo is mostly visited by people located in Japan.

How much Aromafudge.tokyo can earn?

• Aromafudge.tokyo should earn about $5.33/day from advertising revenue.

What is Aromafudge.tokyo estimated value?

• Estimated value of Aromafudge.tokyo is $4,744.87.

What IP addresses does Aromafudge.tokyo resolve to?

• Aromafudge.tokyo resolves to the IP addresses 103.3.2.161.

Where are Aromafudge.tokyo servers located in?

• Aromafudge.tokyo has servers located in Japan.

aromafudge.tokyo Profile

Title:メンエス怪獣のメンズエステ中毒ブログ – 年間150店舗訪問！アクシデント多数！三度の飯より紙パンツが好き。メンズエステに通い続け約4年の中で起きた数々のアクシデント(本番、フェラ、おっぱいスタンプなど)、築き上げてきた店舗データを面白おかしくシェアします！東京は麻布十番、恵比寿、渋谷、池袋、新宿から、横浜や川崎まで。地方遠征の際は、中洲やすすきの。大阪、名古屋の情報もお届けします。
Category:Adult / Adult
Edit Site Info

What technologies does aromafudge.tokyo use?

These are the technologies used at aromafudge.tokyo. aromafudge.tokyo has a total of 9 technologies installed in 10 different categories.
Analytics
Google Analytics Google Analytics
CDN
Google Hosted Libraries Google Hosted Libraries
Tag Managers
Google Tag Manager Google Tag Manager
JavaScript Libraries
jQuery jQuery
Slick Slick
Web Servers
Nginx Nginx
Reverse proxies
Nginx Nginx
CMS
WordPress WordPress
Blogs
WordPress WordPress
Programming Languages
PHP PHP
Databases
MySQL MySQL

aromafudge.tokyo Traffic Analysis

Aromafudge.tokyo is ranked #261,820 in the world. This website is viewed by an estimated 4.8K visitors daily, generating a total of 14.8K pageviews. This equates to about 145.3K monthly visitors. Aromafudge.tokyo traffic has decreased by 13.33% compared to last month.
Daily Visitors4.8K
59.67%
Monthly Visits145.3K
13.33%
Pages per Visit3.09
25.51%
Visit duration03:06
19.72%
Bounce Rate65.84%
38.12%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
4,795
Monthly Visits:
145,289
Pages per Visit:
3.09
Daily Pageviews:
14,803
Avg. visit duration:
03:06
Bounce rate:
65.84%
Global Reach:
9.73E-5%
Monthly Visits (SEMrush):
91,805
Monthly Unique Visitors (SEMrush):
69,878
Monthly Visits (SimilarWeb):
142,421
HypeRank:
261,820
SEMrush Rank:
15,338,783
SimilarWeb Rank:
261,820
*All traffic values are estimates only.

Traffic sources

Direct:
8.40%
Referral:
0.53%
Search:
91.08%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
22.34%
Mobile:
77.66%

Total Visits Last 3 Months

136.7K
DEC
167.6K
JAN
145.3K
FEB

Visitors by country

Country
Users%
 
Japan 100.00%

Which sites are competitors to aromafudge.tokyo?

Websites similar to aromafudge.tokyo are sites similar on user interests and browsing behavior. Users can discover new websites that are similar to the ones they already enjoy or find useful.
Last update was 11 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with aromafudge.tokyo 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:
  aromafudge.tokyo
Rank:
(Rank based on keywords, cost and organic traffic)
  15,338,783
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  13
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
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 $5.3 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $159.9 and annual gross revenue of approximately $1.9K. Based on these figures, the site's net worth is estimated at around $4.7K.

How much would aromafudge.tokyo make?

Daily Revenue:
$5.33
Monthly Revenue:
$159.90
Yearly Revenue:
$1,945.45
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Japan 14,803$5.33

Loss of money due to Adblock?

Daily Revenue Loss:
$0.16
Monthly Revenue Loss:
$4.80
Yearly Revenue Loss:
$58.35
Daily Pageviews Blocked:
444
Monthly Pageviews Blocked:
13,323
Yearly Pageviews Blocked:
162,093

Daily revenue loss by country

 
CountryBlockedLost Money
 
Japan 444$0.16

How much is aromafudge.tokyo worth?

Website Value:
$4.7K

Ad Experience Report ▼

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

Mobile summary

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

Aromafudge.tokyo may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
103.3.2.161
ASN:
AS131965 
ISP:
Xserver Inc. 
Server Location:

Japan, JP
 

Other sites hosted on 103.3.2.161

There are no other sites hosted on this IP

How fast does aromafudge.tokyo load? ▼

The average loading time of aromafudge.tokyo is 701 ms. The Desktop speed index is 82 and mobile speed index is 0.
Average Load Time:
701 ms

Page Speed (Google PageSpeed Insights) - Desktop

82
0-49 50-89 90-100 i

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)0ms 95% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 95% 4% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 4% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)477ms 94% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 94% 4% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 4% 0% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)889ms 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)23ms 98% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 98% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.0s 96% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 96% 2% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 2% 1% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 1%

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 99% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 99% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)300ms 96% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 96% 3% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 3% 0% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)820ms 95% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 95% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 0% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 0%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)31ms 99% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 99% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.0s 97% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 97% 2% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 2% 0% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 0%

Lab Data

INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
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 how to defer third-parties with a facade
Forced reflow  
Many APIs, typically reading layout geometry, force the rendering engine to pause script execution in order to calculate the style and layout. Learn more about and its mitigations. forced reflow
Long critical network tree  
by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Avoid chaining critical requests
First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Max Potential First Input Delay 70 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
Total Blocking Time 10 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
Speed Index 1.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Largest Contentful Paint 1.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Font display  
Consider setting to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with . font-display font metric overrides
Optimize DOM size  
A large DOM can increase the duration of style calculations and layout reflows, impacting page responsiveness. A large DOM will also increase memory usage. Learn how to avoid an excessive DOM size
Time to Interactive 1.6 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

Does aromafudge.tokyo 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 aromafudge.tokyo are reduced by 83%.
aromafudge.tokyo use br compression.
Original size: 109.16 KB
Compressed size: 17.89 KB
File reduced by: 91.26 KB (83%)

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.
Status:
  SAFE
Child Safety Reputations:
  10
Child Safety Confidence:
  51

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. aromafudge.tokyo supports HTTPS.
 aromafudge.tokyo supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: www.aromafudge.tokyo
Organization:
Location:
Issuer: R11
Valid from: Mar 21 01:22:45 2025 GMT
Valid until: Jun 19 01:22:44 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R11
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 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.
 aromafudge.tokyo 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. 
server: nginx
date: Wed, 26 Mar 2025 17:35:05 GMT
content-type: text/html; charset=UTF-8
vary: Accept-Encoding
link: <https://aromafudge.tokyo/wp-json/>; rel="https://api.w.org/"
set-cookie: liquid_connect_target_visitor=1; expires=Wed, 26-Mar-2025 17:36:05 GMT; Max-Age=60; path=/
content-encoding: br

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 v=spf1 +a:sv12160.xserver.jp +a:aromafudge.tokyo +mx include:spf.sender.xserver.jp ~all 3600
MX aromafudge.tokyo 3600
SOA 3600
Mname ns1.xserver.jp
Rname root.xserver.jp
Serial Number 0
Refresh 10800
Retry 3600
Expire 604800
Minimum TTL 3600
A 103.3.2.161 3521
NS ns1.xserver.jp 3600
NS ns2.xserver.jp 3600
NS ns5.xserver.jp 3600
NS ns4.xserver.jp 3600
NS ns3.xserver.jp 3600

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 4, 2021 and will expire on February 4, 2026 if not renewed. This website is now assigned through the registrar GMO Internet Group, Inc.. The WHOIS data for this website's domain was last updated on February 5, 2025.
Domain Created:
2021-02-04
Domain Expires:
2026-02-04
Domain Updated:
2025-02-05
Domain Age:
4 years 2 months 3 days
Domain Registrar:
GMO Internet Group, Inc.
WhoIs:
 

Domain Name: AROMAFUDGE.TOKYO
Registry Domain ID: DO5495455-GMO
Registrar WHOIS Server:
Registrar URL: http://www.onamae.com/
Updated Date: 2025-02-05T05:19:25.0Z
Creation Date: 2021-02-04T05:16:02.0Z
Registry Expiry Date: 2026-02-04T23:59:59.0Z
Registrar: GMO Internet Group, Inc.
Registrar IANA ID: 49
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +81.337709199
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registrant State/Province: Fukuoka
Registrant Country: JP
Registrant Email:
Admin Email:
Tech Email:
Name Server: NS1.XSERVER.JP
Name Server: NS2.XSERVER.JP
Name Server: NS3.XSERVER.JP
Name Server: NS4.XSERVER.JP
Name Server: NS5.XSERVER.JP
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2025-03-26T17:36:21.0Z