viessmann.com Website Information

Daily Unique Visits: 11,658

Daily Page Views: 58,290

Income Per Day: $146

Estimated Value: $87,600

This website is located in Germany and is using following IP address 93.122.86.37. See the complete list of popular websites hosted in Germany.

viessmann.com is registered under .COM top-level domain. Please check other sites in .COM zone.

Website viessmann.com is using the following name servers:

auth04.ns.de.uu.net
auth54.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.com position in Alexa rank database was 114454 and the lowest rank position was 117659. Current position of viessmann.com in Alexa rank database is 116876.

Desktop speed score of viessmann.com (77/100) is better than the results of 63.93% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of viessmann.com (60/100) is better than the results of 3.95% of other sites and means that the page is not mobile-friendly.

Mobile speed score of viessmann.com (55/100) is better than the results of 43.86% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

viessmann.com 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.com 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.

Domain Name: VIESSMANN.COM
Registry Domain ID: 3036054_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.rrpproxy.net
Registrar URL: http://www.key-systems.net
Updated Date: 2023-11-11T08:01:54Z
Creation Date: 1996-11-11T05:00:00Z
Registry Expiry Date: 2024-11-10T05:00:00Z
Registrar: Key-Systems GmbH
Registrar IANA ID: 269
Registrar Abuse Contact Email: abuse@key-systems.net
Registrar Abuse Contact Phone: +49.68949396850
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: AUTH0020.NS.EU.UU.NET
Name Server: AUTH0030.NS.EU.UU.NET
Name Server: AUTH04.NS.DE.UU.NET
Name Server: AUTH54.NS.DE.UU.NET
Name Server: NS1.RRPPROXY.NET
Name Server: NS2.RRPPROXY.NET
Name Server: NS3.RRPPROXY.NET
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-09-25T22:49:41Z

viessmann.com server information

Servers Location

viessmann.com desktop page speed rank

Last tested: 2018-11-06

Desktop Speed Medium

77/100

viessmann.com 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:

https://www.viessmann-us.com/etc/clientlibs/viessm…510758916352-lc.min.js

Optimize CSS Delivery of the following:

https://www.viessmann-us.com/etc/clientlibs/viessm…10758916352-lc.min.css
https://www.viessmann-us.com/etc/clientlibs/viessm…10758916352-lc.min.css
https://fast.fonts.net/t/1.css?apiType=css&project…43ac-b8c5-2c4809e5a450

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.

http://viessmann.com/
https://www.viessmann.com/com/en.html
https://www.viessmann-us.com/

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.

Only about 14% of the final above-the-fold content could be rendered with the full HTML response.

Click to see the screenshot with only the HTML response:

priority - 1Leverage 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-MT2Q229 (15 minutes)
https://www.google-analytics.com/analytics.js (2 hours)
https://www.viessmann-us.com/etc/clientlibs/viessm…10758916352-lc.min.css (3 days)
https://www.viessmann-us.com/content/dam/vi-brands…iginal./icon-login.png (3.8 days)
https://www.viessmann-us.com/content/dam/vi-brands…riginal./cu3a_tile.jpg (5.9 days)

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.3KiB (13% reduction).

Minifying https://www.viessmann-us.com/ could save 1.3KiB (13% reduction) after compression.

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 241B (20% reduction).

Minifying https://www.viessmann-us.com/en/tools/global_js_snippet_body.data.js could save 133B (19% reduction) after compression.
Minifying https://www.viessmann-us.com/en/tools/global_js_snippet_head.data.js could save 108B (23% reduction) after compression.

viessmann.com Desktop Resource Breakdown

Total Resources	41
Number of Hosts	10
Static Resources	30
JavaScript Resources	13
CSS Resources	3

viessmann.com mobile page speed rank

Last tested: 2018-11-06

Mobile Speed Bad

55/100

viessmann.com Mobile Speed Test Quick Summary

priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

http://viessmann.com/com/css/viessmann.css
http://fast.fonts.net/t/1.css?apiType=css&projecti…4055-9a05-da8c84f103ed
http://viessmann.com/com/css/viessmann-font-latin1.css
http://viessmann.com/com/css/viessmann-redesign.css

priority - 20Leverage 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://viessmann.com/com/css/fancybox/jquery.fancybox-1.3.4.css (60 minutes)
http://viessmann.com/com/css/jquery.shadow.css (60 minutes)
http://viessmann.com/com/css/lightbox.css (60 minutes)
http://viessmann.com/com/css/nivo-slider.css (60 minutes)
http://viessmann.com/com/css/viessmann-font-latin1.css (60 minutes)
http://viessmann.com/com/css/viessmann-ipad.css (60 minutes)
http://viessmann.com/com/css/viessmann-redesign.css (60 minutes)
http://viessmann.com/com/css/viessmann-smartphone.css (60 minutes)
http://viessmann.com/com/css/viessmann.css (60 minutes)
http://viessmann.com/com/css/viessmann_form.css (60 minutes)
http://viessmann.com/com/css/viessmannprint.css (60 minutes)
http://viessmann.com/com/fonts/univers67condensed_bold_latin_1-webfont.ttf (60 minutes)
http://viessmann.com/com/js/fancybox/jquery.fancybox-1.3.4.pack.js (60 minutes)
http://viessmann.com/com/js/fontSmoothingHelper.js (60 minutes)
http://viessmann.com/com/js/functions.js (60 minutes)
http://viessmann.com/com/js/jquery.capSlide.js (60 minutes)
http://viessmann.com/com/js/jquery.cookie.js (60 minutes)
http://viessmann.com/com/js/jquery.corner.js (60 minutes)
http://viessmann.com/com/js/jquery.infieldlabel.min.js (60 minutes)
http://viessmann.com/com/js/jquery.min.js (60 minutes)
http://viessmann.com/com/js/jquery.nivo.slider.pack.js (60 minutes)
http://viessmann.com/com/js/jquery.shadow.js (60 minutes)
http://viessmann.com/com/js/jquery.timers.js (60 minutes)
http://viessmann.com/com/js/livevalidation_standalone.js (60 minutes)
http://viessmann.com/com/js/swfobject.js (60 minutes)
http://viessmann.com/com/js/viessmann.js (60 minutes)
http://viessmann.com/com/js/webtrends.js (60 minutes)

priority - 18Enable 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 179.5KiB (69% reduction).

Compressing http://viessmann.com/com/js/jquery.min.js could save 59.7KiB (64% reduction).
Compressing http://viessmann.com/com/js/livevalidation_standalone.js could save 31.5KiB (78% reduction).
Compressing http://viessmann.com/com/js/viessmann.js could save 18.2KiB (71% reduction).
Compressing http://viessmann.com/com/js/webtrends.js could save 15.8KiB (71% reduction).
Compressing http://viessmann.com/com/js/functions.js could save 12.6KiB (76% reduction).
Compressing http://viessmann.com/com/js/fancybox/jquery.fancybox-1.3.4.pack.js could save 9.8KiB (64% reduction).
Compressing http://viessmann.com/com/js/jquery.nivo.slider.pack.js could save 8.3KiB (73% reduction).
Compressing http://viessmann.com/com/js/jquery.corner.js could save 7.9KiB (70% reduction).
Compressing http://viessmann.com/com/js/swfobject.js could save 6KiB (68% reduction).
Compressing http://viessmann.com/com/js/jquery.cookie.js could save 2.3KiB (63% reduction).
Compressing http://viessmann.com/com/js/jquery.timers.js could save 2.2KiB (68% reduction).
Compressing http://viessmann.com/com/js/fontSmoothingHelper.js could save 2.1KiB (62% reduction).
Compressing http://viessmann.com/com/js/jquery.shadow.js could save 1.1KiB (57% reduction).
Compressing http://viessmann.com/com/js/jquery.infieldlabel.min.js could save 982B (56% reduction).
Compressing http://viessmann.com/com/js/jquery.capSlide.js could save 981B (63% reduction).

priority - 6Minify 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 58KiB (39% reduction).

Minifying http://viessmann.com/com/js/livevalidation_standalone.js could save 24KiB (59% reduction).
Minifying http://viessmann.com/com/js/viessmann.js could save 8.7KiB (35% reduction).
Minifying http://viessmann.com/com/js/functions.js could save 6.5KiB (40% reduction).
Minifying http://viessmann.com/com/js/jquery.corner.js could save 5KiB (45% reduction).
Minifying http://viessmann.com/com/js/webtrends.js could save 3.8KiB (17% reduction).
Minifying http://viessmann.com/com/js/jquery.cookie.js could save 2.9KiB (78% reduction).
Minifying http://viessmann.com/com/js/fontSmoothingHelper.js could save 2.3KiB (69% reduction).
Minifying http://viessmann.com/com/js/swfobject.js could save 2.2KiB (26% reduction).
Minifying http://viessmann.com/com/js/jquery.shadow.js could save 1KiB (50% reduction).
Minifying http://viessmann.com/com/js/jquery.timers.js could save 993B (30% reduction).
Minifying http://viessmann.com/com/js/fancybox/jquery.fancybox-1.3.4.pack.js could save 635B (5% reduction).

priority - 2Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 16.9KiB (33% reduction).

Losslessly compressing http://viessmann.com/com/content/dam/internet-glob…me/hp_vitotrol-app.jpg could save 3.4KiB (42% reduction).
Losslessly compressing http://viessmann.com/com/content/dam/internet-glob…/home/hp_mikro-kwk.jpg could save 3.4KiB (27% reduction).
Losslessly compressing http://viessmann.com/img/nivo_slider_arrows.png could save 2.8KiB (77% reduction).
Losslessly compressing http://viessmann.com/com/img/icon-google-plus.gif could save 1.2KiB (54% reduction).
Losslessly compressing http://viessmann.com/com/img/icon-google-plus-one-deactivated.gif could save 1.1KiB (84% reduction).
Losslessly compressing http://viessmann.com/com/img/icons-facelift.gif could save 1.1KiB (27% reduction).
Losslessly compressing http://viessmann.com/com/img/icon-twitter.gif could save 1KiB (82% reduction).
Losslessly compressing http://viessmann.com/com/img/icon-facebook.gif could save 1KiB (81% reduction).
Losslessly compressing http://viessmann.com/com/img/icon-youtube.gif could save 1KiB (46% reduction).
Losslessly compressing http://viessmann.com/com/content/dam/internet-glob…es/home/referenzen.jpg could save 830B (6% 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 3.5KiB (20% reduction).

Minifying http://viessmann.com/com/css/viessmann-redesign.css could save 2.1KiB (25% reduction) after compression.
Minifying http://viessmann.com/com/css/viessmann.css could save 1.3KiB (16% 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 1KiB (16% reduction).

Minifying http://viessmann.com/com/en.html could save 1KiB (16% reduction) after compression.

viessmann.com Mobile Resource Breakdown

Total Resources	68
Number of Hosts	4
Static Resources	61
JavaScript Resources	17
CSS Resources	12

viessmann.com mobile page usability

Last tested: 2018-11-06

Mobile Usability Bad

60/100

viessmann.com Mobile Usability Test Quick Summary

priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

Sitemap and 1 others render only 3 pixels tall (11 CSS pixels).

DE and 1 others render only 3 pixels tall (11 CSS pixels).

viessmann.de renders only 3 pixels tall (11 CSS pixels).

Country / Region renders only 4 pixels tall (13 CSS pixels).

Purchasing department and 8 others render only 4 pixels tall (13 CSS pixels).

Comprehensive…energy sources renders only 4 pixels tall (14 CSS pixels).

Micro CHP boiler and 2 others render only 4 pixels tall (13 CSS pixels).

International renders only 4 pixels tall (13 CSS pixels).

family busines…n 74 countries and 2 others render only 4 pixels tall (13 CSS pixels).

Latin America and 5 others render only 4 pixels tall (13 CSS pixels).

Viessmann Werke GmbH & Co. KG and 4 others render only 3 pixels tall (11 CSS pixels).

priority - 21Size 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.

The tap target <a href="/com/en/service/sitemap.html">Sitemap</a> and 1 others are close to other tap targets.

The tap target <a href="/com/de.html" class="linkItem">DE</a> and 1 others are close to other tap targets.

The tap target <button type="submit" class="button">Search</button> is close to 2 other tap targets.

The tap target <a href="http://www.viessmann.de">viessmann.de</a> is close to 1 other tap targets.

The tap target <button type="submit" class="button"></button> is close to 2 other tap targets.

The tap target <a href="/com/en/profile.html">Profile</a> and 8 others are close to other tap targets.

The tap target <a href="/com/en/intern…al/Africa.html" class="linkItem">Africa</a> and 5 others are close to other tap targets.

The tap target <a href="http://twitter.com/Viessmann"></a> and 4 others are close to other tap targets.

The tap target <div class="g-plusone"></div> is close to 3 other tap targets.

The tap target <a href="/com/en/imprint.html">Imprint</a> and 2 others are close to other tap targets.

priority - 10Configure the viewport

Your page specifies a fixed-width desktop viewport. Use a responsive viewport to allow your page to render properly on all devices.

viessmann.com HTML validation

Errors

Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.

Line: 1 Column: 1 - 6
"...<HTML> <HEAD..."

Element “head” is missing a required instance of child element “title”.

Line: 2 Column: 89 - 95
".../en.html"></HEAD> <BODY..."

viessmann.com similar domains

Similar domains:

www.viessmann.com
www.viessmann.net
www.viessmann.org
www.viessmann.info
www.viessmann.biz
www.viessmann.us
www.viessmann.mobi
www.iessmann.com
www.viessmann.com
www.ciessmann.com
www.vciessmann.com
www.cviessmann.com
www.fiessmann.com
www.vfiessmann.com
www.fviessmann.com
www.giessmann.com
www.vgiessmann.com
www.gviessmann.com
www.biessmann.com
www.vbiessmann.com
www.bviessmann.com
www.vessmann.com
www.vuessmann.com
www.viuessmann.com
www.vuiessmann.com
www.vjessmann.com
www.vijessmann.com
www.vjiessmann.com
www.vkessmann.com
www.vikessmann.com
www.vkiessmann.com
www.voessmann.com
www.vioessmann.com
www.voiessmann.com
www.vissmann.com
www.viwssmann.com
www.viewssmann.com
www.viwessmann.com
www.visssmann.com
www.viesssmann.com
www.visessmann.com
www.vidssmann.com
www.viedssmann.com
www.videssmann.com
www.virssmann.com
www.vierssmann.com
www.viressmann.com
www.viesmann.com
www.viewsmann.com
www.vieswsmann.com
www.vieesmann.com
www.viesesmann.com
www.vieessmann.com
www.viedsmann.com
www.viesdsmann.com
www.viezsmann.com
www.vieszsmann.com
www.viezssmann.com
www.viexsmann.com
www.viesxsmann.com
www.viexssmann.com
www.vieasmann.com
www.viesasmann.com
www.vieassmann.com
www.vieswmann.com
www.viesswmann.com
www.viesemann.com
www.viessemann.com
www.viesdmann.com
www.viessdmann.com
www.vieszmann.com
www.viesszmann.com
www.viesxmann.com
www.viessxmann.com
www.viesamann.com
www.viessamann.com
www.viessann.com
www.viessnann.com
www.viessmnann.com
www.viessnmann.com
www.viessjann.com
www.viessmjann.com
www.viessjmann.com
www.viesskann.com
www.viessmkann.com
www.viesskmann.com
www.viessmnn.com
www.viessmqnn.com
www.viessmaqnn.com
www.viessmqann.com
www.viessmwnn.com
www.viessmawnn.com
www.viessmwann.com
www.viessmsnn.com
www.viessmasnn.com
www.viessmsann.com
www.viessmznn.com
www.viessmaznn.com
www.viessmzann.com
www.viessman.com
www.viessmabn.com
www.viessmanbn.com
www.viessmabnn.com
www.viessmahn.com
www.viessmanhn.com
www.viessmahnn.com
www.viessmajn.com
www.viessmanjn.com
www.viessmajnn.com
www.viessmamn.com
www.viessmanmn.com
www.viessmamnn.com
www.viessmanb.com
www.viessmannb.com
www.viessmanh.com
www.viessmannh.com
www.viessmanj.com
www.viessmannj.com
www.viessmanm.com
www.viessmannm.com
www.viessmann.con

viessmann.com 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.com 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.

VIESSMANN.COM Website Information

viessmann.com Website Information

Advertisement

viessmann.com Alexa Rank

viessmann.com whois

viessmann.com server information

Servers Location

viessmann.com desktop page speed rank

viessmann.com 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:

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.

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.

priority - 1Leverage 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:

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.3KiB (13% 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 241B (20% reduction).

viessmann.com Desktop Resource Breakdown

viessmann.com mobile page speed rank

viessmann.com Mobile Speed Test Quick Summary

priority - 40Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 4 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

priority - 20Leverage 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:

priority - 18Enable 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 179.5KiB (69% reduction).

priority - 6Minify 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 58KiB (39% reduction).

priority - 2Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 16.9KiB (33% 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 3.5KiB (20% 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 1KiB (16% reduction).

viessmann.com Mobile Resource Breakdown

viessmann.com mobile page usability

viessmann.com Mobile Usability Test Quick Summary

priority - 40Use legible font sizes

The following text on your page renders in a way that may be difficult for some of your visitors to read. Use legible font sizes to provide a better user experience.

The following text fragments have a small font size. Increase the font size to make them more legible.

priority - 21Size 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.

priority - 10Configure the viewport

Your page specifies a fixed-width desktop viewport. Use a responsive viewport to allow your page to render properly on all devices.

viessmann.com HTML validation

Errors

Start tag seen without seeing a doctype first. Expected “<!DOCTYPE html>”.

Element “head” is missing a required instance of child element “title”.

viessmann.com similar domains

viessmann.com Ping

viessmann.com TRACEROUTE