Tools & Wizards About Us
wilo.at screenshot

Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

wilo.at

Wilo - Pumpenhersteller in Ihrer Nähe seit 1872 | WILO Pumpen Österreich GmbH

Page Load Speed

4.7 sec in total

First Response

373 ms

Resources Loaded

3.1 sec

Page Rendered

1.2 sec

wilo.at screenshot

About Website

Welcome to wilo.at homepage info - get ready to check Wilo best content for Austria right away, or after learning these important things about wilo.at

Die Wilo-Gruppe ist einer der weltweit führenden Hersteller von Pumpen und Pumpensystemen für Wasserversorgung und Klimatechnik.

Visit wilo.at

Key Findings

We analyzed Wilo.at page load time and found that the first response time was 373 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

wilo.at performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value12.9 s

0/100

25%

SI (Speed Index)

Value7.0 s

33/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.238

52/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

wilo.at

373 ms

505 ms

gtm.js

110 ms

style.css

323 ms

polyfill.min.js

186 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Wilo.at, 55% (22 requests) were made to Cms.media.wilo.com and 28% (11 requests) were made to Wilo.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Cms.media.wilo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 41.4 kB (2%)

Content Size

2.4 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wilo.at main page is 2.4 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. 70% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 40.5 kB

  • Original 49.3 kB
  • After minification 49.1 kB
  • After compression 8.8 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 40.5 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 572 B

  • Original 2.2 MB
  • After minification 2.2 MB

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. Wilo images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 33 B

  • Original 7.2 kB
  • After minification 7.2 kB
  • After compression 7.2 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 271 B

  • Original 81.2 kB
  • After minification 81.2 kB
  • After compression 80.9 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. Wilo.at has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (26%)

Requests Now

35

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wilo.at

wilo.at

373 ms

505 ms

gtm.js

gtm.js

110 ms

style.css

style.css

323 ms

polyfill.min.js

polyfill.min.js

186 ms

Wilo-Global-Config-Script.js

Wilo-Global-Config-Script.js

637 ms

Retargeting-Config-Script.js

Retargeting-Config-Script.js

634 ms

plugin.js

plugin.js

666 ms

script.js

script.js

1029 ms

wilo-search.js

wilo-search.js

658 ms

wilo500689_768x432.jpg

wilo500689_768x432.jpg

814 ms

wilo539990_1600x800.jpg

wilo539990_1600x800.jpg

867 ms

wilo500689_1600x800.jpg

wilo500689_1600x800.jpg

617 ms

wilo520339_1600x800.jpg

wilo520339_1600x800.jpg

713 ms

wilo110125_1600x800.jpg

wilo110125_1600x800.jpg

624 ms

wilo56735_1.png

wilo56735_1.png

627 ms

wilo246407_1.png

wilo246407_1.png

720 ms

wilo428006_1.png

wilo428006_1.png

1229 ms

wilo22898_1.png

wilo22898_1.png

940 ms

wilo23452_1.png

wilo23452_1.png

952 ms

wilo27418_1.png

wilo27418_1.png

865 ms

wilo514174_768x_1.jpg

wilo514174_768x_1.jpg

531 ms

wilo514172_768x_1.jpg

wilo514172_768x_1.jpg

712 ms

wilo56138_768x432.jpg

wilo56138_768x432.jpg

878 ms

wilo537367_768x432.jpg

wilo537367_768x432.jpg

1173 ms

wilo110699_768x432.jpg

wilo110699_768x432.jpg

952 ms

wilo189215_768x432.jpg

wilo189215_768x432.jpg

1175 ms

wilo532253_768x432.jpg

wilo532253_768x432.jpg

1353 ms

wilo558693_768x432.jpg

wilo558693_768x432.jpg

1228 ms

wilo557519_768x432.jpg

wilo557519_768x432.jpg

1173 ms

wilo111211_20x20.jpg

wilo111211_20x20.jpg

1226 ms

wilo111210_20x20.jpg

wilo111210_20x20.jpg

1739 ms

wilologo.png

wilologo.png

515 ms

otSDKStub.js

otSDKStub.js

537 ms

notosans-regular.woff

notosans-regular.woff

713 ms

notosans-bold.woff

notosans-bold.woff

788 ms

wilo-icons.ttf

wilo-icons.ttf

573 ms

e4c873de-cad3-47c6-96ae-ad42ccb2392d.json

e4c873de-cad3-47c6-96ae-ad42ccb2392d.json

10 ms

location

location

60 ms

otBannerSdk.js

otBannerSdk.js

13 ms

Accessibility Review

wilo.at accessibility score

81

Accessibility Issues

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.

Impact

Issue

High

ARIA toggle fields do not have accessible names

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

wilo.at best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

wilo.at SEO score

79

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wilo.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Wilo.at 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

wilo.at

Open Graph data is detected on the main page of Wilo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: