fresse.org Fresse.org

   
Sebastian Freundt

Domain Summary

What percent of global Internet users visit Fresse.org?

• 4.0E-7% of global Internet users visit Fresse.org

How many people visit Fresse.org each day?

• Fresse.org receives approximately 20 visitors and 36 page impressions per day.

Which countries does Fresse.org receive most of its visitors from?

• Fresse.org is mostly visited by people located in United States,India,Czech Republic.

How much Fresse.org can earn?

• Fresse.org should earn about $0.08/day from advertising revenue.

What is Fresse.org estimated value?

• Estimated value of Fresse.org is $81.20.

What IP addresses does Fresse.org resolve to?

• Fresse.org resolves to the IP addresses 2606:50c0:8003::153, 185.199.108.153.

Where are Fresse.org servers located in?

• Fresse.org has servers located in California, United States.

fresse.org Profile

Title:Sebastian Freundt
Edit Site Info

What technologies does fresse.org use?

These are the technologies used at fresse.org. fresse.org has a total of 4 technologies installed in 4 different categories.
UI frameworks
Bootstrap Bootstrap
CDN
Fastly Fastly
PaaS
GitHub Pages GitHub Pages
Caching
Varnish Varnish

fresse.org Traffic Analysis

This website is viewed by an estimated 20 visitors daily, generating a total of 36 pageviews. This equates to about 606 monthly visitors.
Daily Visitors20
Monthly Visits606
Pages per Visit1.82
Visit duration00:11
Bounce Rate43.55%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
20
Monthly Visits:
606
Pages per Visit:
1.82
Daily Pageviews:
36
Avg. visit duration:
00:11
Bounce rate:
43.55%
Global Reach:
4.0E-7%
Monthly Visits (SimilarWeb):
600
HypeRank:
n/a
SEMrush Rank:
9,190,307
*All traffic values are estimates only.

Total Visits Last 3 Months

289
FEB
606
MAR
606
APR

Visitors by country

Country
Users%
 
United States 39.18%
 
India 34.45%
 
Czech Republic 26.37%
Last update was 183 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with fresse.org 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:
  fresse.org
Rank:
(Rank based on keywords, cost and organic traffic)
  9,190,307
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  2
Organic Traffic:
(Number of visitors coming from top 20 search results)
  5
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Full SEMrush Report >>

Revenue report ▼

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

How much would fresse.org make?

Daily Revenue:
$0.08
Monthly Revenue:
$2.40
Yearly Revenue:
$29.20
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
United States 14$0.07
 
India 12$0.00
 
Czech Republic 9$0.00

Loss of money due to Adblock?

Daily Revenue Loss:
$0.01
Monthly Revenue Loss:
$0.42
Yearly Revenue Loss:
$5.12
Daily Pageviews Blocked:
7
Monthly Pageviews Blocked:
209
Yearly Pageviews Blocked:
2,541

Daily revenue loss by country

 
CountryBlockedLost Money
 
United States 3$0.01
 
India 3$0.00
 
Czech Republic 1$0.00

How much is fresse.org worth?

Website Value:
$81.2

Ad Experience Report ▼

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

Mobile summary

Root domain:
fresse.org
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:
fresse.org
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:
fresse.org
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 fresse.org hosted? ▼

Fresse.org 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 fresse.org load? ▼

The average loading time of fresse.org is 245 ms. The Desktop speed index is 93 and mobile speed index is 89.
Average Load Time:
245 ms

Page Speed (Google PageSpeed Insights) - Desktop

93
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

INP by phase  
Start investigating with the longest phase. To reduce processing duration, , often JS. Delays can be minimized optimize the main-thread costs
Legacy JavaScript  
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Largest Contentful Paint 0.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
First Contentful Paint 0.5 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
Max Potential First Input Delay 20 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
Speed Index 2.9 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
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
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
Duplicated JavaScript  
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Time to Interactive 0.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

Page Speed (Google PageSpeed Insights) - Mobile

89
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

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
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
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
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 6.9 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
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 1.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
Legacy JavaScript  
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile features, unless you know you must support legacy browsers. Baseline Learn why most sites can deploy ES6+ code without transpiling
Largest Contentful Paint 2.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
Max Potential First Input Delay 20 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
Duplicated JavaScript  
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Does fresse.org 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 fresse.org are reduced by 64%.
fresse.org use gzip compression.
Original size: 4.7 KB
Compressed size: 1.69 KB
File reduced by: 3.01 KB (64%)

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. fresse.org supports HTTPS.
 fresse.org supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: www.fresse.org
Organization:
Location:
Issuer: R10
Valid from: Apr 25 11:21:09 2025 GMT
Valid until: Jul 24 11:21:08 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.
 fresse.org 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
location: https://www.fresse.org/
x-github-request-id: 3775:37D1B8:8110738:8E37521:682EBD62
accept-ranges: bytes
age: 0
date: Thu, 22 May 2025 06:00:02 GMT
via: 1.1 varnish
x-served-by: cache-chi-klot8100075-CHI
x-cache: MISS
x-cache-hits: 0
x-timer: S1747893602.205021,VS0,VE98
vary: Accept-Encoding
x-fastly-request-id: e7aae713b62a38ffad6456762108e7de5a2a44d7
content-length: 162

HTTP/2 200 
server: GitHub.com
content-type: text/html; charset=utf-8
last-modified: Thu, 12 Sep 2019 08:37:42 GMT
access-control-allow-origin: *
etag: W/"5d7a03d6-12d1"
expires: Thu, 22 May 2025 06:10:02 GMT
cache-control: max-age=600
content-encoding: gzip
x-proxy-cache: MISS
x-github-request-id: EE91:303F83:7A5AB94:8948FC4:682EBD62
accept-ranges: bytes
age: 0
date: Thu, 22 May 2025 06:00:02 GMT
via: 1.1 varnish
x-served-by: cache-chi-klot8100047-CHI
x-cache: MISS
x-cache-hits: 0
x-timer: S1747893602.324367,VS0,VE108
vary: Accept-Encoding
x-fastly-request-id: 2c92a2f9b856d36bb10386324ba89a985435f3e4
content-length: 1730

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
MX mx5.fresse.org 86400
MX mx3.fresse.org 86400
MX mx8.fresse.org 86400
TXT v=spf1 include:spf-a.fresse.org include:spf-b.fresse.org include:spf-ext.fresse.org -all 3600
SOA 172800
Mname ns9.fresse.org
Rname hostmaster.fresse.org
Serial Number 2022060501
Refresh 21400
Retry 3600
Expire 1728000
Minimum TTL 1800
AAAA 2606:50c0:8000::153 3533
AAAA 2606:50c0:8002::153 3533
AAAA 2606:50c0:8001::153 3533
AAAA 2606:50c0:8003::153 3533
A 185.199.111.153 3532
A 185.199.109.153 3532
A 185.199.108.153 3532
A 185.199.110.153 3532
NS ns9.fresse.org 3532
NS ns3.fresse.org 3532

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. Domain registration for this website began on September 19, 2004 and will expire on September 19, 2025 if not renewed. This website is now assigned through the registrar INWX GmbH. The WHOIS data for this website's domain was last updated on November 3, 2024.
Domain Created:
2004-09-19
Domain Expires:
2025-09-19
Domain Updated:
2024-11-03
Domain Age:
21 years 2 months 2 days
Domain Registrar:
INWX GmbH
Domain Owner:
REDACTED
WhoIs:
 

Domain Name: fresse.org
Registry Domain ID: a9436ea2ac6c4dc8be982f3e168e3825-LROR
Registrar WHOIS Server: inwx.de
Registrar URL: http://www.domrobot.com
Updated Date: 2024-11-03T07:52:52Z
Creation Date: 2004-09-19T07:52:42Z
Registry Expiry Date: 2025-09-19T07:52:42Z
Registrar: INWX GmbH
Registrar IANA ID: 1420
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +49.3098321212
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED
Registrant Name: REDACTED
Registrant Organization: 
Registrant Street: REDACTED
Registrant City: REDACTED
Registrant State/Province: 
Registrant Postal Code: REDACTED
Registrant Country: DE
Registrant Phone: REDACTED
Registrant Phone Ext: REDACTED
Registrant Fax: REDACTED
Registrant Fax Ext: REDACTED
Registrant Email: REDACTED
Registry Admin ID: REDACTED
Admin Name: REDACTED
Admin Organization: REDACTED
Admin Street: REDACTED
Admin City: REDACTED
Admin State/Province: REDACTED
Admin Postal Code: REDACTED
Admin Country: REDACTED
Admin Phone: REDACTED
Admin Phone Ext: REDACTED
Admin Fax: REDACTED
Admin Fax Ext: REDACTED
Admin Email: REDACTED
Registry Tech ID: REDACTED
Tech Name: REDACTED
Tech Organization: REDACTED
Tech Street: REDACTED
Tech City: REDACTED
Tech State/Province: REDACTED
Tech Postal Code: REDACTED
Tech Country: REDACTED
Tech Phone: REDACTED
Tech Phone Ext: REDACTED
Tech Fax: REDACTED
Tech Fax Ext: REDACTED
Tech Email: REDACTED
Name Server: ns3.fresse.org
Name Server: ns9.fresse.org
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/
>>> Last update of WHOIS database: 2025-05-22T06:01:08Z