weimar.de Website Information
Daily Unique Visits: 9,550
Daily Page Views: 47,750
Income Per Day: $119
Estimated Value: $71,400
weimar.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 InterNetX GmbH. See the full list of other websites hosted by InterNetX GmbH.
The highest website weimar.de position in Alexa rank database was 9865 and the lowest rank position was 997362. Current position of weimar.de in Alexa rank database is 142673.
Desktop speed score of weimar.de (54/100) is better than the results of 28.19% of other sites and shows that the page desktop performance can be improved.
Mobile usability score of weimar.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 weimar.de (64/100) is better than the results of 64.03% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
weimar.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.
weimar.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
weimar.de server information
Servers Location
weimar.de desktop page speed rank
Last tested: 2019-07-01
weimar.de Desktop Speed Test Quick Summary
priority - 73Optimize images
Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 709.7KiB (89% reduction).
Compressing and resizing https://www.weimar.de/fileadmin/Redaktion/_process…tmuseum_f1a9f1461b.jpg could save 130.3KiB (87% reduction).
Compressing and resizing https://www.weimar.de/fileadmin/Redaktion/_process…%A4chen_d0bf424747.jpg could save 108.8KiB (90% reduction).
Compressing and resizing https://www.weimar.de/fileadmin/Redaktion/_process…mbH_web_1eff6a2900.jpg could save 101.8KiB (85% reduction).
Compressing and resizing https://www.weimar.de/fileadmin/Redaktion/_process…_Wulf_1_ad6e5e81a1.jpg could save 99.1KiB (93% reduction).
Compressing and resizing https://www.weimar.de/typo3temp/_processed_/f/7/cs…30500d6_44be8aa8d9.jpg could save 60.3KiB (87% reduction).
Compressing and resizing https://www.weimar.de/typo3temp/_processed_/b/1/cs…dc2ccb7_29741f70aa.jpg could save 55.5KiB (88% reduction).
Compressing and resizing https://www.weimar.de/typo3temp/_processed_/e/d/cs…eholder_1622725b4a.png could save 2.7KiB (85% reduction).
priority - 9Reduce server response time
In our test, your server responded in 1.1 seconds.
priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 17 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://www.weimar.de/typo3conf/ext/theme_weimar/R…y-ui.min.js?1484052312
https://www.weimar.de/typo3conf/ext/theme_weimar/R…trap.min.js?1477993220
https://www.weimar.de/typo3conf/ext/theme_weimar/R…lick.min.js?1477993220
https://www.weimar.de/typo3conf/ext/theme_weimar/R…minified.js?1478625981
https://www.weimar.de/typo3conf/ext/theme_weimar/R…ight-min.js?1478858958
https://www.weimar.de/typo3conf/ext/theme_weimar/R…tbox.min.js?1485879458
https://www.weimar.de/typo3conf/ext/theme_weimar/R…cker.min.js?1484903094
https://www.weimar.de/typo3conf/ext/theme_weimar/R…parallax.js?1490173519
https://www.weimar.de/typo3conf/ext/theme_weimar/R…lect.min.js?1487342883
https://www.weimar.de/typo3conf/ext/ke_search_prem…lete.min.js?1462545357
https://www.weimar.de/typo3conf/ext/theme_weimar/R…ookiebar.js?1492673289
https://www.weimar.de/typo3conf/ext/theme_weimar/R…vascript.js?1557312094
https://www.weimar.de/typo3conf/ext/theme_weimar/R…sponsive.js?1484831784
https://www.weimar.de/typo3conf/ext/bootstrap_grid…ider-min.js?1477993465
https://www.weimar.de/typo3conf/ext/theme_weimar/R…_address.js?1493380853
https://www.weimar.de/typo3temp/vhs-assets-pageslidejs.js?1561728489
Optimize CSS Delivery of the following:
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 - 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 3.6KiB (22% reduction).
Minifying https://www.weimar.de/typo3conf/ext/theme_weimar/R…parallax.js?1490173519 could save 878B (22% reduction) after compression.
Minifying https://www.weimar.de/typo3conf/ext/theme_weimar/R…vascript.js?1557312094 could save 849B (22% reduction) after compression.
Minifying https://www.weimar.de/typo3conf/ext/theme_weimar/R…tbox.min.js?1485879458 could save 489B (12% reduction) after compression.
Minifying https://www.weimar.de/typo3conf/ext/theme_weimar/R…minified.js?1478625981 could save 188B (27% reduction) after compression.
Minifying https://www.weimar.de/typo3temp/vhs-assets-pageslidejs.js?1561728489 could save 111B (23% reduction) after compression.
Minifying https://www.weimar.de/typo3conf/ext/theme_weimar/R…_address.js?1493380853 could save 110B (15% reduction) after compression.
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 1.5KiB (11% reduction).
weimar.de Desktop Resource Breakdown
| Total Resources | 43 |
| Number of Hosts | 2 |
| Static Resources | 36 |
| JavaScript Resources | 18 |
| CSS Resources | 2 |
weimar.de mobile page speed rank
Last tested: 2017-05-05
weimar.de Mobile Speed Test Quick Summary
priority - 32Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 14 blocking script resources and 1 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
https://www.weimar.de/typo3conf/ext/theme_weimar/R…y-ui.min.js?1484052312
https://www.weimar.de/typo3conf/ext/theme_weimar/R…trap.min.js?1477993220
https://www.weimar.de/typo3conf/ext/theme_weimar/R…lick.min.js?1477993220
https://www.weimar.de/typo3conf/ext/theme_weimar/R…minified.js?1478625981
https://www.weimar.de/typo3conf/ext/theme_weimar/R…ight-min.js?1478858958
https://www.weimar.de/typo3conf/ext/theme_weimar/R…tbox.min.js?1485879458
https://www.weimar.de/typo3conf/ext/theme_weimar/R…cker.min.js?1484903094
https://www.weimar.de/typo3conf/ext/theme_weimar/R…parallax.js?1490173519
https://www.weimar.de/typo3conf/ext/theme_weimar/R…lect.min.js?1487342883
https://www.weimar.de/typo3conf/ext/ke_search_prem…lete.min.js?1462545357
https://www.weimar.de/typo3conf/ext/theme_weimar/R…ookiebar.js?1492673289
https://www.weimar.de/typo3conf/ext/theme_weimar/R…vascript.js?1490861480
https://www.weimar.de/typo3conf/ext/theme_weimar/R…sponsive.js?1484831784
Optimize CSS Delivery of the following:
priority - 26Avoid 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.
http://www.weimar.de/
https://www.weimar.de/
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 2.7KiB (27% reduction).
Minifying https://www.weimar.de/typo3conf/ext/theme_weimar/R…parallax.js?1490173519 could save 876B (22% reduction) after compression.
Minifying https://www.weimar.de/typo3conf/ext/theme_weimar/R…vascript.js?1490861480 could save 839B (22% reduction) after compression.
weimar.de Mobile Resource Breakdown
| Total Resources | 43 |
| Number of Hosts | 2 |
| Static Resources | 36 |
| JavaScript Resources | 18 |
| CSS Resources | 2 |
weimar.de mobile page usability
Last tested: 2017-05-05
weimar.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="https://www.weimar.de" class="wrapper"></a> is close to 1 other tap targets.weimar.de HTML validation
Errors
Element “noscript” not allowed as child of element “picture” in this context. (Suppressing further errors from this subtree.)
"...mar GmbH"><noscript><img s..." Line: 627 Column: 4036 - 4045
"... title=""><noscript><img s..." Line: 627 Column: 5708 - 5717
"... title=""><noscript><img s..." Line: 627 Column: 7459 - 7468
"... title=""><noscript><img s..." Line: 630 Column: 1536 - 1545
"...mar GmbH"><noscript><img s..." Line: 630 Column: 3362 - 3371
"... title=""><noscript><img s..." Line: 651 Column: 14 - 23
"... <noscript> ..." Line: 694 Column: 14 - 23
"... <noscript> ..." Line: 737 Column: 14 - 23
"... <noscript> ..."
Attribute “xmlns:xhtml” not allowed here.
"...ner"> <div xmlns:xhtml="http://www.w3.org/1999/xhtml" class="row"><div c..."
The “itemprop” attribute was specified, but the element is not a property of any item.
"...pas.jpg"> <meta itemprop="name" content="Kulturstadt Weimar&nbsp;-&nbsp;www.weimar.de&nbsp;"> <meta..." Line: 34 Column: 1 - 141
"...p;nbsp;"> <meta itemprop="image" content="https://www.weimar.de/typo3conf/ext/theme_weimar/Resources/Public/Images/Logo/weimar_kulturstadteuropas.jpg"> <meta..."
Warnings
Attribute with the local name “xmlns:xhtml” is not serializable as XML 1.0.
"...ner"> <div xmlns:xhtml="http://www.w3.org/1999/xhtml" class="row"><div c..."
weimar.de similar domains
www.weimar.net
www.weimar.org
www.weimar.info
www.weimar.biz
www.weimar.us
www.weimar.mobi
www.eimar.de
www.weimar.de
www.qeimar.de
www.wqeimar.de
www.qweimar.de
www.aeimar.de
www.waeimar.de
www.aweimar.de
www.seimar.de
www.wseimar.de
www.sweimar.de
www.eeimar.de
www.weeimar.de
www.eweimar.de
www.wimar.de
www.wwimar.de
www.wewimar.de
www.wweimar.de
www.wsimar.de
www.wesimar.de
www.wdimar.de
www.wedimar.de
www.wdeimar.de
www.wrimar.de
www.werimar.de
www.wreimar.de
www.wemar.de
www.weumar.de
www.weiumar.de
www.weuimar.de
www.wejmar.de
www.weijmar.de
www.wejimar.de
www.wekmar.de
www.weikmar.de
www.wekimar.de
www.weomar.de
www.weiomar.de
www.weoimar.de
www.weiar.de
www.weinar.de
www.weimnar.de
www.weinmar.de
www.weijar.de
www.weimjar.de
www.weikar.de
www.weimkar.de
www.weimr.de
www.weimqr.de
www.weimaqr.de
www.weimqar.de
www.weimwr.de
www.weimawr.de
www.weimwar.de
www.weimsr.de
www.weimasr.de
www.weimsar.de
www.weimzr.de
www.weimazr.de
www.weimzar.de
www.weima.de
www.weimae.de
www.weimare.de
www.weimaer.de
www.weimad.de
www.weimard.de
www.weimadr.de
www.weimaf.de
www.weimarf.de
www.weimafr.de
www.weimat.de
www.weimart.de
www.weimatr.de
weimar.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.
weimar.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.