4.8 sec in total
449 ms
3.9 sec
424 ms
Visit rehau.bg now to see the best up-to-date Rehau content and also check out these interesting facts you probably never knew about rehau.bg
Полиемрно базирани решения за глобалните проблеми като енергийна ефективност, управление на водите, възобновяеми енергийни източници, бъдеща мобилност и бъдещ живот.
Visit rehau.bgWe analyzed Rehau.bg page load time and found that the first response time was 449 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
rehau.bg performance score
name
value
score
weighting
Value3.2 s
44/100
10%
Value9.5 s
0/100
25%
Value8.8 s
15/100
10%
Value5,350 ms
0/100
30%
Value0.07
96/100
15%
Value11.7 s
17/100
10%
449 ms
1329 ms
35 ms
81 ms
533 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Rehau.bg, 81% (47 requests) were made to Rehau.com and 9% (5 requests) were made to Etracker.de. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Rehau.com.
Page size can be reduced by 55.5 kB (36%)
155.6 kB
100.2 kB
In fact, the total size of Rehau.bg main page is 155.6 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. Javascripts take 88.2 kB which makes up the majority of the site volume.
Potential reduce by 54.8 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 12.1 kB, which is 18% 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 54.8 kB or 81% of the original size.
Potential reduce by 714 B
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.
Number of requests can be reduced by 13 (24%)
54
41
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rehau. 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 as a result speed up the page load time.
rehau.bg
449 ms
1329 ms
bg-bg.css
35 ms
bg-bg.js
81 ms
e.js
533 ms
analytics.js
48 ms
form.php
624 ms
logo-print-jpg-data.jpg
64 ms
logodesktop-png-data.png
64 ms
bt-search-png-data.png
60 ms
ibau-0073-42160.jpg
62 ms
iml-00541-140757.jpg
61 ms
594-d049-193949.jpg
60 ms
news0255de-423756.jpg
61 ms
igt-0385---399609.jpg
165 ms
sprite20px-png-data.png
61 ms
980-d220-262621.jpg
291 ms
aas-d567-198334.jpg
169 ms
bw-eks-d230-202259.jpg
211 ms
au0084-1280x460-209005.jpg
271 ms
r10-d012-1280x460-208347.jpg
243 ms
463-d015---7490.jpg
316 ms
774-d006-437753--1-.jpg
321 ms
866-d024-01---196977.jpg
361 ms
igt-0366-360879.jpg
473 ms
aas-d315---31194.jpg
498 ms
uniform-bg-input-png-data.png
293 ms
al-d1303---41993809-7-5.jpg
497 ms
facebook-png-data.png
317 ms
delicious-png-data.png
319 ms
twitter-png-data.png
321 ms
recommendationicon-png-data.png
323 ms
uniform-sprite-png-data.png
358 ms
facebook-png-data.png
326 ms
youtube-png-data.png
329 ms
2b7ddafc-2d87-44b4-8271-5ecd2f90414d-woff-data.raw
334 ms
collect
15 ms
cde92697-8c36-491a-a0e6-d93f889eb4e5-woff-data.raw
410 ms
jquery-1.8.3.min.js
489 ms
382 ms
t.js
642 ms
trackingCode.js
147 ms
go-top-png-data.png
36 ms
igt-0385---399609.jpg
1360 ms
980-d220-262621.jpg
747 ms
aas-d567-198334.jpg
748 ms
bw-eks-d230-202259.jpg
553 ms
au0084-1280x460-209005.jpg
625 ms
r10-d012-1280x460-208347.jpg
740 ms
463-d015---7490.jpg
720 ms
774-d006-437753--1-.jpg
787 ms
866-d024-01---196977.jpg
1099 ms
igt-0366-360879.jpg
914 ms
aas-d315---31194.jpg
896 ms
al-d1303---41993809-7-5.jpg
897 ms
bx-loader-gif-data.gif
791 ms
cnt_js.php
132 ms
cntcc
138 ms
rehau.bg accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
rehau.bg best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
rehau.bg SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
BG
BG
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rehau.bg can be misinterpreted by Google and other search engines. Our service has detected that Bulgarian is used on the page, and it matches the claimed language. Our system also found out that Rehau.bg 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.
rehau.bg
Open Graph data is detected on the main page of Rehau. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: