2.9 sec in total
681 ms
2 sec
188 ms
Visit rexin.de now to see the best up-to-date Rexin content and also check out these interesting facts you probably never knew about rexin.de
Visit rexin.deWe analyzed Rexin.de page load time and found that the first response time was 681 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
rexin.de performance score
name
value
score
weighting
Value4.7 s
12/100
10%
Value15.3 s
0/100
25%
Value13.1 s
2/100
10%
Value1,960 ms
8/100
30%
Value0.003
100/100
15%
Value15.8 s
6/100
10%
681 ms
248 ms
181 ms
366 ms
184 ms
Our browser made a total of 39 requests to load all elements on the main page. We found that 69% of them (27 requests) were addressed to the original Rexin.de, 18% (7 requests) were made to Static.xx.fbcdn.net and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (681 ms) belongs to the original domain Rexin.de.
Page size can be reduced by 209.2 kB (60%)
348.6 kB
139.5 kB
In fact, the total size of Rexin.de main page is 348.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 199.3 kB which makes up the majority of the site volume.
Potential reduce by 12.6 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 12.6 kB or 72% of the original size.
Potential reduce by 3.2 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. Rexin images are well optimized though.
Potential reduce by 120.9 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 120.9 kB or 61% of the original size.
Potential reduce by 72.4 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. Rexin.de needs all CSS files to be minified and compressed as it can save up to 72.4 kB or 86% of the original size.
Number of requests can be reduced by 25 (68%)
37
12
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rexin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
www.rexin.de
681 ms
wp-emoji-release.min.js
248 ms
contact.css
181 ms
style.css
366 ms
cardozafacebook.css
184 ms
templates.css
185 ms
gmw.css
185 ms
jquery.js
537 ms
jquery-migrate.min.js
274 ms
contact.js
275 ms
cardozafacebook.js
274 ms
responsive-modernizr.js
336 ms
external-tracking.min.js
367 ms
frontend.css
367 ms
responsive-scripts.js
367 ms
responsive-plugins.js
368 ms
jquery.colorbox.min.js
395 ms
gmw.js
396 ms
wp-embed.min.js
396 ms
show-excerpt.js
397 ms
ga.js
132 ms
staticmap
181 ms
top_rexinde.png
131 ms
rexinde_teaser3.jpg
129 ms
rss.png
126 ms
twitter-icon.png
132 ms
facebook-icon.png
138 ms
youtube-icon.png
138 ms
googleplus-icon.png
179 ms
likebox.php
127 ms
__utm.gif
16 ms
collect
54 ms
hDvwL1_H7g-.css
18 ms
q68gy-v_YMF.js
26 ms
FJmpeSpHpjS.js
60 ms
0wM5s1Khldu.js
58 ms
1bNoFZUdlYZ.js
58 ms
I6-MnjEovm5.js
3 ms
pQrUxxo5oQp.js
6 ms
rexin.de accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
rexin.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
rexin.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rexin.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Rexin.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.
rexin.de
Open Graph description is not detected on the main page of Rexin. 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: