Tools & Wizards About Us
stawag.de screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

stawag.de

STAWAG – Stadt- und Städteregionswerke Aachen AG | STAWAG – Stadt- und Städteregionswerke Aachen AG

Page Load Speed

3.6 sec in total

First Response

331 ms

Resources Loaded

2.8 sec

Page Rendered

405 ms

stawag.de screenshot

About Website

Welcome to stawag.de homepage info - get ready to check STAWAG best content for Germany right away, or after learning these important things about stawag.de

STAWAG – Stadt- und Städteregionswerke Aachen AG: Zuverlässiger und kundenfreundlicher Dienstleister rund um Strom, Gas, Wärme, Wasser und Abwasser in Aachen.

Visit stawag.de

Key Findings

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

Performance Metrics

stawag.de performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value9.1 s

13/100

10%

TBT (Total Blocking Time)

Value510 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

stawag.de

331 ms

www.stawag.de

1352 ms

flipbook.style.css

110 ms

font-awesome.css

341 ms

jquery.fancybox.css

321 ms

Our browser made a total of 40 requests to load all elements on the main page. We found that 85% of them (34 requests) were addressed to the original Stawag.de, 5% (2 requests) were made to Cdn.eye-able.com and 3% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Stawag.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 69.3 kB (11%)

Content Size

628.2 kB

After Optimization

558.9 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-79%

Potential reduce by 35.7 kB

  • Original 45.4 kB
  • After minification 38.0 kB
  • After compression 9.7 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. This page needs HTML code to be minified as it can gain 7.4 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.7 kB or 79% of the original size.

Image Optimization

-7%

Potential reduce by 33.6 kB

  • Original 450.7 kB
  • After minification 417.1 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. STAWAG images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 20 B

  • Original 132.1 kB
  • After minification 132.1 kB
  • After compression 132.1 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.

Requests Breakdown

Number of requests can be reduced by 19 (58%)

Requests Now

33

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

stawag.de

stawag.de

331 ms

www.stawag.de

www.stawag.de

1352 ms

flipbook.style.css

flipbook.style.css

110 ms

font-awesome.css

font-awesome.css

341 ms

jquery.fancybox.css

jquery.fancybox.css

321 ms

style.min.css

style.min.css

428 ms

jquery-2.2.4.min.js

jquery-2.2.4.min.js

26 ms

www.stawag.de.js

www.stawag.de.js

378 ms

eyeAble.js

eyeAble.js

760 ms

app.bundle.js

app.bundle.js

716 ms

merged-dacc34bdbf70a0c721efe0fff42818c0-4c17ace8e4ceb369c74b0e8021de98bc.js.gzip

merged-dacc34bdbf70a0c721efe0fff42818c0-4c17ace8e4ceb369c74b0e8021de98bc.js.gzip

318 ms

jquery-ui.min.js

jquery-ui.min.js

323 ms

core.js

core.js

440 ms

jquery.cookie.js

jquery.cookie.js

439 ms

GSASuggestSource.js

GSASuggestSource.js

440 ms

GSASearchSource.js

GSASearchSource.js

451 ms

stawag.js

stawag.js

569 ms

googleAnalytics.js

googleAnalytics.js

569 ms

flipbook.min.js

flipbook.min.js

649 ms

flipbook.starter.js

flipbook.starter.js

569 ms

micromodal.min.js

micromodal.min.js

43 ms

1.css

1.css

59 ms

gtm.js

gtm.js

119 ms

stawag_header_bg_desktop.png

stawag_header_bg_desktop.png

210 ms

stawag-logo.svg

stawag-logo.svg

171 ms

csm_Header_%C3%96cher_M%C3%A4rz_cba25b84ef.jpg

csm_Header_%C3%96cher_M%C3%A4rz_cba25b84ef.jpg

173 ms

question-mark.svg

question-mark.svg

173 ms

csm_Teaser-Umzug_82aa9969ca.jpg

csm_Teaser-Umzug_82aa9969ca.jpg

289 ms

csm_Teaser_Gasmagellage_c1b739352d.jpg

csm_Teaser_Gasmagellage_c1b739352d.jpg

377 ms

csm_teaser_w%C3%A4rmeplus_6f28daa824.jpg

csm_teaser_w%C3%A4rmeplus_6f28daa824.jpg

290 ms

TOP-Siegel.png

TOP-Siegel.png

477 ms

Imug-Siegel.png

Imug-Siegel.png

414 ms

Focus.png

Focus.png

339 ms

energie-impuls.png

energie-impuls.png

362 ms

b03c5cd2-c6ad-4764-9cab-bf6211f181a7.woff

b03c5cd2-c6ad-4764-9cab-bf6211f181a7.woff

363 ms

icons.woff

icons.woff

391 ms

52382db1-3de6-473e-b9c0-3cb5e70e80a2.woff

52382db1-3de6-473e-b9c0-3cb5e70e80a2.woff

428 ms

97252acf-16d3-480c-8269-89ea815e4179.woff

97252acf-16d3-480c-8269-89ea815e4179.woff

469 ms

stawag_footer_bg_desktop.png

stawag_footer_bg_desktop.png

450 ms

print.min.css

print.min.css

109 ms

Accessibility Review

stawag.de accessibility score

66

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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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

Form elements do not have associated labels

High

Links do not have a discernible name

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.

Best Practices

stawag.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

stawag.de SEO score

100

Search Engine Optimization Advices

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 Stawag.de 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 Stawag.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

stawag.de

Open Graph description is not detected on the main page of STAWAG. 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: