bo.berlin Bo.berlin

   
Botanischer Garten und Botanisches Museum Berlin

Domain Summary

What is the traffic rank for Bo.berlin?

• Bo.berlin ranks #856,552 globally on HypeStat.

What percent of global Internet users visit Bo.berlin?

1.31E-5% of global Internet users visit Bo.berlin

How many people visit Bo.berlin each day?

• Bo.berlin receives approximately 646 visitors and 2,238 page impressions per day.

Which countries does Bo.berlin receive most of its visitors from?

• Bo.berlin is mostly visited by people located in Germany,Turkey,Netherlands.

How much Bo.berlin can earn?

• Bo.berlin should earn about $3.57/day from advertising revenue.

What is Bo.berlin estimated value?

• Estimated value of Bo.berlin is $3,542.77.

What IP addresses does Bo.berlin resolve to?

• Bo.berlin resolves to the IP addresses 160.45.63.21.

Where are Bo.berlin servers located in?

• Bo.berlin has servers located in Berlin, Land Berlin, 14195, Germany.

bo.berlin Profile

Title:Botanischer Garten und Botanisches Museum Berlin
Category:Travel and Tourism / Other Travel and Tourism

What technologies does bo.berlin use?

These are the technologies used at bo.berlin. bo.berlin has a total of 5 technologies installed in 5 different categories.

bo.berlin Traffic Analysis

Bo.berlin is ranked #856,552 in the world. This website is viewed by an estimated 646 visitors daily, generating a total of 2.2K pageviews. This equates to about 19.6K monthly visitors. Bo.berlin traffic has decreased by 8.18% compared to last month.
Daily Visitors646
5.01%
Monthly Visits19.6K
8.18%
Pages per Visit3.46
27.25%
Visit duration01:46
507.69%
Bounce Rate23.07%
87.92%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
646
Monthly Visits:
19,574
Pages per Visit:
3.46
Daily Pageviews:
2,238
Avg. visit duration:
01:46
Bounce rate:
23.07%
Global Reach:
1.31E-5%
Monthly Visits (SEMrush):
29,720
Monthly Unique Visitors (SEMrush):
25,818
Monthly Visits (SimilarWeb):
19,190
HypeRank:
856,552
SEMrush Rank:
1,593,787
SimilarWeb Rank:
856,552
*All traffic values are estimates only.

Traffic sources

Direct:
47.41%
Referral:
2.22%
Search:
50.37%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
49.67%
Mobile:
50.33%

Total Visits Last 3 Months

15.1K
FEB
21.3K
MAR
19.6K
APR

Visitors by country

Country
Users%
 
Germany 66.86%
 
Turkey 6.79%
 
Netherlands 6.41%
 
Belarus 5.56%
 
Sweden 3.35%

Which sites are competitors to bo.berlin?

Websites similar to bo.berlin 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 24 days ago
     
This can take up to 60 seconds. Please wait...

*HypeStat.com is not promoting or affiliated with bo.berlin 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:
  bo.berlin
Rank:
(Rank based on keywords, cost and organic traffic)
  1,593,787
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  36
Organic Traffic:
(Number of visitors coming from top 20 search results)
  426
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 $3.6 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $107.1 and annual gross revenue of approximately $1.3K. Based on these figures, the site's net worth is estimated at around $3.5K.

How much would bo.berlin make?

Daily Revenue:
$3.57
Monthly Revenue:
$107.10
Yearly Revenue:
$1,303.05
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Germany 1,496$2.09
 
Netherlands 143$0.27
 
Sweden 75$0.10
 
Belarus 124$0.07
 
Turkey 152$0.03

Loss of money due to Adblock?

Daily Revenue Loss:
$0.69
Monthly Revenue Loss:
$20.74
Yearly Revenue Loss:
$252.28
Daily Pageviews Blocked:
502
Monthly Pageviews Blocked:
15,072
Yearly Pageviews Blocked:
183,381

Daily revenue loss by country

 
CountryBlockedLost Money
 
Germany 434$0.61
 
Netherlands 24$0.05
 
Sweden 21$0.03
 
Belarus 12$0.01
 
Turkey 11$0.00

How much is bo.berlin worth?

Website Value:
$3.5K

Ad Experience Report

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

Mobile summary

Root domain:
bo.berlin
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:
bo.berlin
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:
bo.berlin
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 bo.berlin hosted?

Bo.berlin may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
160.45.63.21
ASN:
AS680 
ISP:
Verein zur Foerderung eines Deutschen Forschungsnetzes e.V. 
Server Location:
Berlin
Land Berlin, BE
14195
Germany, DE
 

Other sites hosted on 160.45.63.21

There are no other sites hosted on this IP

How fast does bo.berlin load?

The average loading time of bo.berlin is 795 ms. The Desktop speed index is 90 and mobile speed index is 88.
Average Load Time:
795 ms

Page Speed (Google PageSpeed Insights) - Desktop

90
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST 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.

First Contentful Paint (FCP)1.6s 78% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 78% 15% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 15% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)2ms 100% of loads for this page have a fast (<100ms) First Input Delay (FID) 100% 0% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Origin Data

All pages served from this origin have an FAST 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.

First Contentful Paint (FCP)1.8s 76% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 76% 18% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 18% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)2ms 100% of loads for this page have a fast (<100ms) First Input Delay (FID) 100% 0% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

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
Time to Interactive 1.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
Largest Contentful Paint 1.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
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
Speed Index 2.2 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
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
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 1.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 1.0 s
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

88
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a FAST 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.

First Contentful Paint (FCP)1.4s 78% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 85% 9% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 9% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)13ms 97% of loads for this page have a fast (<100ms) First Input Delay (FID) 97% 2% of loads for this page have an average (100ms ~ 300ms) First Input Delay (FID) 2% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 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.

First Contentful Paint (FCP)1.6s 81% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 81% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)13ms 100% of loads for this page have a fast (<100ms) First Input Delay (FID) 94% 5% of loads for this page have an average 100ms ~ 300ms) First Input Delay (FID) 5% 0% of loads for this page have a slow (>300ms) First Input Delay (FID) 0%

Lab Data

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
Time to Interactive 2.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
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
Largest Contentful Paint 2.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
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
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
First Meaningful Paint 2.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful 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
Speed Index 4.7 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric

Does bo.berlin 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 bo.berlin are reduced by 63%.
bo.berlin use gzip compression.
Original size: 122.19 KB
Compressed size: 45.11 KB
File reduced by: 77.07 KB (63%)

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. bo.berlin supports HTTPS.
 bo.berlin supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: bgbm-bo.bgbm.fu-berlin.de
Organization: Freie Universit\C3\A4t Berlin
Location: Berlin, DE
Issuer: Sectigo RSA Organization Validation Secure Server CA
Valid from: Dec 19 00:00:00 2023 GMT
Valid until: Dec 18 23:59:59 2024 GMT
Authority: CA:FALSE
Keysize: 4096 Bits
Common Name: bgbm-bo.bgbm.fu-berlin.de
Organization: Freie Universit\C3\A4t Berlin
Location: Berlin, DE
Issuer: Sectigo RSA Organization Validation Secure Server CA
Valid from: Dec 19 00:00:00 2023 GMT
Valid until: Dec 18 23:59:59 2024 GMT
Authority: CA:FALSE
Keysize: 4096 Bits
Common Name: Sectigo RSA Organization Validation Secure Server CA
Organization: Sectigo Limited
Location: Salford, Greater Manchester, GB
Issuer: USERTrust RSA Certification Authority
Valid from: Nov 2 00:00:00 2018 GMT
Valid until: Dec 31 23:59:59 2030 GMT
Authority: CA:TRUE
Keysize: 2048 Bits
Common Name: USERTrust RSA Certification Authority
Organization: The USERTRUST Network
Location: Jersey City, New Jersey, US
Issuer: AAA Certificate Services
Valid from: Mar 12 00:00:00 2019 GMT
Valid until: Dec 31 23:59:59 2028 GMT
Authority: CA:TRUE
Keysize: 4096 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.
 bo.berlin does not support 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: Tue, 21 May 2024 22:54:01 GMT
Server: Apache/2.4.38 (Debian)
Set-Cookie: PHPSESSID=uo22ps2nd0j1g15imp2tps5uoq; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
Vary: Accept-Encoding
Content-Encoding: gzip
Content-Length: 46195
Content-Type: text/html; charset=UTF-8

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 relay2.zedat.fu-berlin.de 86400
TXT v=spf1 include:_spf.fu-berlin.de ~all 86400
TXT google-site-verification=BRO_fSS7cyb7gG44QS8cGeMo6qeSHgikVfOozcfuas4 86400
CAA sectigo.com 86400
CAA ; 86400
CAA mailto:certificate@fu-berlin.de 86400
SOA 86400
Mname ns1.fu-berlin.de
Rname hostmaster.zedat.fu-berlin.de
Serial Number 2024040201
Refresh 10800
Retry 3600
Expire 2419200
Minimum TTL 3600
A 160.45.63.21 86316
NS ns2.fu-berlin.de 14316
NS ns3.fu-berlin.de 14316
NS dns-2.dfn.de 14316
NS ns1.fu-berlin.de 14316

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 November 12, 2020 and will expire on November 12, 2024 if not renewed. This website is now assigned through the registrar COREhub, S.R.L.. The WHOIS data for this website's domain was last updated on June 15, 2024.
Domain Created:
2020-11-12
Domain Expires:
2024-11-12
Domain Age:
3 years 7 months 3 days
Domain Registrar:
COREhub, S.R.L.
Domain Owner:
Freie Universitaet Berlin
WhoIs:
 

Domain Name: bo.berlin
Registry Domain ID: D0000520974-BERLIN
Registrar WHOIS Server: whois.corehub.net
Registrar URL: http://corehub.net
Updated Date:
Creation Date: 2020-11-12T12:18:00.491Z
Registrar Registration Expiration Date: 2024-11-12T12:18:00.491Z
Registrar: COREhub, S.R.L.
Registrar IANA ID: 15
Registrar Abuse Contact Email: email
Registrar Abuse Contact Phone: +34.931807144
Reseller: CORE-132 (DFN Verein)
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: 
Registrant Name: 
Registrant Organization: Freie Universitaet Berlin
Registrant Street: 
Registrant City: 
Registrant State/Province:
Registrant Postal Code: 
Registrant Country: DE
Registrant Phone: 
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: https://corehub.net/whoiscontact/
Registry Admin ID: 
Admin Name: 
Admin Organization: 
Admin Street: 
Admin City: 
Admin State/Province: 
Admin Postal Code: 
Admin Country: 
Admin Phone: 
Admin Phone Ext: 
Admin Fax: 
Admin Fax Ext: 
Admin Email: https://corehub.net/whoiscontact/
Registry Tech ID: 
Tech Name: 
Tech Organization: 
Tech Street: 
Tech City: 
Tech State/Province: 
Tech Postal Code: 
Tech Country: 
Tech Phone: 
Tech Phone Ext: 
Tech Fax: 
Tech Fax Ext: 
Tech Email: https://corehub.net/whoiscontact/
Registry Tech 2 ID: 
Tech 2 Name: 
Tech 2 Organization: 
Tech 2 Street: 
Tech 2 City: 
Tech 2 State/Province: 
Tech 2 Postal Code: 
Tech 2 Country: 
Tech 2 Phone: 
Tech 2 Phone Ext: 
Tech 2 Fax: 
Tech 2 Fax Ext: 
Tech 2 Email: https://corehub.net/whoiscontact/
Name Server: ns2.fu-berlin.de
Name Server: ns1.fu-berlin.de
Name Server: ns3.fu-berlin.de
Name Server: dns-2.dfn.de
DNSSEC: unsigned
IDN Tag:
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of Whois database: 2024-05-21T22:55:06.450Z