lilienthal.berlin Website Information
Daily Unique Visits: 1,119
Daily Page Views: 2,238
Income Per Day: $7
Estimated Value: $1,680
This website is located in Austria and is using following IP address 62.99.130.83. See the complete list of popular websites hosted in Austria.
lilienthal.berlin is registered under .BERLIN top-level domain. Please check other sites in .BERLIN zone.
Website lilienthal.berlin is using the following name servers:
- ns4.internex.at
- ns2.internex.at
- ns3.internex.at
- ns1.internex.at
and is probably hosted by interneX GmbH. See the full list of other websites hosted by interneX GmbH.
The highest website lilienthal.berlin position in Alexa rank database was 8075 and the lowest rank position was 997735. Current position of lilienthal.berlin in Alexa rank database is 641024.
Desktop speed score of lilienthal.berlin (71/100) is better than the results of 52.66% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of lilienthal.berlin (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 lilienthal.berlin (43/100) is better than the results of 22.8% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
lilienthal.berlin 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.
lilienthal.berlin 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.
Registry Domain ID: D0000262686-BERLIN
Registrar WHOIS Server: whois.psi-usa.info
Registrar URL: http://www.psi-usa.info
Updated Date: 2016-05-12T08:25:38Z
Creation Date: 2014-12-17T09:22:51Z
Registry Expiry Date: 2022-12-17T09:22:51Z
Registrar: PSI-USA, Inc. dba DOMAIN ROBOT
Registrar IANA ID: 151
Registrar Abuse Contact Email: domain-abuse@psi-usa.info
Registrar Abuse Contact Phone: +49.94159559482
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ns1.internex.at
Name Server: ns2.internex.at
Name Server: ns3.internex.at
Name Server: ns4.internex.at
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of Whois database: 2022-09-21T15:55:13Z
lilienthal.berlin server information
Servers Location
lilienthal.berlin desktop page speed rank
Last tested: 2019-02-12
lilienthal.berlin Desktop Speed Test Quick Summary
priority - 18Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://www.lilienthal.berlin/web/cache/1549967569…a8e839bd1a1f0f5590.css
https://fonts.googleapis.com/css?family=Lato:300,400,100,300,700,900
priority - 9Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
https://lilienthal.berlin/
https://www.lilienthal.berlin/
priority - 4Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 39.9KiB (16% reduction).
Compressing https://www.lilienthal.berlin/media/image/34/7c/c4…city-style_800x800.jpg could save 7.8KiB (15% reduction).
Compressing https://www.lilienthal.berlin/media/image/d6/87/d9…achel_02_D_800x800.jpg could save 3.1KiB (13% reduction).
Compressing https://www.lilienthal.berlin/media/image/78/6b/e6…d85e3952_1280x1280.jpg could save 2.3KiB (20% reduction).
priority - 3Reduce server response time
In our test, your server responded in 0.42 seconds.
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://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/187000…6122?v=2.8.40&r=stable (20 minutes)
https://maps.google.com/maps/api/js?v=3&libraries=…8wuANHvThPgPhRmDw1vY6Q (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://www.lilienthal.berlin/engine/Shopware/Plug…s/styles/ouibounce.css (7 days)
priority - 2Prioritize 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 - 1Minify 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 12.8KiB (33% reduction).
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…9/controllerName/index could save 1.3KiB (44% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…6/controllerName/index could save 1.3KiB (44% reduction) after compression.
Minifying https://player.vimeo.com/video/273888216 could save 1.3KiB (25% reduction) after compression.
Minifying https://player.vimeo.com/video/195466508 could save 1.3KiB (25% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…2/controllerName/index could save 1.3KiB (44% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…7/controllerName/index could save 1.3KiB (44% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…8/controllerName/index could save 1.2KiB (24% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…4/controllerName/index could save 748B (43% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…4/controllerName/index could save 594B (31% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…5/controllerName/index could save 354B (40% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…7/controllerName/index could save 248B (14% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…1/controllerName/index could save 244B (33% reduction) after compression.
lilienthal.berlin Desktop Resource Breakdown
Total Resources | 90 |
Number of Hosts | 19 |
Static Resources | 58 |
JavaScript Resources | 14 |
CSS Resources | 4 |
lilienthal.berlin mobile page speed rank
Last tested: 2019-02-12
lilienthal.berlin Mobile Speed Test Quick Summary
priority - 72Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://www.lilienthal.berlin/web/cache/1549967569…a8e839bd1a1f0f5590.css
https://fonts.googleapis.com/css?family=Lato:300,400,100,300,700,900
priority - 34Avoid landing page redirects
Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.
https://lilienthal.berlin/
https://www.lilienthal.berlin/
priority - 28Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 278.2KiB (63% reduction).
Compressing https://www.lilienthal.berlin/media/image/29/51/61…ory_m_1280x1280@2x.jpg could save 102.5KiB (69% reduction).
Compressing https://lilienthal.berlin/media/image/d8/03/b7/web…_M-P_20180718-1459.jpg could save 13.1KiB (18% 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 - 4Leverage 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://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/187000…6122?v=2.8.40&r=stable (20 minutes)
https://maps.google.com/maps/api/js?v=3&libraries=…8wuANHvThPgPhRmDw1vY6Q (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://www.lilienthal.berlin/engine/Shopware/Plug…s/styles/ouibounce.css (7 days)
priority - 2Reduce server response time
In our test, your server responded in 0.30 seconds.
priority - 1Minify 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 9.8KiB (30% reduction).
Minifying https://player.vimeo.com/video/273888216 could save 1.3KiB (25% reduction) after compression.
Minifying https://player.vimeo.com/video/195466508 could save 1.3KiB (25% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…0/controllerName/index could save 1.1KiB (44% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…1/controllerName/index could save 948B (42% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…3/controllerName/index could save 948B (42% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…5/controllerName/index could save 727B (39% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…5/controllerName/index could save 727B (39% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…3/controllerName/index could save 437B (30% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…1/controllerName/index could save 259B (15% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…2/controllerName/index could save 249B (33% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…6/controllerName/index could save 183B (30% reduction) after compression.
Minifying https://www.lilienthal.berlin/widgets/emotion/inde…5/controllerName/index could save 178B (21% reduction) after compression.
lilienthal.berlin Mobile Resource Breakdown
Total Resources | 85 |
Number of Hosts | 20 |
Static Resources | 52 |
JavaScript Resources | 14 |
CSS Resources | 4 |
lilienthal.berlin mobile page usability
Last tested: 2019-02-12
lilienthal.berlin 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.
<div class="dot--link">3</div>
is close to 4 other tap targets.lilienthal.berlin HTML validation
Warnings
Consider avoiding viewport values that prevent users from resizing documents.
"...l.png" /> <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no"> <meta..."
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
"...ript> <section class="content-cookie "> ..." Line: 362 Column: 1 - 52
"...i> </div> <section class="content-main container block-group"> <div ..."
Errors
Bad value “true” for attribute “async” on element “script”.
"...noscript> <script type="text/javascript" src="//static.criteo.net/js/ld/ld.js" async="true"></scri..."
Element “img” is missing required attribute “src”.
"...echseln"> <img srcset="/engine/Shopware/Plugins/Community/Frontend/ShopsThemeLilienthalPreSale/Themes/Frontend/ShopsThemeLilienthalPreSale/frontend/_public/src/img/buyoverlay/logo.png" alt="Lilienthal Berlin - Preisgekrönte Designeruhren - zur Startseite wechseln"/> </a> ..." Line: 343 Column: 1 - 167
"...: 48em)"> <img srcset="https://www.lilienthal.berlin/media/image/9e/f0/bf/logo_lilienthal.png" alt="Lilienthal Berlin - Preisgekrönte Designeruhren - zur Startseite wechseln" /> </pic..."
Attribute “name” not allowed on element “div” at this point.
"...y block"> <div class="buybox--trigger btn is--primary" name="Jetzt auswählen"> Jetzt..."
Bad value “” for attribute “action” on element “form”: Must be non-empty.
"... <form method="post" action="" class="language--form"> ..."
Bad value “menubar” for attribute “role” on element “nav”.
"...v> </nav> <nav class="top-bar--navigation block" role="menubar"> ..."
Attribute “autocapitalize” not allowed on element “input” at this point.
"...h--form"> <input type="search" name="sSearch" class="main-search--field" autocomplete="off" autocapitalize="off" placeholder="Suchbegriff..." maxlength="30" /> <butt..."
Element “div” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)
".../a> </li> <div class="mobile--switches"> ..."
Stray end tag “nav”.
"...i> </ul> </nav> </div..."
Element “script” must not have attribute “async” unless attribute “src” is also specified.
"... <script async id="refresh-statistic"></scri..."
lilienthal.berlin similar domains
www.lilienthal.net
www.lilienthal.org
www.lilienthal.info
www.lilienthal.biz
www.lilienthal.us
www.lilienthal.mobi
www.ilienthal.berlin
www.lilienthal.berlin
www.pilienthal.berlin
www.lpilienthal.berlin
www.plilienthal.berlin
www.oilienthal.berlin
www.loilienthal.berlin
www.olilienthal.berlin
www.kilienthal.berlin
www.lkilienthal.berlin
www.klilienthal.berlin
www.llienthal.berlin
www.lulienthal.berlin
www.liulienthal.berlin
www.luilienthal.berlin
www.ljlienthal.berlin
www.lijlienthal.berlin
www.ljilienthal.berlin
www.lklienthal.berlin
www.liklienthal.berlin
www.lolienthal.berlin
www.liolienthal.berlin
www.liienthal.berlin
www.lipienthal.berlin
www.lilpienthal.berlin
www.liplienthal.berlin
www.lioienthal.berlin
www.liloienthal.berlin
www.likienthal.berlin
www.lilkienthal.berlin
www.lilenthal.berlin
www.liluenthal.berlin
www.liliuenthal.berlin
www.liluienthal.berlin
www.liljenthal.berlin
www.lilijenthal.berlin
www.liljienthal.berlin
www.lilkenthal.berlin
www.lilikenthal.berlin
www.liloenthal.berlin
www.lilioenthal.berlin
www.lilinthal.berlin
www.liliwnthal.berlin
www.liliewnthal.berlin
www.liliwenthal.berlin
www.lilisnthal.berlin
www.liliesnthal.berlin
www.lilisenthal.berlin
www.lilidnthal.berlin
www.liliednthal.berlin
www.lilidenthal.berlin
www.lilirnthal.berlin
www.liliernthal.berlin
www.lilirenthal.berlin
www.liliethal.berlin
www.liliebthal.berlin
www.lilienbthal.berlin
www.liliebnthal.berlin
www.liliehthal.berlin
www.lilienhthal.berlin
www.liliehnthal.berlin
www.liliejthal.berlin
www.lilienjthal.berlin
www.liliejnthal.berlin
www.liliemthal.berlin
www.lilienmthal.berlin
www.liliemnthal.berlin
www.lilienhal.berlin
www.lilienrhal.berlin
www.lilientrhal.berlin
www.lilienrthal.berlin
www.lilienfhal.berlin
www.lilientfhal.berlin
www.lilienfthal.berlin
www.lilienghal.berlin
www.lilientghal.berlin
www.liliengthal.berlin
www.lilienyhal.berlin
www.lilientyhal.berlin
www.lilienythal.berlin
www.liliental.berlin
www.lilientbal.berlin
www.lilienthbal.berlin
www.lilientbhal.berlin
www.lilientgal.berlin
www.lilienthgal.berlin
www.lilientyal.berlin
www.lilienthyal.berlin
www.lilientual.berlin
www.lilienthual.berlin
www.lilientuhal.berlin
www.lilientjal.berlin
www.lilienthjal.berlin
www.lilientjhal.berlin
www.lilientnal.berlin
www.lilienthnal.berlin
www.lilientnhal.berlin
www.lilienthl.berlin
www.lilienthql.berlin
www.lilienthaql.berlin
www.lilienthqal.berlin
www.lilienthwl.berlin
www.lilienthawl.berlin
www.lilienthwal.berlin
www.lilienthsl.berlin
www.lilienthasl.berlin
www.lilienthsal.berlin
www.lilienthzl.berlin
www.lilienthazl.berlin
www.lilienthzal.berlin
www.lilientha.berlin
www.lilienthap.berlin
www.lilienthalp.berlin
www.lilienthapl.berlin
www.lilienthao.berlin
www.lilienthalo.berlin
www.lilienthaol.berlin
www.lilienthak.berlin
www.lilienthalk.berlin
www.lilienthakl.berlin
lilienthal.berlin 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.
lilienthal.berlin 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.