Tools & Wizards About Us
rea.de screenshot

Report Summary

  • 77

    Performance

    Renders faster than
    84% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

rea.de

REA products and complete solutions for the industry | REA

Page Load Speed

3.2 sec in total

First Response

336 ms

Resources Loaded

2.6 sec

Page Rendered

342 ms

rea.de screenshot

About Website

Welcome to rea.de homepage info - get ready to check REA best content for United States right away, or after learning these important things about rea.de

Learn more about products and complete solutions of the REA Group and our four international business units JET, LABEL, VERIFIER and CARD.

Visit rea.de

Key Findings

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

Performance Metrics

rea.de performance score

77

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value140 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value7.1 s

51/100

10%

Network Requests Diagram

rea.de

336 ms

index.html

173 ms

uc.js

36 ms

ie9-10-b7b907c797f9130c7e78261aa754a474.css

106 ms

merged-cd8f615a3c280fe1291e4fc80da09f66-1695cf4a4dc810e192c3a4dd9e9de1df.css

321 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 84% of them (31 requests) were addressed to the original Rea.de, 8% (3 requests) were made to Matomo.rea.de and 5% (2 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (736 ms) belongs to the original domain Rea.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 147.4 kB (18%)

Content Size

840.1 kB

After Optimization

692.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Rea.de main page is 840.1 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 642.9 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 26.1 kB

  • Original 31.4 kB
  • After minification 24.6 kB
  • After compression 5.3 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 6.8 kB, which is 22% 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 26.1 kB or 83% of the original size.

Image Optimization

-5%

Potential reduce by 33.3 kB

  • Original 642.9 kB
  • After minification 609.6 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. REA images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 88.0 kB

  • Original 165.8 kB
  • After minification 165.8 kB
  • After compression 77.7 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 88.0 kB or 53% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (41%)

Requests Now

34

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rea.de

rea.de

336 ms

index.html

index.html

173 ms

uc.js

uc.js

36 ms

ie9-10-b7b907c797f9130c7e78261aa754a474.css

ie9-10-b7b907c797f9130c7e78261aa754a474.css

106 ms

merged-cd8f615a3c280fe1291e4fc80da09f66-1695cf4a4dc810e192c3a4dd9e9de1df.css

merged-cd8f615a3c280fe1291e4fc80da09f66-1695cf4a4dc810e192c3a4dd9e9de1df.css

321 ms

e9e07c5ca0.js

e9e07c5ca0.js

317 ms

vendor.js

vendor.js

736 ms

runtime.js

runtime.js

314 ms

rea-auxiliary.js

rea-auxiliary.js

315 ms

html5lightbox.js

html5lightbox.js

431 ms

app.js

app.js

526 ms

jquery.datetimepicker.min.js

jquery.datetimepicker.min.js

429 ms

parsley.min.js

parsley.min.js

431 ms

Tabs.min.js

Tabs.min.js

432 ms

Form.min.js

Form.min.js

527 ms

rea-systeme.svg

rea-systeme.svg

177 ms

industrial-marking-headquaters-1920x450.jpg

industrial-marking-headquaters-1920x450.jpg

720 ms

link-rea-jet-212x20.png

link-rea-jet-212x20.png

179 ms

link-rea-label-212x20.png

link-rea-label-212x20.png

280 ms

link-rea-verifier-212x20.png

link-rea-verifier-212x20.png

281 ms

link-rea-card-212x20.png

link-rea-card-212x20.png

282 ms

rea-jet-210x38.png

rea-jet-210x38.png

280 ms

rea-jet-teaser.jpg

rea-jet-teaser.jpg

514 ms

rea-label-276x38.png

rea-label-276x38.png

503 ms

rea-label-teaser.jpg

rea-label-teaser.jpg

504 ms

rea-verifier-354x38.png

rea-verifier-354x38.png

504 ms

rea-verifier-teaser.jpg

rea-verifier-teaser.jpg

512 ms

rea-card-252x38.png

rea-card-252x38.png

512 ms

rea-card-teaser.jpg

rea-card-teaser.jpg

513 ms

rea-career-400x38.png

rea-career-400x38.png

513 ms

rea-karriere-1110x278.jpg

rea-karriere-1110x278.jpg

718 ms

matomo.js

matomo.js

622 ms

icons.79c73223.woff

icons.79c73223.woff

534 ms

iframe_api

iframe_api

55 ms

www-widgetapi.js

www-widgetapi.js

4 ms

matomo.php

matomo.php

149 ms

configs.php

configs.php

236 ms

Accessibility Review

rea.de accessibility score

82

Accessibility Issues

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

Links do not have a discernible name

Best Practices

rea.de best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

rea.de SEO score

93

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

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

rea.de

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