Tools & Wizards About Us
r3r.be screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

r3r.be

Home

Page Load Speed

3.7 sec in total

First Response

398 ms

Resources Loaded

2.9 sec

Page Rendered

408 ms

r3r.be screenshot

About Website

Welcome to r3r.be homepage info - get ready to check R 3 best content right away, or after learning these important things about r3r.be

Visit r3r.be

Key Findings

We analyzed R3r.be page load time and found that the first response time was 398 ms and then it took 3.3 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

r3r.be performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value13.2 s

2/100

10%

TBT (Total Blocking Time)

Value18,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value36.5 s

0/100

10%

Network Requests Diagram

r3r.be

398 ms

d7b6dcbca0.css

107 ms

95155764a0.js

174 ms

css

21 ms

6b37b6bc7d.css

183 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 25% of them (15 requests) were addressed to the original R3r.be, 27% (16 requests) were made to Youtube.com and 24% (14 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain R3r.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 278.9 kB (25%)

Content Size

1.1 MB

After Optimization

835.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of R3r.be 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. Only a small number of websites need less resources to load. Javascripts take 640.8 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 27.7 kB

  • Original 34.6 kB
  • After minification 34.6 kB
  • After compression 6.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 27.7 kB or 80% of the original size.

Image Optimization

-4%

Potential reduce by 11.9 kB

  • Original 298.5 kB
  • After minification 286.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. R 3 images are well optimized though.

JavaScript Optimization

-37%

Potential reduce by 236.3 kB

  • Original 640.8 kB
  • After minification 640.8 kB
  • After compression 404.5 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 236.3 kB or 37% of the original size.

CSS Optimization

-2%

Potential reduce by 3.1 kB

  • Original 140.8 kB
  • After minification 140.8 kB
  • After compression 137.7 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. R3r.be has all CSS files already compressed.

Requests Breakdown

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

Requests Now

44

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

r3r.be

r3r.be

398 ms

d7b6dcbca0.css

d7b6dcbca0.css

107 ms

95155764a0.js

95155764a0.js

174 ms

css

css

21 ms

6b37b6bc7d.css

6b37b6bc7d.css

183 ms

52f83381fc.css

52f83381fc.css

184 ms

c339cff225.css

c339cff225.css

212 ms

ecf4d6d6a8.js

ecf4d6d6a8.js

1200 ms

af09b5c73d.js

af09b5c73d.js

211 ms

2-HrkyNCNvk

2-HrkyNCNvk

130 ms

_4rREfwzKmA

_4rREfwzKmA

134 ms

sH7fdu_trmg

sH7fdu_trmg

262 ms

PajC9Op45j0

PajC9Op45j0

135 ms

l3vjhpIisWM

l3vjhpIisWM

183 ms

mo6kQjuVeY0

mo6kQjuVeY0

144 ms

9nyl5HRwklE

9nyl5HRwklE

974 ms

lnmNmyVvlCI

lnmNmyVvlCI

1018 ms

03.jpg

03.jpg

619 ms

banner%20Erbin.jpg

banner%20Erbin.jpg

928 ms

banner%20Kwartel.jpg

banner%20Kwartel.jpg

618 ms

a7cdea4cd1.png

a7cdea4cd1.png

177 ms

digital-art-smokey-black-background_1920x1080.jpg

digital-art-smokey-black-background_1920x1080.jpg

1023 ms

kaart%20Alverlanden%20RGB_edited1.jpg

kaart%20Alverlanden%20RGB_edited1.jpg

1022 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

11 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4k.woff

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

20 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

18 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

31 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVQ.woff

29 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkaVQ.woff

529 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVQ.woff

210 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVQ.woff

210 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVQ.woff

33 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVQ.woff

210 ms

www-player.css

www-player.css

20 ms

www-embed-player.js

www-embed-player.js

94 ms

base.js

base.js

180 ms

www-player.css

www-player.css

55 ms

www-embed-player.js

www-embed-player.js

130 ms

base.js

base.js

492 ms

ad_status.js

ad_status.js

788 ms

GkV5yKS0-OANEhjyXXxuzTYu8mVL2o5guieYvUh3n1c.js

GkV5yKS0-OANEhjyXXxuzTYu8mVL2o5guieYvUh3n1c.js

993 ms

embed.js

embed.js

637 ms

0c83c4984e.png

0c83c4984e.png

242 ms

V6n6N6lR58V6YvKWzRgNRm2UbnEaYiTpGDY0zZzDx9c.js

V6n6N6lR58V6YvKWzRgNRm2UbnEaYiTpGDY0zZzDx9c.js

370 ms

embed.js

embed.js

197 ms

id

id

189 ms

ZOxatAyGP5lpnWZuZ8HWLHoI3f7SWXtSvYonPMa35nU.js

ZOxatAyGP5lpnWZuZ8HWLHoI3f7SWXtSvYonPMa35nU.js

275 ms

Create

Create

661 ms

Create

Create

659 ms

Create

Create

664 ms

Create

Create

664 ms

Create

Create

667 ms

Create

Create

659 ms

Create

Create

810 ms

Create

Create

666 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

487 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

488 ms

Accessibility Review

r3r.be accessibility score

88

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

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

High

Links do not have a discernible name

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

Best Practices

r3r.be 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

High

Page has valid source maps

SEO Factors

r3r.be SEO score

92

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

    NL

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise R3r.be can be misinterpreted by Google and other search engines. Our service has detected that Dutch 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 R3r.be 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

r3r.be

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