berlinerdom.de Website Information
Daily Unique Visits: 11,587
Daily Page Views: 57,935
Income Per Day: $145
Estimated Value: $87,000
berlinerdom.de is registered under .DE top-level domain. Please check other sites in .DE zone.
No name server records were found.
and is probably hosted by Neue Medien Muennich GmbH. See the full list of other websites hosted by Neue Medien Muennich GmbH.
The highest website berlinerdom.de position in Alexa rank database was 31563 and the lowest rank position was 999617. Current position of berlinerdom.de in Alexa rank database is 117588.
Desktop speed score of berlinerdom.de (86/100) is better than the results of 82.23% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of berlinerdom.de (99/100) is better than the results of 79.46% of other sites and means that the page is mobile-friendly.
Mobile speed score of berlinerdom.de (63/100) is better than the results of 61.76% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
berlinerdom.de Alexa Rank
The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.
berlinerdom.de whois
WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.
Status: connect
berlinerdom.de server information
Servers Location
berlinerdom.de desktop page speed rank
Last tested: 2015-10-13
berlinerdom.de Desktop Speed Test Quick Summary
priority - 6Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking CSS resources. This causes a delay in rendering your page.
Optimize CSS Delivery of the following:
priority - 5Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
http://www.berlinerdom.de/components/com_joomfish/images/flags/en.gif (expiration not specified)
http://www.berlinerdom.de/images/stories/presse/ben_becker_1.jpg (expiration not specified)
http://www.berlinerdom.de/modules/mod_jflanguageselection.css (expiration not specified)
http://www.berlinerdom.de/templates/berlinerdom/css/template_css.css (expiration not specified)
http://www.berlinerdom.de/templates/berlinerdom/images/bg_start.jpg (expiration not specified)
http://www.berlinerdom.de/templates/berlinerdom/images/logo.gif (expiration not specified)
http://www.berlinerdom.de/templates/berlinerdom/images/navi-bg.gif (expiration not specified)
http://www.berlinerdom.de/templates/berlinerdom/images/searchbutton.png (expiration not specified)
http://connect.facebook.net/de_DE/all.js (20 minutes)
priority - 2Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 17.2KiB (69% reduction).
Compressing http://berlinerdom.de/ could save 6.1KiB (63% reduction).
Compressing http://www.berlinerdom.de/modules/mod_jflanguageselection.css could save 2KiB (57% reduction).
priority - 1Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 9.1KiB (39% reduction).
priority - 1Minify CSS
Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 7.1KiB (47% reduction).
Minifying http://www.berlinerdom.de/modules/mod_jflanguageselection.css could save 2.2KiB (62% reduction).
priority - 0Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 1.1KiB (2% reduction).
priority - 0Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 766B (8% reduction).
berlinerdom.de Desktop Resource Breakdown
Total Resources | 17 |
Number of Hosts | 7 |
Static Resources | 12 |
JavaScript Resources | 2 |
CSS Resources | 2 |
berlinerdom.de mobile page speed rank
Last tested: 2019-08-12
berlinerdom.de Mobile Speed Test Quick Summary
priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 4 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://cdn.rawgit.com/scottjehl/picturefill/3.0.2/dist/picturefill.min.js
https://www.berlinerdom.de/typo3temp/assets/js/9a38f34785.js?1523373255
https://www.berlinerdom.de/typo3conf/ext/berliner_…dist.min.js?1558449205
Optimize CSS Delivery of the following:
priority - 12Enable compression
Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.
Enable compression for the following resources to reduce their transfer size by 116.3KiB (51% reduction).
Compressing https://www.berlinerdom.de/typo3conf/ext/berliner_…SansOffcPro-Medium.ttf could save 53.8KiB (51% reduction).
Compressing https://www.berlinerdom.de/typo3conf/ext/berliner_…es/Public/Img/logo.svg could save 3.4KiB (65% reduction).
Compressing https://www.berlinerdom.de/typo3conf/ext/berliner_…nts/icomoon.ttf?duwhw1 could save 1.9KiB (41% reduction).
Compressing https://www.berlinerdom.de/typo3conf/ext/berliner_…/Public/Img/marker.svg could save 872B (50% reduction).
priority - 8Prioritize visible content
Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
priority - 6Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 54.5KiB (23% reduction).
Compressing https://www.berlinerdom.de/fileadmin/user_upload/B…uppelblick-desktop.jpg could save 19.1KiB (21% reduction).
Compressing https://www.berlinerdom.de/fileadmin/user_upload/B…herservice-desktop.jpg could save 14.4KiB (23% reduction).
priority - 2Leverage browser caching
Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:
https://www.berlinerdom.de/typo3conf/ext/berliner_…aSansOffcPro-Bold.woff (24 hours)
https://www.berlinerdom.de/typo3conf/ext/berliner_…es/Public/Img/logo.svg (24 hours)
https://www.berlinerdom.de/typo3conf/ext/berliner_…/Public/Img/marker.svg (24 hours)
priority - 0Minify HTML
Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 2.4KiB (20% reduction).
priority - 0Minify JavaScript
Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 104B (26% reduction).
berlinerdom.de Mobile Resource Breakdown
Total Resources | 38 |
Number of Hosts | 7 |
Static Resources | 32 |
JavaScript Resources | 5 |
CSS Resources | 1 |
berlinerdom.de mobile page usability
Last tested: 2019-08-12
berlinerdom.de Mobile Usability Test Quick Summary
priority - 0Size tap targets appropriately
Some of the links/buttons on your webpage may be too small for a user to easily tap on a touchscreen. Consider making these tap targets larger to provide a better user experience.
The following tap targets are close to other nearby tap targets and may need additional spacing around them.
<a href="/aktuelles/80-…all-auf-polen/">Mehr erfahren</a>
and 1 others are close to other tap targets.<a href="#">15</a>
is close to 1 other tap targets.<button id="calendar-next"></button>
is close to 1 other tap targets.<a href="/datenschutz/">hier</a>
is close to 1 other tap targets.berlinerdom.de HTML validation
Errors
Malformed byte sequence: “96”.
"......" Line: 5 Column: - 54
"......" Line: 126 Column: - 26
"......" Line: 141 Column: - 97
"......"
Malformed byte sequence: “e4”.
"......" Line: 92 Column: - 7
"......" Line: 93 Column: - 63
"......" Line: 96 Column: - 7
"......" Line: 104 Column: - 69
"......" Line: 109 Column: - 43
"......" Line: 111 Column: - 43
"......" Line: 117 Column: - 40
"......" Line: 117 Column: - 100
"......" Line: 117 Column: - 152
"......" Line: 132 Column: - 91
"......" Line: 132 Column: - 133
"......" Line: 141 Column: - 138
"......" Line: 141 Column: - 148
"......" Line: 141 Column: - 223
"......" Line: 150 Column: - 131
"......" Line: 171 Column: - 84
"......" Line: 181 Column: - 216
"......"
Saw “<?”. Probable cause: Attempt to use an XML processing instruction in HTML. (XML processing instructions are not supported in HTML.)
"...<?xml version="1..."
Almost standards mode doctype. Expected “<!DOCTYPE html>”.
"...-8859-1"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."
Internal encoding declaration “iso-8859-1” disagrees with the actual encoding of the document (“utf-8”).
"...ico" /> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> ..."
Bad value “text/html; charset=iso-8859-1” for attribute “content” on element “meta”: “iso-8859-1” is not a preferred encoding name. The preferred label for this encoding is “windows-1252”.
"...ico" /> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> ..."
The “cellpadding” attribute on the “table” element is obsolete. Use CSS instead.
"...ide"> <table class="blog" cellpadding="0" cellspacing="0"><tr><t..." Line: 210 Column: 40 - 92
"...ign="top"><table width="100%" cellpadding="0" cellspacing="0"><tr><t..."
The “cellspacing” attribute on the “table” element is obsolete. Use CSS instead.
"...ide"> <table class="blog" cellpadding="0" cellspacing="0"><tr><t..." Line: 210 Column: 40 - 92
"...ign="top"><table width="100%" cellpadding="0" cellspacing="0"><tr><t..."
The “valign” attribute on the “td” element is obsolete. Use CSS instead.
"...g="0"><tr><td valign="top"><div> ..." Line: 77 Column: 9 - 32
"...> <tr> <td valign="top" colspan="2"> <..." Line: 210 Column: 23 - 39
"...></tr><tr><td valign="top"><table..." Line: 210 Column: 97 - 145
"...g="0"><tr><td valign="top" width="100%" class="blog-titel"> <ta..." Line: 213 Column: 9 - 32
"...> <tr> <td valign="top" colspan="2"> <..."
Malformed byte sequence: “f6”.
"......" Line: 104 Column: - 76
"......" Line: 117 Column: - 10
"......" Line: 129 Column: - 506
"......" Line: 132 Column: - 36
"......" Line: 132 Column: - 48
"......" Line: 141 Column: - 195
"......" Line: 171 Column: - 333
"......" Line: 181 Column: - 166
"......" Line: 181 Column: - 209
"......" Line: 181 Column: - 290
"......" Line: 193 Column: - 103
"......" Line: 193 Column: - 112
"......" Line: 198 Column: - 21
"......" Line: 221 Column: - 10
"......" Line: 222 Column: - 2
"......"
Malformed byte sequence: “df”.
"......" Line: 104 Column: - 39
"......" Line: 109 Column: - 21
"......" Line: 109 Column: - 35
"......" Line: 109 Column: - 55
"......" Line: 111 Column: - 41
"......" Line: 117 Column: - 72
"......" Line: 181 Column: - 465
"......"
Malformed byte sequence: “fc”.
"......" Line: 85 Column: - 193
"......" Line: 91 Column: - 231
"......" Line: 91 Column: - 242
"......" Line: 91 Column: - 259
"......" Line: 108 Column: - 58
"......" Line: 111 Column: - 32
"......" Line: 129 Column: - 85
"......" Line: 141 Column: - 36
"......" Line: 141 Column: - 43
"......" Line: 147 Column: - 31
"......" Line: 171 Column: - 123
"......" Line: 171 Column: - 354
"......" Line: 193 Column: - 40
"......" Line: 198 Column: - 59
"......"
Malformed byte sequence: “a0”.
"......" Line: 91 Column: - 258
"......" Line: 91 Column: - 267
"......" Line: 91 Column: - 450
"......" Line: 94 Column: - 4
"......" Line: 96 Column: - 71
"......" Line: 132 Column: - 628
"......" Line: 197 Column: - 122
"......"
Malformed byte sequence: “e9”.
"......" Line: 187 Column: - 212
"......"
The “align” attribute on the “img” element is obsolete. Use CSS instead.
"...hr /> <p> <img style="width: 180px; height: 180px" src="images/stories/presse/kein_gepaeck.png" alt="kein_gepaeck.png" title="kein_gepaeck.png" width="180" height="180" align="default" /> </p>..." Line: 221 Column: 1 - 94
"... </p> <p> <img src="components/com_calendar/upload/8b50_WObachhp.jpg" border="0" alt="" align="right" /> </p> ..."
Malformed byte sequence: “dc”.
"......"
Malformed byte sequence: “d6”.
"......"
Malformed byte sequence: “84”.
"......"
Malformed byte sequence: “93”.
"......"
Table column 2 established by element “td” has no cells beginning in it.
"...> <tr> <td valign="top" colspan="2"> <..." Line: 213 Column: 9 - 32
"...> <tr> <td valign="top" colspan="2"> <..."
The “width” attribute on the “table” element is obsolete. Use CSS instead.
"...ign="top"><table width="100%" cellpadding="0" cellspacing="0"><tr><t..."
The “width” attribute on the “td” element is obsolete. Use CSS instead.
"...g="0"><tr><td valign="top" width="100%" class="blog-titel"> <ta..."
Warnings
The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.
"...tion"><li><img src="http://www.berlinerdom.de/components/com_joomfish/images/flags/en.gif" alt="English" title="English" border="0" class="langImg"/><a hre..." Line: 221 Column: 1 - 94
"... </p> <p> <img src="components/com_calendar/upload/8b50_WObachhp.jpg" border="0" alt="" align="right" /> </p> ..."
Empty heading.
"...</u></h1> <h1> </h1>..."
This document appears to be written in German. Consider adding “lang="de"” (or variant) to the “html” start tag.
"...onal.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head..."
berlinerdom.de similar domains
www.berlinerdom.net
www.berlinerdom.org
www.berlinerdom.info
www.berlinerdom.biz
www.berlinerdom.us
www.berlinerdom.mobi
www.erlinerdom.de
www.berlinerdom.de
www.verlinerdom.de
www.bverlinerdom.de
www.vberlinerdom.de
www.gerlinerdom.de
www.bgerlinerdom.de
www.gberlinerdom.de
www.herlinerdom.de
www.bherlinerdom.de
www.hberlinerdom.de
www.nerlinerdom.de
www.bnerlinerdom.de
www.nberlinerdom.de
www.brlinerdom.de
www.bwrlinerdom.de
www.bewrlinerdom.de
www.bwerlinerdom.de
www.bsrlinerdom.de
www.besrlinerdom.de
www.bserlinerdom.de
www.bdrlinerdom.de
www.bedrlinerdom.de
www.bderlinerdom.de
www.brrlinerdom.de
www.berrlinerdom.de
www.brerlinerdom.de
www.belinerdom.de
www.beelinerdom.de
www.berelinerdom.de
www.beerlinerdom.de
www.bedlinerdom.de
www.berdlinerdom.de
www.beflinerdom.de
www.berflinerdom.de
www.befrlinerdom.de
www.betlinerdom.de
www.bertlinerdom.de
www.betrlinerdom.de
www.berinerdom.de
www.berpinerdom.de
www.berlpinerdom.de
www.berplinerdom.de
www.beroinerdom.de
www.berloinerdom.de
www.berolinerdom.de
www.berkinerdom.de
www.berlkinerdom.de
www.berklinerdom.de
www.berlnerdom.de
www.berlunerdom.de
www.berliunerdom.de
www.berluinerdom.de
www.berljnerdom.de
www.berlijnerdom.de
www.berljinerdom.de
www.berlknerdom.de
www.berliknerdom.de
www.berlonerdom.de
www.berlionerdom.de
www.berlierdom.de
www.berliberdom.de
www.berlinberdom.de
www.berlibnerdom.de
www.berliherdom.de
www.berlinherdom.de
www.berlihnerdom.de
www.berlijerdom.de
www.berlinjerdom.de
www.berlimerdom.de
www.berlinmerdom.de
www.berlimnerdom.de
www.berlinrdom.de
www.berlinwrdom.de
www.berlinewrdom.de
www.berlinwerdom.de
www.berlinsrdom.de
www.berlinesrdom.de
www.berlinserdom.de
www.berlindrdom.de
www.berlinedrdom.de
www.berlinderdom.de
www.berlinrrdom.de
www.berlinerrdom.de
www.berlinrerdom.de
www.berlinedom.de
www.berlineedom.de
www.berlineredom.de
www.berlineerdom.de
www.berlineddom.de
www.berlinerddom.de
www.berlinefdom.de
www.berlinerfdom.de
www.berlinefrdom.de
www.berlinetdom.de
www.berlinertdom.de
www.berlinetrdom.de
www.berlinerom.de
www.berlinerxom.de
www.berlinerdxom.de
www.berlinerxdom.de
www.berlinersom.de
www.berlinerdsom.de
www.berlinersdom.de
www.berlinereom.de
www.berlinerdeom.de
www.berlinerrom.de
www.berlinerdrom.de
www.berlinerfom.de
www.berlinerdfom.de
www.berlinercom.de
www.berlinerdcom.de
www.berlinercdom.de
www.berlinerdm.de
www.berlinerdim.de
www.berlinerdoim.de
www.berlinerdiom.de
www.berlinerdkm.de
www.berlinerdokm.de
www.berlinerdkom.de
www.berlinerdlm.de
www.berlinerdolm.de
www.berlinerdlom.de
www.berlinerdpm.de
www.berlinerdopm.de
www.berlinerdpom.de
www.berlinerdo.de
www.berlinerdon.de
www.berlinerdomn.de
www.berlinerdonm.de
www.berlinerdoj.de
www.berlinerdomj.de
www.berlinerdojm.de
www.berlinerdok.de
www.berlinerdomk.de
berlinerdom.de Ping
Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.
berlinerdom.de TRACEROUTE
Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.