4.2 sec in total
439 ms
3.4 sec
388 ms
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.beWe analyzed R3r.be page load time and found that the first response time was 439 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 60% of websites can load faster.
r3r.be performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value5.0 s
26/100
25%
Value8.4 s
19/100
10%
Value18,110 ms
0/100
30%
Value0.003
100/100
15%
Value27.3 s
0/100
10%
439 ms
87 ms
175 ms
17 ms
187 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 28% of them (15 requests) were addressed to the original R3r.be, 26% (14 requests) were made to Fonts.gstatic.com and 22% (12 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Youtube.com.
Page size can be reduced by 55.3 kB (9%)
629.2 kB
574.0 kB
In fact, the total size of R3r.be main page is 629.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 298.5 kB which makes up the majority of the site volume.
Potential reduce by 27.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 27.7 kB or 80% of the original size.
Potential reduce by 11.9 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.
Potential reduce by 12.6 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.
Potential reduce by 3.1 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.
Number of requests can be reduced by 12 (31%)
39
27
The browser has sent 39 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 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
r3r.be
439 ms
d7b6dcbca0.css
87 ms
95155764a0.js
175 ms
css
17 ms
6b37b6bc7d.css
187 ms
52f83381fc.css
184 ms
c339cff225.css
184 ms
ecf4d6d6a8.js
449 ms
af09b5c73d.js
186 ms
2-HrkyNCNvk
149 ms
_4rREfwzKmA
157 ms
sH7fdu_trmg
315 ms
PajC9Op45j0
156 ms
l3vjhpIisWM
269 ms
mo6kQjuVeY0
141 ms
9nyl5HRwklE
1110 ms
lnmNmyVvlCI
1286 ms
03.jpg
116 ms
banner%20Erbin.jpg
887 ms
banner%20Kwartel.jpg
887 ms
a7cdea4cd1.png
94 ms
digital-art-smokey-black-background_1920x1080.jpg
1279 ms
kaart%20Alverlanden%20RGB_edited1.jpg
1281 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff
11 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4k.woff
24 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff
25 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff
25 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff
28 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff
28 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVQ.woff
25 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkaVQ.woff
61 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVQ.woff
61 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVQ.woff
62 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVQ.woff
47 ms
memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVQ.woff
61 ms
www-player.css
20 ms
www-embed-player.js
65 ms
base.js
176 ms
0c83c4984e.png
995 ms
ad_status.js
914 ms
QgWDfoJvVp2VFZIVcozjRcqkiBvpbRKPHyLZQ1mikO8.js
648 ms
embed.js
354 ms
id
248 ms
Create
763 ms
Create
767 ms
Create
768 ms
Create
766 ms
Create
902 ms
Create
885 ms
id
669 ms
Create
785 ms
KFOmCnqEu92Fr1Mu4mxM.woff
709 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
709 ms
Create
696 ms
r3r.be accessibility score
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
<frame> or <iframe> elements do not have a title
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
<html> element does not have a [lang] attribute
r3r.be best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
r3r.be SEO score
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
Document uses legible font sizes
NL
N/A
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.
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: