susu.bot Susu.bot

   
Susu AI

Domain Summary

What percent of global Internet users visit Susu.bot?

3.0E-6% of global Internet users visit Susu.bot

How many people visit Susu.bot each day?

• Susu.bot receives approximately 149 visitors and 197 page impressions per day.

How much Susu.bot can earn?

• Susu.bot should earn about $0.80/day from advertising revenue.

What is Susu.bot estimated value?

• Estimated value of Susu.bot is $677.46.

What IP addresses does Susu.bot resolve to?

• Susu.bot resolves to the IP addresses 76.76.21.21.

Where are Susu.bot servers located in?

• Susu.bot has servers located in Walnut, California, 91789, United States.

susu.bot Profile

Title:Susu AI
Description:Susu AI

What technologies does susu.bot use?

These are the technologies used at susu.bot. susu.bot has a total of 4 technologies installed in 4 different categories.

susu.bot Traffic Analysis

This website is viewed by an estimated 149 visitors daily, generating a total of 197 pageviews. This equates to about 4.5K monthly visitors. Susu.bot traffic has decreased by 45.42% compared to last month.
Daily Visitors149
28.83%
Monthly Visits4.5K
45.42%
Pages per Visit1.32
2.74%
Visit duration00:12
95.57%
Bounce Rate71.70%
6.32%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
149
Monthly Visits:
4,515
Pages per Visit:
1.32
Daily Pageviews:
197
Avg. visit duration:
00:12
Bounce rate:
71.70%
Global Reach:
3.0E-6%
Monthly Visits (SEMrush):
4,565
Monthly Unique Visitors (SEMrush):
4,090
HypeRank:
n/a
SEMrush Rank:
1,113,670
*All traffic values are estimates only.

Traffic sources

Direct:
4.38%
Referral:
59.72%
Search:
1.29%
Social:
34.61%
Paid:
0%

Desktop vs Mobile

Desktop:
87.93%
Mobile:
12.07%
Last update was 7 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with susu.bot 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:
1

 

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:
  susu.bot
Rank:
(Rank based on keywords, cost and organic traffic)
  1,113,670
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  60
Organic Traffic:
(Number of visitors coming from top 20 search results)
  932
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $14.00

Revenue report

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

How much would susu.bot make?

Daily Revenue:
$0.80
Monthly Revenue:
$24.00
Yearly Revenue:
$292.00
*All earnings values are estimates only.

How much is susu.bot worth?

Website Value:
$677.5

Ad Experience Report

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

Mobile summary

Root domain:
susu.bot
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:
susu.bot
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:
susu.bot
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 susu.bot hosted?

Susu.bot may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
76.76.21.21
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:
Walnut
California, CA
91789
United States, US
 

Other sites hosted on 76.76.21.21

How fast does susu.bot load?

The average loading time of susu.bot is 107 ms. The Desktop speed index is 45 and mobile speed index is 69.
Average Load Time:
107 ms

Page Speed (Google PageSpeed Insights) - Desktop

45
0-49 50-89 90-100 i

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)21ms 28% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 28% 56% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 56% 15% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 15%
Time To First Byte (TTFB)741ms 78% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 78% 19% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 19% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.0s 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)54ms 97% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 97% 1% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 1% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)2.1s 84% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 84% 13% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 13% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

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)21ms 28% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 28% 56% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 56% 15% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 15%
Time To First Byte (TTFB)741ms 78% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 78% 19% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 19% 2% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 2%
First Contentful Paint (FCP)1.0s 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)54ms 97% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 97% 1% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 1% 1% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 1%
Largest Contentful Paint (LCP)2.1s 84% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 84% 13% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 13% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

Lab Data

First Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
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
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
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
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
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
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
Time to Interactive 8.9 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
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
Max Potential First Input Delay 290 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 8.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
CSS Selector costs  
If Recalculate Style costs remain high, selector optimization can reduce them. with both high elapsed time and high slow-path %. Simpler selectors, fewer selectors, a smaller DOM, and a shallower DOM will all reduce matching costs. Optimize the selectors
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
Total Blocking Time 300 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
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
INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs

Page Speed (Google PageSpeed Insights) - Mobile

69
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)30ms 28% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 25% 36% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 36% 38% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 38%
Time To First Byte (TTFB)838ms 78% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 71% 24% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 24% 3% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)1.1s 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 1% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 1%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)145ms 97% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 88% 10% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 10% 1% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)2.1s 84% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 83% 13% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 13% 3% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 3%

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)30ms 25% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 25% 36% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 36% 38% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 38%
Time To First Byte (TTFB)838ms 71% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 71% 24% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 24% 3% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 3%
First Contentful Paint (FCP)1.1s 94% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 94% 3% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 3% 2% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 2%
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)145ms 88% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 88% 10% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 10% 1% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)2.1s 83% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 83% 12% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 12% 3% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 3%

Lab Data

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 Time 60 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
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
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
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
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
Speed Index 4.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
Time to Interactive 53.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
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 Paint 53.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
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
First Contentful Paint 2.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
Max Potential First Input Delay 80 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

Does susu.bot 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 susu.bot are reduced by 68%.
susu.bot use br compression.
Original size: 31.13 KB
Compressed size: 9.92 KB
File reduced by: 21.21 KB (68%)

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:
  UNKNOWN

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. susu.bot supports HTTPS.
 susu.bot supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: www.susu.bot
Organization:
Location:
Issuer: R10
Valid from: Feb 13 20:17:10 2025 GMT
Valid until: May 14 20:17:09 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R10
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Verify HTTP/2 Support

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 susu.bot 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.
cache-control: public, max-age=0, must-revalidate
content-type: text/plain
date: Tue, 25 Mar 2025 07:23:26 GMT
location: https://www.susu.bot/
refresh: 0;url=https://www.susu.bot/
server: Vercel
strict-transport-security: max-age=63072000
x-vercel-id: cle1::s7vrv-1742887406102-3748561ce44e

HTTP/2 200 
access-control-allow-origin: *
age: 1007751
cache-control: public, max-age=0, must-revalidate
content-disposition: inline
content-encoding: br
content-type: text/html; charset=utf-8
date: Tue, 25 Mar 2025 07:23:26 GMT
etag: W/"399a5934faa064eef86936888636efe6"
last-modified: Thu, 13 Mar 2025 15:27:34 GMT
server: Vercel
strict-transport-security: max-age=63072000
x-matched-path: /
x-vercel-cache: HIT
x-vercel-id: cle1::vhh7v-1742887406150-17feb74f3925

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
A 76.76.21.21 1619
NS dns1.registrar-servers.com 172620
NS dns2.registrar-servers.com 172620
HINFO 3600