eyez.blog

Eyez.blog

#3,983,124 Global
Mkt single page application
Last Updated 572 days ago
     
This can take up to 60 seconds. Please wait...

Domain Summary

What is the traffic rank for Eyez.blog?

Eyez.blog ranks #3,983,124 globally on HypeStat.

What percent of global Internet users visit Eyez.blog?

8.7E-6% of global Internet users visit Eyez.blog

How many people visit Eyez.blog each day?

Eyez.blog receives approximately 427 visitors and 720 page impressions per day.

How much Eyez.blog can earn?

Eyez.blog should earn about $2.94/day from advertising revenue.

What is Eyez.blog estimated value?

Estimated value of Eyez.blog is $2,610.77.

What IP addresses does Eyez.blog resolve to?

Eyez.blog resolves to the IP addresses 2606:4700:3030::6815:2001, 104.21.96.1.

eyez.blog Profile

Title
mkt single page application

eyez.blog Traffic Analysis

Eyez.blog is ranked #3,983,124 in the world. This website is viewed by an estimated 427 visitors daily, generating a total of 720 pageviews. This equates to about 12.9K monthly visitors. Eyez.blog traffic has decreased by 64.09% compared to last month.

Daily Visitors
427
427 unique
▲ 7.73%
Monthly Visits
12.9K
▼ 64.09%
Pages per Visit
1.69
Visit Duration
00:24
Bounce Rate
65.00%
▼ 0.01%
Is this your site?Verify your site's metrics.
Daily Unique Visitors
427
Monthly Visits
12,938
Pages per Visit
1.69
Daily Pageviews
720
Avg. Visit Duration
00:24
Bounce Rate
65.00%
Global Reach
8.7E-6%
Monthly Visits (SEMrush)
15,031
Monthly Unique Visitors (SEMrush)
15,031
Monthly Visits (SimilarWeb)
12,945
HypeRank
3,983,124
SimilarWeb Rank
2,133,578

*All traffic values are estimates only.

Traffic Sources

Direct
99.99%
Referral
0.01%
Search
0%
Social
0%
Paid
0%

Desktop vs Mobile

Desktop
0%
Mobile
100.00%

Total Visits Last 3 Months

5.4K
DEC
36K
JAN
12.9K
FEB
SEO

eyez.blog SEMrush Overview

SEMrush is a complete online advertising and marketing platform that gives a wide variety of tools and features to help businesses and marketers improve their online visibility and optimize their digital marketing strategies.

SemRushSemRush
Domain
eyez.blog
RankBased on keywords, cost and organic traffic
n/a
Organic KeywordsKeywords in top 20 Google SERP
0
Organic TrafficVisitors coming from top 20 search results
0
Organic CostEquivalent Google Ads spend for the same traffic
$0.00
Full SEMrush Report →

Search Engine Indexes

Search engine indexes are huge databases of web pages that search engines like Google, Bing 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
1
Monetization

Revenue Report

eyez.blog would generate approximately $2.9 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $88.2 and annual gross revenue of approximately $1.1K. Based on these figures, the site's net worth is estimated at around $2.6K.

How much would eyez.blog make?

Daily Revenue
$2.94
Monthly Revenue
$88.20
Yearly Revenue
$1,073.10

How much is eyez.blog worth?

Website Value
$2.6K

*All earnings values are estimates only.

Ad Experience Report

Summary of the ad and abusive experience ratings Google assigns to eyez.blog, per platform.

Mobile Summary

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

Desktop Summary

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

Abusive Experience

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

Where is eyez.blog hosted?

Eyez.blog may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.

ASN
AS13335
ISP
Cloudflare Inc
Server Location


Other sites hosted on 104.21.96.1

How fast does eyez.blog load?

The average loading time of eyez.blog is 2007 ms. The Desktop speed index is 91 and mobile speed index is 72.

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

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.

CLSCumulative Layout Shift
0ms
100% fast0% avg0% slow
TTFBTime To First Byte
702ms
79% fast16% avg4% slow
FCPFirst Contentful Paint
1.2s
88% fast8% avg3% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
19ms
92% fast4% avg3% slow
LCPLargest Contentful Paint
1.3s
93% fast4% avg2% slow

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.

CLSCumulative Layout Shift
0ms
100% fast0% avg0% slow
TTFBTime To First Byte
702ms
80% fast15% avg4% slow
FCPFirst Contentful Paint
1.2s
88% fast7% avg3% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
19ms
92% fast4% avg3% slow
LCPLargest Contentful Paint
1.3s
93% fast4% avg2% slow
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
Time to Interactive1.2 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
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
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
Speed Index2.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
Max Potential First Input Delay20 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
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
Total Blocking Time0 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
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Largest Contentful Paint1.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
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
INP by phase
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
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 Contentful Paint1.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
72
Needs Work
0–49 · Poor
50–89 · Needs Improvement
90–100 · Good
How is this scored? →
Average Load Time
2007 ms

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.

CLSCumulative Layout Shift
0ms
99% fast0% avg0% slow
TTFBTime To First Byte
907ms
70% fast21% avg8% slow
FCPFirst Contentful Paint
2.0s
70% fast18% avg11% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
91ms
84% fast7% avg8% slow
LCPLargest Contentful Paint
2.2s
80% fast12% avg7% slow

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.

CLSCumulative Layout Shift
0ms
99% fast0% avg0% slow
TTFBTime To First Byte
907ms
70% fast21% avg8% slow
FCPFirst Contentful Paint
2.0s
70% fast18% avg11% slow
FIDFirst Input Delay
0
0% fast0% avg0% slow
INPInteraction To Next Paint
91ms
84% fast7% avg7% slow
LCPLargest Contentful Paint
2.2s
80% fast12% avg6% slow
First Contentful Paint4.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint 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
Total Blocking Time0 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
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
First Meaningful Paint
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
Time to Interactive4.4 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
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
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
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
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
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
Max Potential First Input Delay20 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
Speed Index5.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
Largest Contentful Paint4.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Improve image delivery
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Does eyez.blog 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 eyez.blog are reduced by 73%.

73%
Reduced
Original
1.73 KB
Compressed
473 B

Saved 1.27 KB off the original size

eyez.blog use gzip 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. eyez.blog supports HTTPS.

eyez.blog supports HTTPS
Verifying SSL Support. Please wait...
Common Name: shope.ee
Organization:
Location:
Issuer: GlobalSign GCC R6 AlphaSSL CA 2023
Valid from: May 17 02:17:25 2024 GMT
Valid until: Jun 18 02:17:24 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: GlobalSign GCC R6 AlphaSSL CA 2023
Organization: GlobalSign nv-sa
Location: BE
Issuer: GlobalSign
Valid from: Jul 19 03:43:25 2023 GMT
Valid until: Jul 19 00:00:00 2026 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: GlobalSign
Organization: GlobalSign
Location:
Issuer: GlobalSign Root CA
Valid from: Jun 19 00:00:00 2019 GMT
Valid until: Jan 28 12:00:00 2028 GMT
Authority: CA:TRUE
Keysize: 4096 Bits
Common Name: GlobalSign Root CA
Organization: GlobalSign nv-sa, OU = Root CA
Location: BE
Issuer: GlobalSign Root CA
Valid from: Sep 1 12:00:00 1998 GMT
Valid until: Jan 28 12:00:00 2028 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

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.

eyez.blog supports HTTP/2
eyez.blog supports 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: Wed, 19 Mar 2025 07:11:26 GMT
content-type: text/html
location: https://s.shopee.vn/
server: cloudflare
custom-header: S03
cf-cache-status: DYNAMIC
cf-ray: 922b27df3bd9812d-ORD
alt-svc: h3=":443"; ma=86400

HTTP/2 307 
server: SGW
date: Wed, 19 Mar 2025 07:11:27 GMT
content-type: text/html; charset=utf-8
content-length: 63
location: https://shope.ee/error_page
x-request-id: ba18337830acbadb4a9dfc104122c000:000000810f28a472:0000000000000000

HTTP/2 200 
server: SGW
date: Wed, 19 Mar 2025 07:11:28 GMT
content-type: text/html; charset=utf-8
x-via: 44.2
vary: Accept-Encoding
x-ratelimit-limit: 1250
x-ratelimit-remaining: 1232
etag: W/"e768adac77f05f61c3b6d93aa5e81013"
last-modified: Mon, 03 Jun 2024 11:05:20 GMT
originalmd5: e768adac77f05f61c3b6d93aa5e81013
x-origin: uss
x-request-id: 55bad034-1690-4f9a-b374-92ad044bd05b
content-encoding: gzip
x-cache-status: HIT
x-uri: /shopee-mktspa-live-sg/portal/h5-link-track/index.html
x-cdn: staticcache
cache-control: no-cache

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:3030::6815:4001 223
AAAA 2606:4700:3030::6815:3001 223
AAAA 2606:4700:3030::6815:1001 223
AAAA 2606:4700:3030::6815:5001 223
AAAA 2606:4700:3030::6815:6001 223
AAAA 2606:4700:3030::6815:7001 223
AAAA 2606:4700:3030::6815:2001 223
A 104.21.80.1 223
A 104.21.16.1 223
A 104.21.32.1 223
A 104.21.48.1 223
A 104.21.64.1 223
A 104.21.112.1 223
A 104.21.96.1 223
NS mira.ns.cloudflare.com 3523
NS boyd.ns.cloudflare.com 3523
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 November 8, 2023 and will expire on November 8, 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 November 9, 2024.

Domain Created
2023-11-08
Domain Expires
2025-11-08
Domain Updated
2024-11-09
Domain Age
2 years 11 months 4 days
Domain Registrar
NAMECHEAP INC
Domain Owner
Privacy service provided by Withheld for Privacy e
WHOIS
Domain name: eyez.blog
Registry Domain ID: D408363438-CNIC
Registrar WHOIS Server: whois.namecheap.com
Registrar URL: http://www.namecheap.com
Updated Date: 2024-11-09T02:39:41.20Z
Creation Date: 2023-11-08T04:42:34.00Z
Registrar Registration Expiration Date: 2025-11-08T23:59:59.00Z
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
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: boyd.ns.cloudflare.com
Name Server: mira.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-19T01:12:25.44Z 
More on HypeStat
Activity

Recently Analyzed Sites

canaries.co.uk
HTTP/3 supportedHTTPS supported 5 secs
dreisteinenhof.de
HTTP/3 supportedHTTPS supported 36 secs
careery.pro
HTTP/2 supportedHTTPS supported 50 secs
dreizett.net
HTTP/2 supportedHTTPS supported 1 min
themodernsubstitute.com
HTTP/3 supportedHTTPS supported 1 min
dreissigacker-wein.com
HTTP/3 supportedHTTPS supported 2 mins
watchanimee.com
HTTP/2 supportedHTTPS supported 2 mins
dreistadtmoehnen-duelken.de
HTTP/2 supportedHTTPS supported 2 mins
stokecityfc.com
HTTP/2 supportedHTTPS supported 2 mins
dreizackreisen.com
HTTP/2 supportedHTTPS supported 3 mins
jatim.harianexpress.com
HTTP/2 supportedHTTPS supported 3 mins
dreiwannen.at
HTTP/2 supportedHTTPS supported 4 mins
dreistein.cc
HTTP/2 supportedHTTPS supported 4 mins
dreivital.at
HTTP/2 supportedHTTPS supported 4 mins
charmbodies.com
HTTP/3 supportedHTTPS supported 4 mins
Resources

Custom Widget

eyez.blog
Daily Visitors 427
Monthly Visits 12.9K
Pages / Visit 1.69
HypeRank #3,983,124
Powered by HypeStat
Embed a live, always up-to-date stats card like this on your own site.
Get the embed code →

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.