Yume.wiki
YumeWikiDomain Summary
What is the traffic rank for Yume.wiki?
• Yume.wiki ranks #177,982 globally on HypeStat.
What percent of global Internet users visit Yume.wiki?
• 0.0001458% of global Internet users visit Yume.wiki
How many people visit Yume.wiki each day?
• Yume.wiki receives approximately 7.2K visitors and 92,094 page impressions per day.
Which countries does Yume.wiki receive most of its visitors from?
• Yume.wiki is mostly visited by people located in United States,Spain,United Kingdom.
How much Yume.wiki can earn?
• Yume.wiki should earn about $389.91/day from advertising revenue.
What is Yume.wiki estimated value?
• Estimated value of Yume.wiki is $422,052.51.
What IP addresses does Yume.wiki resolve to?
• Yume.wiki resolves to the IP addresses 2606:4700:3034::6815:37a0, 172.67.171.169.
Where are Yume.wiki servers located in?
• Yume.wiki has servers located in United States.
yume.wiki Profile
About:
Yume.wiki is an informational platform predominantly dedicated to the "Yume Nikki" universe and its related fan games. On the website, users can find comprehensive details about the exploration-based game created by the enigmatic Japanese developer, Kikiyama. The platform offers extensive guides, character profiles, and individual articles about the multitude of dream worlds players can explore in the game. Additionally, it serves as a hub for the fan community, maintaining pages on various fan-made projects inspired by the original game, fostering a collaborative environment for enthusiasts of the genre.
*This text is generated by artificial intelligence and may not be accurate. Edit Site Info
What technologies does yume.wiki use?
These are the technologies used at yume.wiki. yume.wiki has a total of 6 technologies installed in 5 different categories.yume.wiki Traffic Analysis
Yume.wiki is ranked #177,982 in the world. This website is viewed by an estimated 7.2K visitors daily, generating a total of 92.1K pageviews. This equates to about 217.8K monthly visitors. Yume.wiki traffic has increased by 18.35% compared to last month.Daily Visitors7.2K
2.39%
Monthly Visits217.8K
18.35%
Pages per Visit12.81
12.91%
Visit duration15:48
21.18%
Bounce Rate27.30%
1.07%
Is this your site?Verify your site's metrics.
- Daily Unique Visitors:
- 7,189
- Monthly Visits:
- 217,827
- Pages per Visit:
- 12.81
- Daily Pageviews:
- 92,094
- Avg. visit duration:
- 15:48
- Bounce rate:
- 27.30%
- Global Reach:
- 0.0001458%
- Monthly Visits (SEMrush):
- 72,176
- Monthly Unique Visitors (SEMrush):
- 12,908
- Monthly Visits (SimilarWeb):
- 213,542
- HypeRank:
- 177,982
- SEMrush Rank:
- 605,688
- SimilarWeb Rank:
- 141,317
Traffic sources
- Direct:
- 59.57%
- Referral:
- 25.85%
- Search:
- 13.45%
- Social:
- 1.13%
- Paid:
- 0%
Desktop vs Mobile
- Desktop:
- 59.87%
- Mobile:
- 40.13%
Total Visits Last 3 Months
109K
MAR
184.1K
APR
217.8K
MAY
Visitors by country
- Country
- Users%
- United States 65.83%
- Spain 5.74%
- United Kingdom 4.17%
- Mexico 3.56%
- Canada 3.08%
Backlinks Report ▼
Yume.wiki has a total of 1,865 backlinks from 356 referring domains and most of them comes from United States.- Total Backlinks:
- 1,865
- Follow Links:
- n/a
- Nofollow Links:
- n/a
- Referring Domains:
- 356
- Referring IPs:
- 388
- Authority Domain Score:
- 13
Backlinks by country
- Country
- Domains
- United States 141
- Russian Federation 25
- France 24
- Singapore 11
- Germany 10
Backlinks by TLDs
- TLD Distribution
- Domains
- .com
- 165
- .ru
- 18
- .org
- 18
- .edu
- 0
- .gov
- 0
Which sites are competitors to yume.wiki?
Websites similar to yume.wiki 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.- Domain
- CompareDaily Visitors
- steampowered.com
- Compare >6.4M
- ign.com
- Compare >3.9M
- playstation.com
- Compare >2.2M
- ea.com
- Compare >2M
- xbox.com
- Compare >1.8M
- wowhead.com
- Compare >1.6M
- gamespot.com
- Compare >1.5M
- gamesradar.com
- Compare >1.2M
- newgrounds.com
- Compare >496.3K
- gamestop.com
- Compare >320.8K
- runescape.com
- Compare >240.4K
- bigfishgames.com
- Compare >105K
- agame.com
- Compare >66K
- addictinggames.com
- Compare >34.7K
- cheatcc.com
- Compare >27K
- thesims3.com
- Compare >15.6K
- nickjr.com
- Compare >14K
- gamefaqs.com
- Compare >11.5K
- funny-games.biz
- Compare >6.1K
- wowwiki.com
- Compare >98
Last update was 26 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 yume.wiki 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.- Google Index:
- 19,800
▼
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:
- yume.wiki
- Rank:
(Rank based on keywords, cost and organic traffic) - 605,688
- Organic Keywords:
(Number of keywords in top 20 Google SERP) - 1,452
- Organic Traffic:
(Number of visitors coming from top 20 search results) - 2,047
- Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords) - $135.00
Revenue report ▼
Google.com would generate approximately $389.9 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $11.7K and annual gross revenue of approximately $142.3K. Based on these figures, the site's net worth is estimated at around $422.1K.How much would yume.wiki make?
- Daily Revenue:
- $389.91
- Monthly Revenue:
- $11,697.30
- Yearly Revenue:
- $142,317.15
Daily earning by country
- CountryPageviewsEarning
- United States 60,628$292.83
- Canada 2,834$17.12
- United Kingdom 3,839$10.29
- Spain 5,283$2.54
- Mexico 3,281$0.92
Loss of money due to Adblock?
- Daily Revenue Loss:
- $59.20
- Monthly Revenue Loss:
- $1,776.01
- Yearly Revenue Loss:
- $21,608.17
- Daily Pageviews Blocked:
- 13,535
- Monthly Pageviews Blocked:
- 406,051
- Yearly Pageviews Blocked:
- 4,940,282
Daily revenue loss by country
- CountryBlockedLost Money
- United States 10,913$52.71
- Canada 709$4.28
- United Kingdom 614$1.65
- Spain 1,004$0.48
- Mexico 295$0.08
How much is yume.wiki worth?
- Website Value:
- $422.1K
Ad Experience Report ▼
Summary of the ad experience rating of a website for a specific platform.Mobile summary
- Root domain:
- yume.wiki
- 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:
- yume.wiki
- 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:
- yume.wiki
- 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 yume.wiki hosted? ▼
Yume.wiki may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.- Server IP:
- 2606:4700:3034::6815:37a0, 172.67.171.169
- ASN:
- AS13335
- ISP:
- Cloudflare Inc
- Server Location:
United States, US
Other sites hosted on 172.67.171.169
How fast does yume.wiki load? ▼
The average loading time of yume.wiki is 832 ms. The Desktop speed index is 92 and mobile speed index is 73.- Average Load Time:
- 832 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)618ms
First Contentful Paint (FCP)1.2s
First Input Delay (FID)2ms
Interaction To Next Paint (INP)30ms
Largest Contentful Paint (LCP)1.2s
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)2ms
Time To First Byte (TTFB)645ms
First Contentful Paint (FCP)950ms
First Input Delay (FID)1ms
Interaction To Next Paint (INP)30ms
Largest Contentful Paint (LCP)1.0s
Lab Data
First Contentful Paint 1.0 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
First Meaningful Paint 1.0 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
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 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
Time to Interactive 1.0 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
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
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
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
Speed Index 1.0 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
Largest Contentful Paint 1.1 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 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)0ms
Time To First Byte (TTFB)770ms
First Contentful Paint (FCP)1.5s
First Input Delay (FID)11ms
Interactive To Next Paint (INP)252ms
Largest Contentful Paint (LCP)1.5s
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)0ms
Time To First Byte (TTFB)723ms
First Contentful Paint (FCP)1.1s
First Input Delay (FID)10ms
Interactive To Next Paint (INP)235ms
Largest Contentful Paint (LCP)1.2s
Lab Data
Speed Index 3.2 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
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
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
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
First Contentful Paint 3.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
Time to Interactive 5.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
First Meaningful Paint 3.2 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
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
Total Blocking Time 30 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
Largest Contentful Paint 4.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
Does yume.wiki 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 yume.wiki are reduced by 77%.
yume.wiki use br compression.
Original size: 39.18 KB
Compressed size: 8.78 KB
File reduced by: 30.4 KB (77%)
Compressed size: 8.78 KB
File reduced by: 30.4 KB (77%)
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. yume.wiki supports HTTPS. yume.wiki supports HTTPS
Verifying SSL Support. Please wait...
Common Name: yume.wiki
Organization:
Location:
Issuer: WE1
Valid from: Oct 19 03:54:16 2024 GMT
Valid until: Jan 17 03:54:15 2025 GMT
Authority: CA:FALSE
Keysize:
Organization:
Location:
Issuer: WE1
Valid from: Oct 19 03:54:16 2024 GMT
Valid until: Jan 17 03:54:15 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: WE1
Organization: Google Trust Services
Location: US
Issuer: GTS Root R4
Valid from: Dec 13 09:00:00 2023 GMT
Valid until: Feb 20 14:00:00 2029 GMT
Authority: CA:TRUE
Keysize:
Organization: Google Trust Services
Location: US
Issuer: GTS Root R4
Valid from: Dec 13 09:00:00 2023 GMT
Valid until: Feb 20 14:00:00 2029 GMT
Authority: CA:TRUE
Keysize:
Common Name: GTS Root R4
Organization: Google Trust Services LLC
Location: US
Issuer: GlobalSign Root CA
Valid from: Nov 15 03:43:21 2023 GMT
Valid until: Jan 28 00:00:42 2028 GMT
Authority: CA:TRUE
Keysize:
Organization: Google Trust Services LLC
Location: US
Issuer: GlobalSign Root CA
Valid from: Nov 15 03:43:21 2023 GMT
Valid until: Jan 28 00:00:42 2028 GMT
Authority: CA:TRUE
Keysize:
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. yume.wiki 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: Fri, 08 Nov 2024 13:45:02 GMT
content-type: text/html; charset=UTF-8
location: https://yume.wiki/Main_Page
x-content-type-options: nosniff
vary: Accept-Encoding, Cookie
expires: Thu, 01 Jan 1970 00:00:00 GMT
cache-control: private, must-revalidate, max-age=0
last-modified: Fri, 08 Nov 2024 13:45:02 GMT
x-request-id: 045228d96edf680d6783c612
access-control-allow-origin: https://2kki.app
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=ZgUfYcStbA22o9Pj6o8G%2B1uJJejPv6JMyCvsdrIpljlCojeVXM3JsBjneKgoMoi%2FpGO8XRD%2BBF6Pa%2BqCFZ%2Fb7iVWU61ANgy6%2FhoFB%2FwHcJIaPO9B621lfTHPa38%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
strict-transport-security: max-age=15552000; includeSubDomains; preload
server: cloudflare
cf-ray: 8df6004aec0d60a6-ORD
alt-svc: h3=":443"; ma=86400
server-timing: cfL4;desc="?proto=TCP&rtt=1585&sent=8&recv=13&lost=0&retrans=0&sent_bytes=3419&recv_bytes=890&delivery_rate=1606211&cwnd=141&unsent_bytes=0&cid=fee6b57287aee3ed&ts=251&x=0"
HTTP/2 200
date: Fri, 08 Nov 2024 13:45:02 GMT
content-type: text/html; charset=UTF-8
x-content-type-options: nosniff
content-language: en
vary: Accept-Encoding, Cookie
expires: Thu, 01 Jan 1970 00:00:00 GMT
cache-control: private, must-revalidate, max-age=0
last-modified: Fri, 08 Nov 2024 13:45:02 GMT
x-request-id: 436b564deabfddc48eb9de9d
access-control-allow-origin: https://2kki.app
cf-cache-status: DYNAMIC
report-to: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=Lt8oyXV10ea8ZPveThZryVv38pt%2BC51OOU446yQ0HhsG7m5jx8Ek9vZECcZ2ozt%2BYWetfKrmkAOMB%2B7fcsi7n4uvg7Edxwbchg642kyUFxd5IpKEyxkRHPuh4f4%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
strict-transport-security: max-age=15552000; includeSubDomains; preload
server: cloudflare
cf-ray: 8df6004c6ddd60a6-ORD
content-encoding: br
alt-svc: h3=":443"; ma=86400
server-timing: cfL4;desc="?proto=TCP&rtt=1636&sent=11&recv=16&lost=0&retrans=0&sent_bytes=4235&recv_bytes=938&delivery_rate=1606211&cwnd=143&unsent_bytes=0&cid=fee6b57287aee3ed&ts=786&x=0"
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 |
AAAA | 2606:4700:3034::ac43:aba9 | 290 | |
AAAA | 2606:4700:3034::6815:37a0 | 290 | |
A | 172.67.171.169 | 290 | |
A | 104.21.55.160 | 290 | |
NS | 3590 | ||
NS | 3590 | ||
HINFO | 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 August 20, 2022 and will expire on August 20, 2024 if not renewed. This website is now assigned through the registrar NAMECHEAP INC. The WHOIS data for this website's domain was last updated on August 13, 2023.- Domain Created:
- 2022-08-20
- Domain Expires:
- 2024-08-20
- Domain Updated:
- 2023-08-13
- Domain Age:
- 2 years 3 months 15 days
- Domain Registrar:
- NAMECHEAP INC
- Domain Owner:
- Privacy service provided by Withheld for Privacy e
- WhoIs:
Domain name: yume.wiki Registry Domain ID: DD01B8C4006C84BEF9174BA0BD13DCE7B-GDREG Registrar WHOIS Server: whois.namecheap.com Registrar URL: http://www.namecheap.com Updated Date: 2023-08-13T19:51:44.71Z Creation Date: 2022-08-20T01:31:50.43Z Registrar Registration Expiration Date: 2024-08-20T01:31:50.43Z Registrar: NAMECHEAP INC Registrar IANA ID: 1068 Registrar Abuse Contact Email: Registrar Abuse Contact Phone: +1.9854014545 Reseller: NAMECHEAP INC Domain Status: ok https://icann.org/epp#ok Registry Registrant ID: Registrant Name: Redacted for Privacy Registrant Organization: Privacy service provided by Withheld for Privacy ehf Registrant Street: Kalkofnsvegur 2 Registrant City: Reykjavik Registrant State/Province: Capital Region Registrant Postal Code: 101 Registrant Country: IS Registrant Phone: +354.4212434 Registrant Phone Ext: Registrant Fax: Registrant Fax Ext: Registrant Email: Registry Admin ID: Admin Name: Redacted for Privacy Admin Organization: Privacy service provided by Withheld for Privacy ehf Admin Street: Kalkofnsvegur 2 Admin City: Reykjavik Admin State/Province: Capital Region Admin Postal Code: 101 Admin Country: IS Admin Phone: +354.4212434 Admin Phone Ext: Admin Fax: Admin Fax Ext: Admin Email: Registry Tech ID: Tech Name: Redacted for Privacy Tech Organization: Privacy service provided by Withheld for Privacy ehf Tech Street: Kalkofnsvegur 2 Tech City: Reykjavik Tech State/Province: Capital Region Tech Postal Code: 101 Tech Country: IS Tech Phone: +354.4212434 Tech Phone Ext: Tech Fax: Tech Fax Ext: Tech Email: Name Server: meg.ns.cloudflare.com Name Server: yew.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2024-06-20T10:45:12.74Z