Tools & Wizards About Us
wiwi.rwth-aachen.de screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

wiwi.rwth-aachen.de

RWTH AACHEN UNIVERSITY School of Business and Economics - English

Page Load Speed

6 sec in total

First Response

495 ms

Resources Loaded

5.2 sec

Page Rendered

263 ms

wiwi.rwth-aachen.de screenshot

About Website

Click here to check amazing Wiwi RWTH AACHEN content for Germany. Otherwise, check out these important facts you probably never knew about wiwi.rwth-aachen.de

RWTH Aachen University - School of Business and Economics - School of Business and Economics - Homepage

Visit wiwi.rwth-aachen.de

Key Findings

We analyzed Wiwi.rwth-aachen.de page load time and found that the first response time was 495 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

wiwi.rwth-aachen.de performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value120 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.793

5/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

wiwi.rwth-aachen.de

495 ms

wiwi.rwth-aachen.de

594 ms

159 ms

1151 ms

aw_mobile.asp

439 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that all of those requests were addressed to Wiwi.rwth-aachen.de and no external sources were called. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Wiwi.rwth-aachen.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.6 kB (12%)

Content Size

1.1 MB

After Optimization

945.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wiwi.rwth-aachen.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. 30% of websites need less resources to load. Images take 737.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 43.7 kB

  • Original 53.4 kB
  • After minification 52.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. 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 43.7 kB or 82% of the original size.

Image Optimization

-4%

Potential reduce by 28.3 kB

  • Original 737.9 kB
  • After minification 709.7 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. Wiwi RWTH AACHEN images are well optimized though.

JavaScript Optimization

-19%

Potential reduce by 49.6 kB

  • Original 267.4 kB
  • After minification 266.8 kB
  • After compression 217.8 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 49.6 kB or 19% of the original size.

CSS Optimization

-32%

Potential reduce by 4.0 kB

  • Original 12.4 kB
  • After minification 12.4 kB
  • After compression 8.4 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. Wiwi.rwth-aachen.de needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (38%)

Requests Now

29

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wiwi.rwth-aachen.de

wiwi.rwth-aachen.de

495 ms

wiwi.rwth-aachen.de

wiwi.rwth-aachen.de

594 ms

159 ms

1151 ms

aw_mobile.asp

aw_mobile.asp

439 ms

styles.css

styles.css

666 ms

jquery-3.6.0.js

jquery-3.6.0.js

1332 ms

jquery.ui-1.13.0.js

jquery.ui-1.13.0.js

1351 ms

__basic-behaviour.js

__basic-behaviour.js

569 ms

__base-modules.js

__base-modules.js

688 ms

__base-modules-2.js

__base-modules-2.js

908 ms

__rwth.js

__rwth.js

793 ms

customscript.js

customscript.js

776 ms

aw_mobile_jquery.js

aw_mobile_jquery.js

797 ms

show_picture.asp

show_picture.asp

352 ms

icon-sprites.png

icon-sprites.png

548 ms

teaser-wrapper-small-sprite.png

teaser-wrapper-small-sprite.png

113 ms

show_picture.asp

show_picture.asp

341 ms

show_picture.asp

show_picture.asp

768 ms

show_picture.asp

show_picture.asp

331 ms

border-50.png

border-50.png

223 ms

dotted-line-persona.png

dotted-line-persona.png

332 ms

line-color-teaser.png

line-color-teaser.png

440 ms

show_picture.asp

show_picture.asp

985 ms

show_picture.asp

show_picture.asp

1213 ms

show_picture.asp

show_picture.asp

896 ms

show_picture.asp

show_picture.asp

558 ms

show_picture.asp

show_picture.asp

875 ms

border-25.png

border-25.png

669 ms

icon-sprites-1.png

icon-sprites-1.png

780 ms

tablet.css

tablet.css

222 ms

tablet-portrait.css

tablet-portrait.css

223 ms

print.css

print.css

114 ms

Accessibility Review

wiwi.rwth-aachen.de accessibility score

90

Accessibility Issues

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

wiwi.rwth-aachen.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

SEO Factors

wiwi.rwth-aachen.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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wiwi.rwth-aachen.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 Wiwi.rwth-aachen.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

wiwi.rwth-aachen.de

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