Viessmann.family Site Title

Vier Generationen – ein Unternehmen

Viessmann.family Meta Description

Viessmann bietet Unternehmen und Mitgestaltern ein Ökosystem, das sich für die Vermeidung, Reduktion und Speicherung von CO2 einsetzt.

Viessmann.family Test Results

Viessmann.family Mobile Performance: 55/100
Quick overview:
Max Potential First Input Delay
400 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
10.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
First Meaningful Paint
3.2 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Network Round Trip Times
30 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Final Screenshot
The last screenshot captured of the pageload.

448685835182

Metrics
Collects all available metrics.
Server Backend Latencies
30 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Diagnostics
Collection of useful page vitals.
Script Treemap Data
Used for treemap app
Network Requests
Lists the network requests that were made during page load.
Tasks
Lists the toplevel main thread tasks that executed during page load.

Viessmann.family Mobile SEO: 86/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Viessmann.family Mobile Best Practices: 77/100
Quick overview:
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Viessmann.family Mobile PWA: 88/100
Quick overview:
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn about maskable manifest icons.
Viessmann.family Mobile Accessibility: 82/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Touch targets have sufficient size and spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
All heading elements contain content.
A heading with no content or inaccessible text prevent screen reader users from accessing information on the page's structure. Learn more about headings.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Audio and video
These are opportunities to provide alternative content for audio and video. This may improve the experience for users with hearing or vision impairments.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
When a video provides a caption it is easier for deaf and hearing impaired users to access its information. Learn more about video captions.
Similar tests
www.viessmann.com
www.viessmann.net
www.viessmann.org
www.viessmann.info
www.viessmann.biz
www.viessmann.us
www.viessmann.mobi
www.iessmann.family
www.viessmann.family
www.ciessmann.family
www.vciessmann.family
www.cviessmann.family
www.fiessmann.family
www.vfiessmann.family
www.fviessmann.family
www.giessmann.family
www.vgiessmann.family
www.gviessmann.family
www.biessmann.family
www.vbiessmann.family
www.bviessmann.family
www.vessmann.family
www.vuessmann.family
www.viuessmann.family
www.vuiessmann.family
www.vjessmann.family
www.vijessmann.family
www.vjiessmann.family
www.vkessmann.family
www.vikessmann.family
www.vkiessmann.family
www.voessmann.family
www.vioessmann.family
www.voiessmann.family
www.vissmann.family
www.viwssmann.family
www.viewssmann.family
www.viwessmann.family
www.visssmann.family
www.viesssmann.family
www.visessmann.family
www.vidssmann.family
www.viedssmann.family
www.videssmann.family
www.virssmann.family
www.vierssmann.family
www.viressmann.family
www.viesmann.family
www.viewsmann.family
www.vieswsmann.family
www.vieesmann.family
www.viesesmann.family
www.vieessmann.family
www.viedsmann.family
www.viesdsmann.family
www.viezsmann.family
www.vieszsmann.family
www.viezssmann.family
www.viexsmann.family
www.viesxsmann.family
www.viexssmann.family
www.vieasmann.family
www.viesasmann.family
www.vieassmann.family
www.vieswmann.family
www.viesswmann.family
www.viesemann.family
www.viessemann.family
www.viesdmann.family
www.viessdmann.family
www.vieszmann.family
www.viesszmann.family
www.viesxmann.family
www.viessxmann.family
www.viesamann.family
www.viessamann.family
www.viessann.family
www.viessnann.family
www.viessmnann.family
www.viessnmann.family
www.viessjann.family
www.viessmjann.family
www.viessjmann.family
www.viesskann.family
www.viessmkann.family
www.viesskmann.family
www.viessmnn.family
www.viessmqnn.family
www.viessmaqnn.family
www.viessmqann.family
www.viessmwnn.family
www.viessmawnn.family
www.viessmwann.family
www.viessmsnn.family
www.viessmasnn.family
www.viessmsann.family
www.viessmznn.family
www.viessmaznn.family
www.viessmzann.family
www.viessman.family
www.viessmabn.family
www.viessmanbn.family
www.viessmabnn.family
www.viessmahn.family
www.viessmanhn.family
www.viessmahnn.family
www.viessmajn.family
www.viessmanjn.family
www.viessmajnn.family
www.viessmamn.family
www.viessmanmn.family
www.viessmamnn.family
www.viessmanb.family
www.viessmannb.family
www.viessmanh.family
www.viessmannh.family
www.viessmanj.family
www.viessmannj.family
www.viessmanm.family
www.viessmannm.family
Last Tested: