Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

reinegger.net

reinegger.net - Webdesign, E-Learning und SEO Aachen

Page Load Speed

4.1 sec in total

First Response

364 ms

Resources Loaded

3.2 sec

Page Rendered

565 ms

reinegger.net screenshot

About Website

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

reinegger.net - Büro für interaktive Medien - Webdesign, E-Learning, Suchmaschinenoptimierung und alles was interaktiv ist

Visit reinegger.net

Key Findings

We analyzed Reinegger.net page load time and found that the first response time was 364 ms and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

reinegger.net performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value1.084

2/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

reinegger.net

364 ms

www.reinegger.net

337 ms

www.reinegger.net

611 ms

jquery.min.js

18 ms

bootstrap.min.js

339 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 96% of them (25 requests) were addressed to the original Reinegger.net, 4% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Reinegger.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 401.1 kB (33%)

Content Size

1.2 MB

After Optimization

807.6 kB

In fact, the total size of Reinegger.net main page is 1.2 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. 20% of websites need less resources to load. Images take 945.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 171.7 kB

  • Original 210.6 kB
  • After minification 207.1 kB
  • After compression 38.9 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 171.7 kB or 82% of the original size.

Image Optimization

-24%

Potential reduce by 229.4 kB

  • Original 945.9 kB
  • After minification 716.5 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. Obviously, Reinegger needs image optimization as it can save up to 229.4 kB or 24% 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 0 B

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

We found no issues to fix!

Requests Now

22

After Optimization

22

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Reinegger. According to our analytics all requests are already optimized.

Accessibility Review

reinegger.net accessibility score

89

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

Best Practices

reinegger.net 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

reinegger.net SEO score

99

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

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 Reinegger.net 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 Reinegger.net 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 description is not detected on the main page of Reinegger. 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: