koi.finance

Koi.finance

#495,401 Global
Koi Finance
Last Updated 605 days ago
     
This can take up to 60 seconds. Please wait...

Domain Summary

What is the traffic rank for Koi.finance?

Koi.finance ranks #495,401 globally on HypeStat.

What percent of global Internet users visit Koi.finance?

0.000018% of global Internet users visit Koi.finance

How many people visit Koi.finance each day?

Koi.finance receives approximately 0.9K visitors and 1,826 page impressions per day.

Which countries does Koi.finance receive most of its visitors from?

Koi.finance is mostly visited by people located in Viet Nam,United States,United Kingdom.

How much Koi.finance can earn?

Koi.finance should earn about $2.78/day from advertising revenue.

What is Koi.finance estimated value?

Estimated value of Koi.finance is $2,550.53.

What IP addresses does Koi.finance resolve to?

Koi.finance resolves to the IP addresses 2606:4700:20::ac43:4960, 104.26.5.92.

koi.finance Profile

Title
Koi Finance
Description
Koi Finance is a zkRollup DeFi Platform. Invest & trade, earn yields, and participate in Bonds all on one decentralized, community driven platform.

What technologies does koi.finance use?

These are the technologies used at koi.finance. koi.finance has a total of 5 technologies installed in 4 different categories.

koi.finance Traffic Analysis

Koi.finance is ranked #495,401 in the world. This website is viewed by an estimated 0.9K visitors daily, generating a total of 1.8K pageviews. This equates to about 27.3K monthly visitors. Koi.finance traffic has decreased by 73.7% compared to last month.

Daily Visitors
0.9K
902 unique
▼ 38.27%
Monthly Visits
27.3K
▼ 73.7%
Daily Pageviews
1.8K
1,826 pageviews
Pages per Visit
2.02
▲ 19.57%
Visit Duration
00:11
▲ 27.96%
Bounce Rate
44.09%
▼ 9.3%
Daily Unique Visitors
902
Monthly Visits
27,331
Pages per Visit
2.02
Daily Pageviews
1,826
Avg. Visit Duration
00:11
Bounce Rate
44.09%
Global Reach
0.000018%
HypeRank
495,401
Monthly Visits (SEMrush)
61,375
Monthly Unique Visitors (SEMrush)
18,245
Organic Keywords (SEMrush)
10
Organic Traffic (SEMrush)
42
SEMrush Rank
5,002,452
Monthly Visits (SimilarWeb)
26,798
SimilarWeb Rank
1,063,196
Country Rank (SimilarWeb)
314,007
Category Rank (SimilarWeb)
3,672

Traffic Sources

Direct96.37%
Referral3.46%
Search0.17%
Social0%
Paid0%

Desktop vs Mobile

Desktop
17.64%
Mobile
82.36%

Monthly Visits

26.9K
DEC '24
103.9K
JAN '25
27.3K
FEB '25

Visitors by Country

CountryUsers %
Viet Nam 19.65%
United States 17.68%
United Kingdom 17.54%
United Arab Emirates 14.78%
Hong Kong 10.09%

*All traffic values are estimates only.

SEO

Which sites are competitors to koi.finance?

Websites similar to koi.finance 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.

DomainDaily Visitors
intuit.com 3.7M Compare →
marketwatch.com 0.9M Compare →
seekingalpha.com 626K Compare →
foxbusiness.com 605.7K Compare →
fortune.com 471.9K Compare →
bankrate.com 208.3K Compare →
prnewswire.com 140.4K Compare →
dowjones.com 105.1K Compare →
businesswire.com 81.6K Compare →
ccbill.com 78.1K Compare →
aon.com 53.1K Compare →
manta.com 37.7K Compare →
agriculture.com 21.7K Compare →
ibtimes.com 19.3K Compare →
creditcards.com 9.2K Compare →
eprintview.com 7.5K Compare →
alacrastore.com 1.5K Compare →
banks.com 551 Compare →
donkeymails.com 272 Compare →
hothyips.com 17 Compare →

Search Engine Indexes

Search engine indexes are huge databases of web pages that search engines like Google and Baidu use to retrieve relevant results when users search. These indexes are built by crawling and indexing pages from across the web.

Google Index
382
Monetization

Revenue Report

koi.finance would generate approximately $2.8 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $83.4 and annual gross revenue of approximately $1K. Based on these figures, the site's net worth is estimated at around $2.6K.

How much would koi.finance make?

Daily Revenue
$2.78
Monthly Revenue
$83.40
Yearly Revenue
$1,014.70

How much is koi.finance worth?

Website Value
$2.6K

*All earnings values are estimates only.

Daily Earning by Country

CountryPageviewsEarning
United States 323 $1.28
United Kingdom 320 $0.72
United Arab Emirates 270 $0.22
Hong Kong 184 $0.18
Viet Nam 359 $0.16

Daily Revenue Loss by Country

CountryBlockedLost
United States 58 $0.28
United Kingdom 51 $0.14
United Arab Emirates 38 $0.04
Hong Kong 18 $0.02
Viet Nam 14 $0.01

Impact of Ad Blockers

Daily Revenue Loss
$0.48
Monthly Revenue Loss
$14.43
Yearly Revenue Loss
$175.56
Daily Pageviews Blocked
180
Monthly Pageviews Blocked
5,398
Yearly Pageviews Blocked
65,673

Ad Experience Report

Summary of the ad and abusive experience ratings Google assigns to koi.finance, per platform.

Mobile Summary

Root Domain
koi.finance
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Desktop Summary

Root Domain
koi.finance
Ad FilteringChrome is not filtering ads on your site.
Off
StatusReviewed against the Better Ads Standards
Not reviewed

Abusive Experience

Root Domain
koi.finance
EnforcementChrome is not preventing your site from opening new windows or tabs.
Off
StatusReviewed for abusive experiences
Not reviewed
Technical

Where is koi.finance hosted?

Koi.finance is behind Cloudflare (CDN and security proxy). Visitors connect to Cloudflare's shared IP addresses, which answer from the nearest Cloudflare data center, so the real server location is hidden.

ISP
Cloudflare, Inc. CDN / proxy
Server Location
Hidden behind Cloudflare

Other sites using the same Cloudflare IP 104.26.5.92

How fast does koi.finance load?

The average loading time of koi.finance is 121 ms. The Desktop speed index is 75 and mobile speed index is 78.

75
Needs Work
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
121 ms

Over the last 30 days, the field data shows that this page has a 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.

All pages served from this origin have an 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.

Largest Contentful Paint1.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
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
First Contentful Paint0.8 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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
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
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
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
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
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Max Potential First Input Delay70 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
Time to Interactive1.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
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
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
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
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
Speed Index0.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Total Blocking Time10 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
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
78
Needs Work
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
121 ms

Over the last 30 days, the field data shows that this page has a 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.

All pages served from this origin have an 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.

Max Potential First Input Delay140 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
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
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
Time to Interactive4.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
Total Blocking Time120 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
Render blocking requests
Requests are blocking the page's initial render, which may delay LCP. can move these network requests out of the critical path. Deferring or inlining
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
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
First Contentful Paint2.6 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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
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
Speed Index4.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
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
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
Largest Contentful Paint4.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest 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
LCP request discovery
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading

Does koi.finance 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 koi.finance are reduced by 77%.

77%
Reduced
Original
39.81 KB
Compressed
8.86 KB

Saved 30.95 KB off the original size

koi.finance use br compression.

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

WOT 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

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 browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. koi.finance supports HTTPS.

koi.finance supports HTTPS
Verifying SSL Support. Please wait...
Common Name: koi.finance
Organization:
Location:
Issuer: WE1
Valid from: Mar 2 06:30:33 2025 GMT
Valid until: May 31 07:30:27 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:
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:

Verify HTTP/2 & HTTP/3 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. HTTP/3 goes a step further and runs over QUIC instead of TCP, for faster connections and better performance on unreliable networks.

koi.finance supports HTTP/2
koi.finance does not support HTTP/3
Verifying HTTP/2 and HTTP/3 Support. Please wait...
Details

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.

HTTP/1.1
date: Mon, 24 Mar 2025 12:20:21 GMT
content-type: text/html; charset=utf-8
access-control-allow-origin: *
cache-control: public, max-age=0, must-revalidate
link: <https://fonts.gstatic.com>; rel="preconnect"
referrer-policy: strict-origin-when-cross-origin
x-content-type-options: nosniff
x-matched-path: /en
report-to: {"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=G%2BBY%2BuZ8UiW49MtO2tdjSJ0MqOXZBhY0w3nh9OllHNfxrYODaLoQm%2BAgEc22nkPby4iDI1H4vVAtLE8COX2vFQuX0cZx0Y0ra0u9Uli%2B0ca6ad7fHcrO%2Fz0Jq9FSKg%3D%3D"}],"group":"cf-nel","max_age":604800}
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
vary: Accept-Encoding
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 92561f43ed28ead0-ORD
content-encoding: br
server-timing: cfL4;desc="?proto=TCP&rtt=7305&min_rtt=1935&rtt_var=10906&sent=8&recv=12&lost=0&retrans=0&sent_bytes=3394&recv_bytes=891&delivery_rate=1348858&cwnd=254&unsent_bytes=0&cid=86648c23531d0cd8&ts=115&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.

TypeIPTarget / TXTTTL
AAAA 2606:4700:20::681a:55c 248
AAAA 2606:4700:20::681a:45c 248
AAAA 2606:4700:20::ac43:4960 248
A 104.26.4.92 248
A 172.67.73.96 248
A 104.26.5.92 248
NS princess.ns.cloudflare.com 3548
NS damien.ns.cloudflare.com 3548
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 April 23, 2023 and will expire on April 23, 2025 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 February 9, 2024.

Domain Created
2023-04-23
Domain Expires
2025-04-23
Domain Updated
2024-02-09
Domain Age
3 years 6 months 27 days
Domain Registrar
NAMECHEAP INC
Domain Owner
Privacy service provided by Withheld for Privacy e
WHOIS
Domain name: koi.finance
Registry Domain ID: d1f4ecbaa0034afd98da743795296bea-DONUTS
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2024-02-09T10:01:22.35Z
Creation Date: 2023-04-23T17:11:16.08Z
Registrar Registration Expiration Date: 2025-04-23T17:11:16.08Z
Registrar: NAMECHEAP INC
Registrar IANA ID: 1068
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +1.9854014545
Reseller: NAMECHEAP INC
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: transferPeriod https://icann.org/epp#transferPeriod
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: 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: 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: email
Name Server: damien.ns.cloudflare.com
Name Server: princess.ns.cloudflare.com
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2025-03-23T13:21:13.01Z 

More on HypeStat

Activity

Recently Analyzed Sites

w3z6e.com
HTTP/2 supportedHTTPS supported 34 secs
debaodoor.com
HTTP/3 supportedHTTPS supported 1 min
szrongdao.com
HTTP/3 supportedHTTPS supported 2 mins
tvkitwing.com
HTTP/2 supportedHTTPS supported 2 mins
w41zdv.com
HTTP/3 supportedHTTPS supported 3 mins
w1m9r5.com
HTTP/3 supportedHTTPS supported 4 mins
123av.com
HTTP/3 supportedHTTPS supported 4 mins
w5k8zn.com
HTTP/3 supportedHTTPS supported 4 mins
yandex.eu
HTTP/2 supportedHTTPS supported 6 mins
w5e6t7.com
HTTP/3 supportedHTTPS supported 6 mins
merivelle.store
HTTP/3 supportedHTTPS supported 7 mins
w4n9x3k.com
HTTP/3 supportedHTTPS supported 7 mins
w5zalb9o.com
HTTP/3 supportedHTTPS supported 7 mins
miraluneqj.com
HTTP/2 supportedHTTPS supported 8 mins
mdph.re
HTTP/2 not supportedHTTPS not supported 8 mins
Resources

Custom Widget

koi.finance
Daily Visitors 0.9K
Monthly Visits 27.3K
Pages / Visit 2.02
HypeRank #495,401
Powered by HypeStat
Embed a live, always up-to-date stats card like this on your own site.
Get the embed code →

Own this website?

Verify that you own koi.finance to hide WHOIS data or traffic estimates, write the site description, connect Google Analytics to show your real traffic, or remove the report from HypeStat.
Manage this site →