weddingfy.app Weddingfy.app

   
Invitaciones Digitales de Boda | Weddingfy

Domain Summary

What is the traffic rank for Weddingfy.app?

• Weddingfy.app ranks #8,887,795 globally on HypeStat.

What percent of global Internet users visit Weddingfy.app?

1.2E-6% of global Internet users visit Weddingfy.app

How many people visit Weddingfy.app each day?

• Weddingfy.app receives approximately 59 visitors and 101 page impressions per day.

Which countries does Weddingfy.app receive most of its visitors from?

• Weddingfy.app is mostly visited by people located in Mexico,Argentina.

How much Weddingfy.app can earn?

• Weddingfy.app should earn about $0.03/day from advertising revenue.

What is Weddingfy.app estimated value?

• Estimated value of Weddingfy.app is $23.66.

What IP addresses does Weddingfy.app resolve to?

• Weddingfy.app resolves to the IP addresses 92.113.23.25.

Where are Weddingfy.app servers located in?

• Weddingfy.app has servers located in Frankfurt am Main, Hesse, 60313, Germany.

weddingfy.app Profile

Title:Invitaciones Digitales de Boda | Weddingfy Description:Las mejores invitaciones digitales de boda encuentralas en Weddingfy. Con música, RSVP, fotos y en sólo 24 horas. Muchos diseños disponibles. Invitaciones 100% Digitales.

What technologies does weddingfy.app use?

These are the technologies used at weddingfy.app. weddingfy.app has a total of 12 technologies installed in 8 different categories.

weddingfy.app Traffic Analysis

Weddingfy.app is ranked #8,887,795 in the world. This website is viewed by an estimated 59 visitors daily, generating a total of 101 pageviews. This equates to about 1.8K monthly visitors. Weddingfy.app traffic has decreased by 38.4% compared to last month.
Daily Visitors59
28.71%
Monthly Visits1.8K
38.4%
Pages per Visit1.70
25.44%
Visit duration00:12
95.57%
Bounce Rate54.13%
34.53%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
59
Monthly Visits:
1,788
Pages per Visit:
1.70
Daily Pageviews:
101
Avg. visit duration:
00:12
Bounce rate:
54.13%
Global Reach:
1.2E-6%
Monthly Visits (SEMrush):
1,577
Monthly Unique Visitors (SEMrush):
1,457
Monthly Visits (SimilarWeb):
1,738
HypeRank:
8,887,795
SEMrush Rank:
11,322,148
SimilarWeb Rank:
8,887,795
*All traffic values are estimates only.

Traffic sources

Direct:
54.98%
Referral:
0%
Search:
22.95%
Social:
22.07%
Paid:
0%

Desktop vs Mobile

Desktop:
55.68%
Mobile:
44.32%

Total Visits Last 3 Months

8.7K
JUN
2.9K
JUL
1.8K
AUG

Visitors by country

Country
Users%
 
Mexico 66.64%
 
Argentina 33.36%
Last update was 19 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with weddingfy.app 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:
  weddingfy.app
Rank:
(Rank based on keywords, cost and organic traffic)
  11,322,148
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  19
Organic Traffic:
(Number of visitors coming from top 20 search results)
  2
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00

Revenue report

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

How much would weddingfy.app make?

Daily Revenue:
$0.03
Monthly Revenue:
$0.90
Yearly Revenue:
$10.95
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Mexico 67$0.02
 
Argentina 34$0.01

Daily revenue loss by country

 
CountryBlockedLost Money
 
Mexico 6$0.00
 
Argentina 5$0.00

How much is weddingfy.app worth?

Website Value:
$23.7

Ad Experience Report

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

Mobile summary

Root domain:
weddingfy.app
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:
weddingfy.app
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:
weddingfy.app
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 weddingfy.app hosted?

Weddingfy.app may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
92.113.23.25
ASN:
AS47583 
ISP:
Hostinger International Limited 
Server Location:
Frankfurt am Main
Hesse, HE
60313
Germany, DE
 

Other sites hosted on 92.113.23.25

How fast does weddingfy.app load?

The average loading time of weddingfy.app is 732 ms. The Desktop speed index is 85 and mobile speed index is 49.
Average Load Time:
732 ms

Page Speed (Google PageSpeed Insights) - Desktop

85
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)1ms 82% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 82% 4% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 4% 13% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 13%
Time To First Byte (TTFB)1.6s 26% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 26% 50% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 50% 22% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 22%
First Contentful Paint (FCP)2.3s 53% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 53% 28% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 28% 17% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 17%
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)2.7s 73% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 73% 10% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 10% 15% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 15%

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)1ms 93% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 93% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 2% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 2%
Time To First Byte (TTFB)1.6s 47% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 47% 30% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 30% 22% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 22%
First Contentful Paint (FCP)2.2s 63% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 63% 23% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 23% 12% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 12%
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)64ms 99% of loads for this page have a fast (<200ms) Interaction To Next Paint (INP) 99% 0% of loads for this page have an average (200ms ~ 500ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>500ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)2.5s 73% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 73% 16% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 16% 10% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 10%

Lab Data

First Contentful Paint 1.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
Total Blocking Time 90 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 2.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index 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
Max Potential First Input Delay 100 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 1.7 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
Time to Interactive 3.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

Page Speed (Google PageSpeed Insights) - Mobile

49
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)0ms 82% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 87% 6% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 6% 6% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 6%
Time To First Byte (TTFB)1.7s 26% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 38% 42% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 42% 19% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 19%
First Contentful Paint (FCP)2.4s 53% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 48% 32% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 32% 19% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 19%
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)2.7s 73% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 69% 20% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 20% 10% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 10%

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)0ms 96% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 96% 0% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 0% 2% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 2%
Time To First Byte (TTFB)1.6s 37% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 37% 42% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 42% 20% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 20%
First Contentful Paint (FCP)2.5s 57% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 57% 25% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 25% 17% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 17%
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)107ms 93% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 93% 4% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 4% 1% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 1%
Largest Contentful Paint (LCP)3.0s 66% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 66% 19% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 19% 14% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 14%

Lab Data

Speed Index 6.1 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Time to Interactive 14.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
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
INP breakdown  
Start investigating with the longest subpart. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Total Blocking Time 380 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
Max Potential First Input Delay 210 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
First Contentful Paint 4.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint 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
Largest Contentful Paint 6.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

Does weddingfy.app 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 weddingfy.app are reduced by 65%.
weddingfy.app use br compression.
Original size: 25.77 KB
Compressed size: 8.91 KB
File reduced by: 16.86 KB (65%)

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. weddingfy.app supports HTTPS.
 weddingfy.app supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: weddingfy.app
Organization:
Location:
Issuer: R12
Valid from: Aug 23 20:52:45 2025 GMT
Valid until: Nov 21 20:52:44 2025 GMT
Authority: CA:FALSE
Keysize: 4096 Bits
Common Name: R12
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.
 weddingfy.app 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.
date: Mon, 15 Sep 2025 20:06:02 GMT
content-type: text/html
content-length: 795
location: https://www.weddingfy.app/
platform: hostinger
panel: hpanel
content-security-policy: upgrade-insecure-requests
server: hcdn
alt-svc: h3=":443"; ma=86400
x-hcdn-request-id: 9fbe64417eec7b343aa22c6e42b0b5d5-fra-edge1
x-hcdn-cache-status: EXPIRED
x-hcdn-upstream-rt: 0.281

HTTP/2 200 
date: Mon, 15 Sep 2025 20:06:03 GMT
content-type: text/html; charset=UTF-8
content-length: 9123
x-powered-by: PHP/8.2.27
content-encoding: br
platform: hostinger
panel: hpanel
content-security-policy: upgrade-insecure-requests
server: hcdn
alt-svc: h3=":443"; ma=86400
x-hcdn-request-id: 20b6e6a012283d7eb248bcb025216488-fra-edge2
x-hcdn-cache-status: DYNAMIC
x-hcdn-upstream-rt: 0.352
accept-ranges: bytes

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
NS ns1.dns-parking.com 69482
NS ns2.dns-parking.com 69482