diarly.app Diarly.app

   
Diarly — Secure, simple & beautiful diary app.

Domain Summary

What is the traffic rank for Diarly.app?

• Diarly.app ranks #1,561,503 globally on HypeStat.

What percent of global Internet users visit Diarly.app?

1.14E-5% of global Internet users visit Diarly.app

How many people visit Diarly.app each day?

• Diarly.app receives approximately 560 visitors and 944 page impressions per day.

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

• Diarly.app is mostly visited by people located in United States,India,United Kingdom.

How much Diarly.app can earn?

• Diarly.app should earn about $3.13/day from advertising revenue.

What is Diarly.app estimated value?

• Estimated value of Diarly.app is $2,904.70.

What IP addresses does Diarly.app resolve to?

• Diarly.app resolves to the IP addresses 104.198.14.52.

Where are Diarly.app servers located in?

• Diarly.app has servers located in The Dalles, Oregon, 97058, United States.

diarly.app Profile

Title:Diarly — Secure, simple & beautiful diary app. Description:Experience journaling in a whole new way.
Category:Computers Electronics and Technology / Other Computers Electronics and Technology

What technologies does diarly.app use?

These are the technologies used at diarly.app. diarly.app has a total of 5 technologies installed in 7 different categories.

diarly.app Traffic Analysis

Diarly.app is ranked #1,561,503 in the world. This website is viewed by an estimated 560 visitors daily, generating a total of 0.9K pageviews. This equates to about 17K monthly visitors. Diarly.app traffic has decreased by 71.13% compared to last month.
Daily Visitors560
67.23%
Monthly Visits17K
71.13%
Pages per Visit1.69
30.37%
Visit duration00:38
917.39%
Bounce Rate37.39%
20.53%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
560
Monthly Visits:
16,968
Pages per Visit:
1.69
Daily Pageviews:
944
Avg. visit duration:
00:38
Bounce rate:
37.39%
Global Reach:
1.14E-5%
Monthly Visits (SEMrush):
3,241
Monthly Unique Visitors (SEMrush):
2,551
Monthly Visits (SimilarWeb):
16,465
HypeRank:
1,561,503
SEMrush Rank:
1,405,510
SimilarWeb Rank:
1,561,503
*All traffic values are estimates only.

Traffic sources

Direct:
63.71%
Referral:
14.35%
Search:
21.94%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

9.2K
MAY
58.8K
JUN
17K
JUL

Visitors by country

Country
Users%
 
United States 54.89%
 
India 15.69%
 
United Kingdom 11.64%
 
Germany 11.21%
 
France 3.78%

Which sites are competitors to diarly.app?

Websites similar to diarly.app 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.
Last update was 32 days ago
     
This can take up to 60 seconds. Please wait...

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

Revenue report

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

How much would diarly.app make?

Daily Revenue:
$3.13
Monthly Revenue:
$93.90
Yearly Revenue:
$1,142.45
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 518$2.50
 
United Kingdom 110$0.29
 
Germany 106$0.15
 
India 148$0.06
 
France 36$0.02

Loss of money due to Adblock?

Daily Revenue Loss:
$0.56
Monthly Revenue Loss:
$16.76
Yearly Revenue Loss:
$203.88
Daily Pageviews Blocked:
187
Monthly Pageviews Blocked:
5,608
Yearly Pageviews Blocked:
68,225

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 93$0.45
 
United Kingdom 18$0.05
 
Germany 31$0.04
 
India 41$0.02
 
France 4$0.00

How much is diarly.app worth?

Website Value:
$2.9K

Ad Experience Report

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

Mobile summary

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

Diarly.app may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
104.198.14.52
ASN:
AS396982 
ISP:
Google LLC 
Server Location:
The Dalles
Oregon, OR
97058
United States, US
 

Other sites hosted on 104.198.14.52

How fast does diarly.app load?

The average loading time of diarly.app is 622 ms. The Desktop speed index is 96 and mobile speed index is 80.
Average Load Time:
622 ms

Page Speed (Google PageSpeed Insights) - Desktop

96
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)4ms 94% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 94% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)817ms 73% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 73% 22% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 22% 4% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 4%
First Contentful Paint (FCP)1.1s 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 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)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)1.3s 94% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 94% 4% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 4% 0% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 0%

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)4ms 94% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 94% 3% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 3% 1% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 1%
Time To First Byte (TTFB)817ms 73% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 73% 22% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 22% 4% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 4%
First Contentful Paint (FCP)1.1s 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 93% 5% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 5% 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)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)1.3s 94% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 94% 4% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 4% 0% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 0%

Lab Data

Time to Interactive 1.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 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
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 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
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 1.1 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 110 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.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
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

80
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 94% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 97% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.3s 73% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 51% 33% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 33% 14% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 14%
First Contentful Paint (FCP)1.8s 93% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 74% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 8% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 8%
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.2s 94% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 81% 13% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 13% 5% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 5%

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 97% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 97% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 0% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 0%
Time To First Byte (TTFB)1.3s 51% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 51% 33% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 33% 14% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 14%
First Contentful Paint (FCP)1.8s 74% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 74% 16% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 16% 8% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 8%
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.2s 81% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 81% 13% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 13% 5% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 5%

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
Total Blocking Time 50 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
Largest Contentful Paint 5.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Time to Interactive 5.0 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 2.5 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 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
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
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 breakdown  
Start investigating with the longest subpart. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs

Does diarly.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 diarly.app are reduced by 79%.
diarly.app use br compression.
Original size: 53.98 KB
Compressed size: 10.83 KB
File reduced by: 43.15 KB (79%)

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. diarly.app supports HTTPS.
 diarly.app supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: diarly.app
Organization:
Location:
Issuer: E6
Valid from: Aug 16 17:23:48 2025 GMT
Valid until: Nov 14 17:23:47 2025 GMT
Authority: CA:FALSE
Keysize:
Common Name: E6
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:

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.
 diarly.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.
accept-ranges: bytes
age: 13164
cache-control: public,max-age=0,must-revalidate
cache-status: "Netlify Edge"; hit
content-encoding: br
content-type: text/html; charset=UTF-8
date: Thu, 04 Sep 2025 22:54:23 GMT
etag: "95f24da69a3fb36ae088f094c4d0bd6a-ssl-df"
server: Netlify
strict-transport-security: max-age=31536000
vary: Accept-Encoding
x-nf-request-id: 01K4BF0BX1M6XA4T38CSSBZ70T
content-length: 11089

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 104.198.14.52 3525