cuffed.dating Cuffed.dating

   
Cuffed - One match at a time

Domain Summary

What percent of global Internet users visit Cuffed.dating?

• 2.3E-6% of global Internet users visit Cuffed.dating

How many people visit Cuffed.dating each day?

• Cuffed.dating receives approximately 115 visitors and 206 page impressions per day.

Which countries does Cuffed.dating receive most of its visitors from?

• Cuffed.dating is mostly visited by people located in United States.

How much Cuffed.dating can earn?

• Cuffed.dating should earn about $1.00/day from advertising revenue.

What is Cuffed.dating estimated value?

• Estimated value of Cuffed.dating is $903.73.

What IP addresses does Cuffed.dating resolve to?

• Cuffed.dating resolves to the IP addresses 216.150.1.193.

Where are Cuffed.dating servers located in?

• Cuffed.dating has servers located in United States.

cuffed.dating Profile

Title:Cuffed - One match at a time Description:Cuffed dating app - One match at a time
Edit Site Info

What technologies does cuffed.dating use?

These are the technologies used at cuffed.dating. cuffed.dating has a total of 3 technologies installed in 3 different categories.
Security
HSTS HSTS
Performance
Priority Hints Priority Hints
Web Servers
Vercel Vercel

cuffed.dating Traffic Analysis

This website is viewed by an estimated 115 visitors daily, generating a total of 206 pageviews. This equates to about 3.5K monthly visitors. Cuffed.dating traffic has increased by 83.89% compared to last month.
Daily Visitors115
83.89%
Monthly Visits3.5K
83.89%
Pages per Visit1.79
10.14%
Visit duration00:24
580%
Bounce Rate45.36%
22.03%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
115
Monthly Visits:
3,485
Pages per Visit:
1.79
Daily Pageviews:
206
Avg. visit duration:
00:24
Bounce rate:
45.36%
Global Reach:
2.3E-6%
Monthly Visits (SEMrush):
879
Monthly Unique Visitors (SEMrush):
879
Monthly Visits (SimilarWeb):
3,484
HypeRank:
n/a
SEMrush Rank:
1,922,811
SimilarWeb Rank:
4,781,938
*All traffic values are estimates only.

Traffic sources

Direct:
0%
Referral:
0%
Search:
100.00%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

3K
JUN
1.9K
JUL
3.5K
AUG

Visitors by country

Country
Users%
 
United States 100.00%
Last update was 25 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with cuffed.dating in any way. Only publicly available statistics data are displayed.

  ▼

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:
  cuffed.dating
Rank:
(Rank based on keywords, cost and organic traffic)
  1,922,811
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  27
Organic Traffic:
(Number of visitors coming from top 20 search results)
  382
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $158.00
Full SEMrush Report >>

Revenue report ▼

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

How much would cuffed.dating make?

Daily Revenue:
$1.00
Monthly Revenue:
$30.00
Yearly Revenue:
$365.00
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 206$0.99

Loss of money due to Adblock?

Daily Revenue Loss:
$0.18
Monthly Revenue Loss:
$5.37
Yearly Revenue Loss:
$65.37
Daily Pageviews Blocked:
37
Monthly Pageviews Blocked:
1,112
Yearly Pageviews Blocked:
13,534

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 37$0.18

How much is cuffed.dating worth?

Website Value:
$0.9K

Ad Experience Report ▼

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

Mobile summary

Root domain:
cuffed.dating
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:
cuffed.dating
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:
cuffed.dating
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 cuffed.dating hosted? ▼

Cuffed.dating may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
216.150.1.193
ASN:
AS16509 
ISP:
Amazon.com, Inc. 
Server Location:

United States, US
 

Other sites hosted on 216.150.1.193

How fast does cuffed.dating load? ▼

The average loading time of cuffed.dating is 181 ms. The Desktop speed index is 98 and mobile speed index is 66.
Average Load Time:
181 ms

Page Speed (Google PageSpeed Insights) - Desktop

98
0-49 50-89 90-100 i

Field Data

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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0ms) Largest Contentful Paint (LCP) 0%

Origin Data

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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0ms) Largest Contentful Paint (LCP) 0%

Lab Data

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
INP breakdown  
Start investigating with the longest subpart. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
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 Meaningful Paint  
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
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
Max Potential First Input Delay 50 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 Interactive 1.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
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 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
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
Speed Index 0.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric

Page Speed (Google PageSpeed Insights) - Mobile

66
0-49 50-89 90-100 i

Field Data

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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0s) Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0s ~ 0s) Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0s) Largest Contentful Paint (LCP) 0%

Origin Data

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.

Cumulative Layout Shift (CLS)0 0% of loads for this page have a fast (<0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have an average (0s ~ 0s) Cumulative Layout Shift (CLS) 0% 0% of loads for this page have a slow (>0s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)0 0% of loads for this page have a fast (<0s) Time To First Byte (TTFB) 0% 0% of loads for this page have an average (0s ~ 0s) Time To First Byte (TTFB) 0% 0% of loads for this page have a slow (>0s) Time To First Byte (TTFB) 0%
First Contentful Paint (FCP)0 0% of loads for this page have a fast (<0s) First Contentful Paint (FCP) 0% 0% of loads for this page have an average (0s ~ 0s) First Contentful Paint (FCP) 0% 0% of loads for this page have a slow (>0s) First Contentful Paint (FCP) 0%
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)0 0% of loads for this page have a fast (<0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have an average (0s ~ 0s) Interactive To Next Paint (INP) 0% 0% of loads for this page have a slow (>0s) Interactive To Next Paint (INP) 0%
Largest Contentful Paint (LCP)0 0% of loads for this page have a fast (<0s)Largest Contentful Paint (LCP) 0% 0% of loads for this page have an average (0s ~ 0s)Largest Contentful Paint (LCP) 0% 0% of loads for this page have a slow (>0s)Largest Contentful Paint (LCP) 0%

Lab Data

Max Potential First Input Delay 30 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 Interactive 8.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
Speed Index 5.9 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
First Meaningful Paint  
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
LCP request discovery  
Optimize LCP by making the LCP image from the HTML immediately, and discoverable avoiding lazy-loading
Largest Contentful Paint 8.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
INP breakdown  
Start investigating with the longest subpart. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
First Contentful Paint 2.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
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
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

Does cuffed.dating 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 cuffed.dating are reduced by 83%.
cuffed.dating use br compression.
Original size: 23.38 KB
Compressed size: 3.87 KB
File reduced by: 19.52 KB (83%)

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. cuffed.dating supports HTTPS.
 cuffed.dating supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.cuffed.dating
Organization:
Location:
Issuer: R13
Valid from: Aug 24 16:20:45 2025 GMT
Valid until: Nov 22 16:20:44 2025 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R13
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.
 cuffed.dating 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: Fri, 19 Sep 2025 23:03:22 GMT
location: https://www.cuffed.dating/
refresh: 0;url=https://www.cuffed.dating/
server: Vercel
strict-transport-security: max-age=63072000
x-vercel-id: fra1::9zvc5-1758323002404-42690c0af991

HTTP/2 200 
accept-ranges: bytes
access-control-allow-origin: *
age: 2424534
cache-control: public, max-age=0, must-revalidate
content-disposition: inline
content-encoding: br
content-type: text/html; charset=utf-8
date: Fri, 19 Sep 2025 23:03:22 GMT
etag: "447cb1b51008346af017773dff9cedb8"
last-modified: Fri, 22 Aug 2025 21:34:27 GMT
server: Vercel
strict-transport-security: max-age=63072000
x-matched-path: /
x-vercel-cache: HIT
x-vercel-id: fra1::64ww4-1758323002509-25c1187ae55c
content-length: 3958

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 216.150.1.193 1764
A 216.150.16.193 1764