Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

rwe.de

RWE | Our energy for a sustainable life.

Page Load Speed

7.3 sec in total

First Response

761 ms

Resources Loaded

5.7 sec

Page Rendered

834 ms

About Website

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

We dared to make a new start: With over 125 years of history, RWE has fundamentally changed and is now a leading supplier of renewable energies worldwide.

Visit rwe.de

Key Findings

We analyzed Rwe.de page load time and found that the first response time was 761 ms and then it took 6.6 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

rwe.de performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value45.3 s

0/100

25%

SI (Speed Index)

Value18.7 s

0/100

10%

TBT (Total Blocking Time)

Value4,550 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.131

81/100

15%

TTI (Time to Interactive)

Value36.1 s

0/100

10%

Network Requests Diagram

www.rwe.com

761 ms

435 ms

nkStyles.20240521.9.min.css

312 ms

uikit.20240521.9.min.css

871 ms

vendor.20240521.9.min.js

836 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Rwe.de, 2% (1 request) were made to Googletagmanager.com and 2% (1 request) were made to Tools.eurolandir.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Rwe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 789.7 kB (14%)

Content Size

5.5 MB

After Optimization

4.7 MB

In fact, the total size of Rwe.de main page is 5.5 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 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 160.0 kB

  • Original 185.0 kB
  • After minification 162.1 kB
  • After compression 25.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. This page needs HTML code to be minified as it can gain 22.9 kB, which is 12% 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 160.0 kB or 86% of the original size.

Image Optimization

-17%

Potential reduce by 626.1 kB

  • Original 3.7 MB
  • After minification 3.1 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. Obviously, RWE needs image optimization as it can save up to 626.1 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 2.2 kB

  • Original 1.5 MB
  • After minification 1.5 MB
  • After compression 1.5 MB

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

-1%

Potential reduce by 1.4 kB

  • Original 107.4 kB
  • After minification 107.4 kB
  • After compression 106.0 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. Rwe.de has all CSS files already compressed.

Requests Breakdown

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

Requests Now

38

After Optimization

28

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

Accessibility Review

rwe.de accessibility score

53

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

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

High

[aria-*] attributes are not valid or misspelled

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

rwe.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

rwe.de SEO score

77

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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