frzyc.github.io Frzyc.github.io

   
Fred Zhao

Domain Summary

What is the traffic rank for Frzyc.github.io?

• Frzyc.github.io ranks #235,217 globally on HypeStat.

What percent of global Internet users visit Frzyc.github.io?

• 0.0001486% of global Internet users visit Frzyc.github.io

How many people visit Frzyc.github.io each day?

• Frzyc.github.io receives approximately 7.3K visitors and 60,594 page impressions per day.

Which countries does Frzyc.github.io receive most of its visitors from?

• Frzyc.github.io is mostly visited by people located in United States,Mauritius,United Kingdom.

How much Frzyc.github.io can earn?

• Frzyc.github.io should earn about $210.53/day from advertising revenue.

What is Frzyc.github.io estimated value?

• Estimated value of Frzyc.github.io is $207,476.47.

What IP addresses does Frzyc.github.io resolve to?

• Frzyc.github.io resolves to the IP addresses 2606:50c0:8003::153, 185.199.108.153.

Where are Frzyc.github.io servers located in?

• Frzyc.github.io has servers located in California, United States.

frzyc.github.io Profile

Title:Fred Zhao Description:Fred Zhao | Portfolio
Category:Games / Other Games
About: Frzyc.github.io is a personal website hosted on GitHub Pages, created and maintained by a developer using the pseudonym "Frzyc." The site typically showcases various projects and tools that the developer has worked on. Among these projects, the most well-known tool is likely the Cookie Clicker Mod Manager, which helps players manage and install mods for the popular incremental game Cookie Clicker. The website often includes detailed documentation, download links, and instructions, making it relatively user-friendly for those looking to enhance their game experience or explore the developer's other work. Overall, the site serves as a portfolio and resource center for Frzyc's programming and development efforts.
*This text is generated by artificial intelligence and may not be accurate. Edit Site Info

What technologies does frzyc.github.io use?

These are the technologies used at frzyc.github.io. frzyc.github.io has a total of 4 technologies installed in 4 different categories.
CDN
Fastly Fastly
PaaS
GitHub Pages GitHub Pages
Miscellaneous
PWA PWA
Caching
Varnish Varnish

frzyc.github.io Traffic Analysis

Frzyc.github.io is ranked #235,217 in the world. This website is viewed by an estimated 7.3K visitors daily, generating a total of 60.6K pageviews. This equates to about 222K monthly visitors. Frzyc.github.io traffic has decreased by 1.63% compared to last month.
Daily Visitors7.3K
14.27%
Monthly Visits222K
1.63%
Pages per Visit8.27
0.75%
Visit duration06:40
17.99%
Bounce Rate37.19%
6.32%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
7,327
Monthly Visits:
222,008
Pages per Visit:
8.27
Daily Pageviews:
60,594
Avg. visit duration:
06:40
Bounce rate:
37.19%
Global Reach:
0.0001486%
Monthly Visits (SEMrush):
414,902
Monthly Unique Visitors (SEMrush):
110,760
Monthly Visits (SimilarWeb):
217,638
HypeRank:
235,217
SEMrush Rank:
551,216
SimilarWeb Rank:
133,267
*All traffic values are estimates only.

Traffic sources

Direct:
80.78%
Referral:
3.10%
Search:
14.37%
Social:
1.75%
Paid:
0%

Desktop vs Mobile

Desktop:
68.90%
Mobile:
31.10%

Total Visits Last 3 Months

282.4K
DEC
225.7K
JAN
222K
FEB

Visitors by country

Country
Users%
 
United States 18.98%
 
Mauritius 12.86%
 
United Kingdom 7.16%
 
Brazil 6.48%
 
Australia 6.03%

Which sites are competitors to frzyc.github.io?

Websites similar to frzyc.github.io 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
pocketpair.jp
Compare >24.1K
Last update was 94 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with frzyc.github.io 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:
4
Bing Index:
40

  ▼

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:
  frzyc.github.io
Rank:
(Rank based on keywords, cost and organic traffic)
  551,216
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  2,002
Organic Traffic:
(Number of visitors coming from top 20 search results)
  2,589
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $27.00
Full SEMrush Report >>

Revenue report ▼

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

How much would frzyc.github.io make?

Daily Revenue:
$210.53
Monthly Revenue:
$6,315.90
Yearly Revenue:
$76,843.45
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 11,502$55.55
 
Australia 3,656$17.62
 
United Kingdom 4,336$11.62
 
Brazil 3,925$5.22
 
Mauritius 7,790$0.62

Loss of money due to Adblock?

Daily Revenue Loss:
$15.71
Monthly Revenue Loss:
$471.26
Yearly Revenue Loss:
$5,733.72
Daily Pageviews Blocked:
3,887
Monthly Pageviews Blocked:
116,598
Yearly Pageviews Blocked:
1,418,611

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 2,070$10.00
 
Australia 731$3.52
 
United Kingdom 694$1.86
 
Brazil 236$0.31
 
Mauritius 156$0.01

How much is frzyc.github.io worth?

Website Value:
$207.5K

Ad Experience Report ▼

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

Mobile summary

Root domain:
frzyc.github.io
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:
frzyc.github.io
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:
frzyc.github.io
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 frzyc.github.io hosted? ▼

Frzyc.github.io may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
2606:50c0:8003::153, 185.199.108.153
ASN:
AS54113 
ISP:
Fastly 
Server Location:
California, CA
United States, US
 

Other sites hosted on 185.199.108.153

How fast does frzyc.github.io load? ▼

The average loading time of frzyc.github.io is 49 ms. The Desktop speed index is 77 and mobile speed index is 65.
Average Load Time:
49 ms

Page Speed (Google PageSpeed Insights) - Desktop

77
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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)28ms 41% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 41% 30% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 30% 28% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 28%
Time To First Byte (TTFB)340ms 93% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 93% 4% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 4% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)1.6s 81% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 81% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
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)599ms 32% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 32% 36% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 36% 31% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 31%
Largest Contentful Paint (LCP)2.7s 71% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 71% 17% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 17% 10% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 10%

Origin Data

All pages served from this origin have an SLOW 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)28ms 41% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 41% 30% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 30% 28% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 28%
Time To First Byte (TTFB)340ms 93% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 93% 4% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 4% 1% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 1%
First Contentful Paint (FCP)1.6s 81% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 81% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 6% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 6%
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)599ms 32% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 32% 36% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 36% 31% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 31%
Largest Contentful Paint (LCP)2.7s 71% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 71% 17% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 17% 10% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 10%

Lab Data

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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay 160 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 2.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint 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
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 Interactive 2.7 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 Time 150 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.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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

Page Speed (Google PageSpeed Insights) - Mobile

65
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a SLOW 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)86ms 41% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 15% 11% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 11% 73% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 73%
Time To First Byte (TTFB)392ms 93% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 91% 5% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 5% 2% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)2.5s 81% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 56% 25% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 25% 18% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 18%
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%
Interactive To Next Paint (INP)846ms 32% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 28% 29% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 29% 41% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 41%
Largest Contentful Paint (LCP)4.1s 71% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 43% 29% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 29% 27% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 27%

Origin Data

All pages served from this origin have an SLOW 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)86ms 15% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 15% 11% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 11% 73% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 73%
Time To First Byte (TTFB)392ms 91% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 91% 5% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 5% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)2.5s 56% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 56% 25% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 25% 18% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 18%
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%
Interactive To Next Paint (INP)846ms 28% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 28% 29% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 29% 41% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 41%
Largest Contentful Paint (LCP)4.1s 43% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 43% 29% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 29% 27% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 27%

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
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
Largest Contentful Paint 10.6 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
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
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
First Contentful Paint 2.1 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Speed Index 3.6 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Max Potential First Input Delay 190 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 240 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
Time to Interactive 12.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
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

Does frzyc.github.io 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 frzyc.github.io are reduced by 47%.
frzyc.github.io use gzip compression.
Original size: 1.5 KB
Compressed size: 809 B
File reduced by: 727 B (47%)

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

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. frzyc.github.io supports HTTPS.
 frzyc.github.io supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.github.io
Organization:
Location:
Issuer: Sectigo RSA Domain Validation Secure Server CA
Valid from: Mar 7 00:00:00 2025 GMT
Valid until: Mar 7 23:59:59 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: Sectigo RSA Domain Validation Secure Server CA
Organization: Sectigo Limited
Location: Salford, Greater Manchester, GB
Issuer: USERTrust RSA Certification Authority
Valid from: Nov 2 00:00:00 2018 GMT
Valid until: Dec 31 23:59:59 2030 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: USERTrust RSA Certification Authority
Organization: The USERTRUST Network
Location: Jersey City, New Jersey, US
Issuer: AAA Certificate Services
Valid from: Mar 12 00:00:00 2019 GMT
Valid until: Dec 31 23:59:59 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.
 frzyc.github.io 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: GitHub.com
content-type: text/html; charset=utf-8
permissions-policy: interest-cohort=()
last-modified: Wed, 11 Sep 2024 18:29:26 GMT
access-control-allow-origin: *
etag: W/"66e1e186-600"
expires: Wed, 12 Mar 2025 16:03:09 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: 887E:173C:160BFB8:186B5EE:67D1ADE4
accept-ranges: bytes
date: Wed, 12 Mar 2025 15:53:09 GMT
via: 1.1 varnish
age: 0
x-served-by: cache-chi-kigq8000130-CHI
x-cache: MISS
x-cache-hits: 0
x-timer: S1741794789.991715,VS0,VE36
vary: Accept-Encoding
x-fastly-request-id: 6bb0f3fa442eaffe853e0410a6da4400f3b54766
content-length: 809

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:50c0:8000::153 3536
AAAA 2606:50c0:8002::153 3536
AAAA 2606:50c0:8001::153 3536
AAAA 2606:50c0:8003::153 3536
A 185.199.110.153 3536
A 185.199.111.153 3536
A 185.199.108.153 3536
A 185.199.109.153 3536

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.
WhoIs:
 

Malformed request.
>>> Last update of WHOIS database: 2025-03-12T15:54:11Z