Tools & Wizards About Us
viega.de screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

viega.de

Viega Deutschland | viega.de

Page Load Speed

6.7 sec in total

First Response

329 ms

Resources Loaded

6.2 sec

Page Rendered

172 ms

viega.de screenshot

About Website

Visit viega.de now to see the best up-to-date Viega content for Germany and also check out these interesting facts you probably never knew about viega.de

Wir engagieren uns für die elementar wichtigen Themen der Branche - wie den Erhalt der Trinkwassergüte oder den Brandschutz. Aber auch in puncto Design setzen wir Maßstäbe – etwa mit unseren Produkten...

Visit viega.de

Key Findings

We analyzed Viega.de page load time and found that the first response time was 329 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

viega.de performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value19.9 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.852

4/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

viega.de

329 ms

www.viega.de

735 ms

screen.css

1828 ms

jquery.fancybox.css

1748 ms

jquery.min.js

2306 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 97% of them (38 requests) were addressed to the original Viega.de, 3% (1 request) were made to Viegade01.wt-eu02.net. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Viega.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 746.5 kB (70%)

Content Size

1.1 MB

After Optimization

327.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Viega.de main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Javascripts take 750.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 23.6 kB

  • Original 30.6 kB
  • After minification 28.0 kB
  • After compression 7.0 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 23.6 kB or 77% of the original size.

Image Optimization

-3%

Potential reduce by 5.3 kB

  • Original 156.8 kB
  • After minification 151.4 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Viega images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 601.9 kB

  • Original 750.2 kB
  • After minification 545.8 kB
  • After compression 148.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 601.9 kB or 80% of the original size.

CSS Optimization

-85%

Potential reduce by 115.7 kB

  • Original 136.1 kB
  • After minification 101.1 kB
  • After compression 20.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Viega.de needs all CSS files to be minified and compressed as it can save up to 115.7 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (68%)

Requests Now

37

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Viega. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

viega.de

viega.de

329 ms

www.viega.de

www.viega.de

735 ms

screen.css

screen.css

1828 ms

jquery.fancybox.css

jquery.fancybox.css

1748 ms

jquery.min.js

jquery.min.js

2306 ms

viega.js

viega.js

2027 ms

swfobject-1.5.js

swfobject-1.5.js

1944 ms

form_validation.js

form_validation.js

2581 ms

jquery.fancybox-1.2.1.js

jquery.fancybox-1.2.1.js

3038 ms

jquery-ui.js

jquery-ui.js

3587 ms

jquery.JScrollPane.js

jquery.JScrollPane.js

2938 ms

jquery.hoverIntent.js

jquery.hoverIntent.js

2966 ms

doorpage.js

doorpage.js

3166 ms

jquery.wmuslider.js

jquery.wmuslider.js

3408 ms

jquery.wmuGallery.js

jquery.wmuGallery.js

3506 ms

webtrekk_v4.min.de.js

webtrekk_v4.min.de.js

3956 ms

screen_default.css

screen_default.css

2322 ms

screen_default_new.css

screen_default_new.css

1927 ms

screen_mobile_portrait.css

screen_mobile_portrait.css

1933 ms

screen_mobile_landscape.css

screen_mobile_landscape.css

1930 ms

screen_mobile_landscape_iphone5.css

screen_mobile_landscape_iphone5.css

1954 ms

screen_mobile.css

screen_mobile.css

2301 ms

logo.gif

logo.gif

96 ms

bg_mainnav.gif

bg_mainnav.gif

95 ms

ico_dropdown.gif

ico_dropdown.gif

187 ms

bg_2col_navigation.png

bg_2col_navigation.png

193 ms

de-DE_Materialvielfalt_DE2_quer_720x184.jpg

de-DE_Materialvielfalt_DE2_quer_720x184.jpg

578 ms

Arbeitgeber_174x80.jpg

Arbeitgeber_174x80.jpg

288 ms

rd_Megapress_Pressen_B_174x80.jpg

rd_Megapress_Pressen_B_174x80.jpg

359 ms

rd_Titel_0055-final_174x80.jpg

rd_Titel_0055-final_174x80.jpg

362 ms

rd_viega-170118-06-12_174x80.jpg

rd_viega-170118-06-12_174x80.jpg

453 ms

unterkante4.gif

unterkante4.gif

368 ms

send.gif

send.gif

466 ms

add.gif

add.gif

548 ms

info.gif

info.gif

550 ms

questionmark.gif

questionmark.gif

551 ms

trinkwasser.jpg

trinkwasser.jpg

833 ms

wt

wt

293 ms

print.css

print.css

192 ms

Accessibility Review

viega.de accessibility score

84

Accessibility Issues

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.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

viega.de best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

viega.de SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Viega.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Viega.de main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

viega.de

Open Graph description is not detected on the main page of Viega. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: