viessmann.de Website Information
Daily Unique Visits: 27,300
Daily Page Views: 163,800
Income Per Day: $328
Estimated Value: $236,160
This website is located in Germany and is using following IP address 93.122.86.52. See the complete list of popular websites hosted in Germany.
viessmann.de is registered under .DE top-level domain. Please check other sites in .DE zone.
Website viessmann.de is using the following name servers:
- auth54.ns.de.uu.net
- auth04.ns.de.uu.net
and is probably hosted by T-Systems International GmbH. See the full list of other websites hosted by T-Systems International GmbH.
The highest website viessmann.de position in Alexa rank database was 16058 and the lowest rank position was 959542. Current position of viessmann.de in Alexa rank database is 52536.
Desktop speed score of viessmann.de (80/100) is better than the results of 69.89% of other sites and shows that the page is performing great on desktop computers.
Mobile usability score of viessmann.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 viessmann.de (71/100) is better than the results of 78.26% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.
Advertisement
viessmann.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.
viessmann.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
viessmann.de server information
Servers Location
viessmann.de desktop page speed rank
Last tested: 2018-11-23
viessmann.de Desktop Speed Test Quick Summary
priority - 16Eliminate 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.viessmann.de/etc/clientlibs/viessmann/…10758916352-lc.min.css
https://fast.fonts.net/t/1.css?apiType=css&project…43ac-b8c5-2c4809e5a450
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:
https://www.googletagmanager.com/gtm.js?id=GTM-5JKBZ8 (15 minutes)
https://amplify.outbrain.com/cp/obtp.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/186060…2433?v=2.8.33&r=stable (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://cdn.inspectlet.com/inspectlet.js (4 hours)
https://cdn.taboola.com/libtrc/unip/1079574/tfa.js (4 hours)
https://cdn.taboola.com/libtrc/viessmannwerkegmbhcokg-sc/tfa.js (4 hours)
https://www.viessmann.de/de/tools/global_js_snippet_head.data.js (25.9 hours)
https://www.viessmann.de/content/dam/vi-corporate/…ns/original./blank.png (6 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 - 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 665B (14% reduction).
Minifying https://www.viessmann.de/de/tools/global_js_snippet_head.data.js could save 165B (24% reduction) after compression.
viessmann.de Desktop Resource Breakdown
Total Resources | 62 |
Number of Hosts | 18 |
Static Resources | 41 |
JavaScript Resources | 19 |
CSS Resources | 3 |
viessmann.de mobile page speed rank
Last tested: 2018-11-23
viessmann.de Mobile Speed Test Quick Summary
priority - 24Eliminate render-blocking JavaScript and CSS in above-the-fold content
Your page has 1 blocking script resources and 2 blocking CSS resources. This causes a delay in rendering your page.
Remove render-blocking JavaScript:
Optimize CSS Delivery of the following:
https://www.viessmann.de/etc/clientlibs/viessmann/…10758916352-lc.min.css
priority - 9Leverage 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.googletagmanager.com/gtm.js?id=GTM-5JKBZ8 (15 minutes)
https://amplify.outbrain.com/cp/obtp.js (20 minutes)
https://connect.facebook.net/en_US/fbevents.js (20 minutes)
https://connect.facebook.net/signals/config/186060…2433?v=2.8.33&r=stable (20 minutes)
https://bat.bing.com/bat.js (30 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://cdn.inspectlet.com/inspectlet.js (4 hours)
https://cdn.taboola.com/libtrc/unip/1079574/tfa.js (4 hours)
https://cdn.taboola.com/libtrc/viessmannwerkegmbhcokg-sc/tfa.js (4 hours)
https://www.viessmann.de/de/tools/global_js_snippet_head.data.js (25.9 hours)
https://www.viessmann.de/content/dam/vi-brands/DE/…icon-gewerbe-white.png (28.8 hours)
https://www.viessmann.de/content/dam/vi-brands/DE/…rgie-Spar-Check-1s.jpg (47.5 hours)
https://www.viessmann.de/content/dam/vi-brands/DE/…essmann-logo-weiss.png (3.2 days)
https://www.viessmann.de/content/dam/vi-corporate/…ns/original./blank.png (6 days)
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 - 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 665B (14% reduction).
Minifying https://www.viessmann.de/de/tools/global_js_snippet_head.data.js could save 165B (24% reduction) after compression.
viessmann.de Mobile Resource Breakdown
Total Resources | 61 |
Number of Hosts | 18 |
Static Resources | 41 |
JavaScript Resources | 19 |
CSS Resources | 3 |
viessmann.de mobile page usability
Last tested: 2018-11-23
viessmann.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://twitte…eenergiegesetz">#Gebäudeenergiegesetz</a>
and 1 others are close to other tap targets.viessmann.de HTML validation
Errors
A “charset” attribute on a “meta” element found after the first 1024 bytes.
"... charset="UTF-8"/> <meta htt..."
A “meta” element with an “http-equiv” attribute whose value is “X-UA-Compatible” must have a “content” attribute with the value “IE=edge”.
"...TF-8"/> <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"/> <m..."
Element “meta” is missing required attribute “content”.
"... <meta property="og:description"/> ..."
Element “img” is missing required attribute “src”.
".../a> <img class="vi_js_responsive_image" data-resp-src='[{ "mq": "vi_asset_s", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-facebook.png" },{ "mq": "vi_asset_m", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-facebook.png" },{ "mq": "vi_asset_l", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-facebook.png" },{ "mq": "vi_asset_xl", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-facebook-xl.png" }]'/> <..." Line: 2760 Column: 7 - 16
".../a> <img class="vi_js_responsive_image" data-resp-src='[{ "mq": "vi_asset_s", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-twitter.png" },{ "mq": "vi_asset_m", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-twitter.png" },{ "mq": "vi_asset_l", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-twitter.png" },{ "mq": "vi_asset_xl", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-twitter-xl.png" }]'/> <..."
An “img” element must have an “alt” attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images.
".../a> <img class="vi_js_responsive_image" data-resp-src='[{ "mq": "vi_asset_s", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-facebook.png" },{ "mq": "vi_asset_m", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-facebook.png" },{ "mq": "vi_asset_l", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-facebook.png" },{ "mq": "vi_asset_xl", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-facebook-xl.png" }]'/> <..." Line: 2760 Column: 7 - 16
".../a> <img class="vi_js_responsive_image" data-resp-src='[{ "mq": "vi_asset_s", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-twitter.png" },{ "mq": "vi_asset_m", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-twitter.png" },{ "mq": "vi_asset_l", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-twitter.png" },{ "mq": "vi_asset_xl", "src": "/etc/clientlibs/viessmann/viessmann.base.app/resources/img/icon-kachel-twitter-xl.png" }]'/> <..."
Warnings
Consider avoiding viewport values that prevent users from resizing documents.
"...e=1"/> <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no"/> ..."
Section lacks heading. Consider using “h2”-“h6” elements to add identifying headings to all sections.
"... <section class="vi_gesc vi_js_gesc"> <di..." Line: 2151 Column: 58 - 103
"... section"><section class="vi_tile_container vi_bg__gr5"> <di..." Line: 2937 Column: 3 - 42
"...ist --> <section class="vi_footer__social_list"> <..." Line: 3171 Column: 3 - 37
"...ction> <section class="vi_footer__bottom"> <..."
This document appears to be written in German. Consider adding “lang="de"” (or variant) to the “html” start tag.
"...E 8]><!--><html class="no-js"><!--<!..."
viessmann.de similar domains
www.viessmann.net
www.viessmann.org
www.viessmann.info
www.viessmann.biz
www.viessmann.us
www.viessmann.mobi
www.iessmann.de
www.viessmann.de
www.ciessmann.de
www.vciessmann.de
www.cviessmann.de
www.fiessmann.de
www.vfiessmann.de
www.fviessmann.de
www.giessmann.de
www.vgiessmann.de
www.gviessmann.de
www.biessmann.de
www.vbiessmann.de
www.bviessmann.de
www.vessmann.de
www.vuessmann.de
www.viuessmann.de
www.vuiessmann.de
www.vjessmann.de
www.vijessmann.de
www.vjiessmann.de
www.vkessmann.de
www.vikessmann.de
www.vkiessmann.de
www.voessmann.de
www.vioessmann.de
www.voiessmann.de
www.vissmann.de
www.viwssmann.de
www.viewssmann.de
www.viwessmann.de
www.visssmann.de
www.viesssmann.de
www.visessmann.de
www.vidssmann.de
www.viedssmann.de
www.videssmann.de
www.virssmann.de
www.vierssmann.de
www.viressmann.de
www.viesmann.de
www.viewsmann.de
www.vieswsmann.de
www.vieesmann.de
www.viesesmann.de
www.vieessmann.de
www.viedsmann.de
www.viesdsmann.de
www.viezsmann.de
www.vieszsmann.de
www.viezssmann.de
www.viexsmann.de
www.viesxsmann.de
www.viexssmann.de
www.vieasmann.de
www.viesasmann.de
www.vieassmann.de
www.vieswmann.de
www.viesswmann.de
www.viesemann.de
www.viessemann.de
www.viesdmann.de
www.viessdmann.de
www.vieszmann.de
www.viesszmann.de
www.viesxmann.de
www.viessxmann.de
www.viesamann.de
www.viessamann.de
www.viessann.de
www.viessnann.de
www.viessmnann.de
www.viessnmann.de
www.viessjann.de
www.viessmjann.de
www.viessjmann.de
www.viesskann.de
www.viessmkann.de
www.viesskmann.de
www.viessmnn.de
www.viessmqnn.de
www.viessmaqnn.de
www.viessmqann.de
www.viessmwnn.de
www.viessmawnn.de
www.viessmwann.de
www.viessmsnn.de
www.viessmasnn.de
www.viessmsann.de
www.viessmznn.de
www.viessmaznn.de
www.viessmzann.de
www.viessman.de
www.viessmabn.de
www.viessmanbn.de
www.viessmabnn.de
www.viessmahn.de
www.viessmanhn.de
www.viessmahnn.de
www.viessmajn.de
www.viessmanjn.de
www.viessmajnn.de
www.viessmamn.de
www.viessmanmn.de
www.viessmamnn.de
www.viessmanb.de
www.viessmannb.de
www.viessmanh.de
www.viessmannh.de
www.viessmanj.de
www.viessmannj.de
www.viessmanm.de
www.viessmannm.de
viessmann.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.
viessmann.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.