6.2 sec in total
1.3 sec
4.1 sec
851 ms
Visit martinrein.com now to see the best up-to-date Martinrein content and also check out these interesting facts you probably never knew about martinrein.com
Visit martinrein.comWe analyzed Martinrein.com page load time and found that the first response time was 1.3 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
martinrein.com performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value0.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
1347 ms
9 ms
96 ms
282 ms
26 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 19% of them (15 requests) were addressed to the original Martinrein.com, 9% (7 requests) were made to Fonts.gstatic.com and 8% (6 requests) were made to Cm.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Martinrein.com.
Page size can be reduced by 925.2 kB (36%)
2.6 MB
1.6 MB
In fact, the total size of Martinrein.com main page is 2.6 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. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 220.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. 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 220.3 kB or 89% of the original size.
Potential reduce by 26.1 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. Martinrein images are well optimized though.
Potential reduce by 602.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 602.7 kB or 72% of the original size.
Potential reduce by 76.0 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. Martinrein.com needs all CSS files to be minified and compressed as it can save up to 76.0 kB or 76% of the original size.
Number of requests can be reduced by 44 (77%)
57
13
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Martinrein. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.martinrein.com
1347 ms
shareaholic.js
9 ms
styles.css
96 ms
twitter-feed.css
282 ms
css
26 ms
genericons.css
284 ms
style.css
192 ms
jquery.js
380 ms
jquery-migrate.min.js
284 ms
jquery.form.min.js
283 ms
scripts.js
285 ms
jquery.masonry.min.js
371 ms
functions.js
374 ms
e-201611.js
5 ms
e-201611.js
26 ms
56490bcb3075ede506defd0df011673c.json
31 ms
540x293_20140112_90af157ccf485936767234f9d03728d0_jpg.jpg
277 ms
landschaft.jpg
760 ms
cropped-960x265_Geld-ist.png
757 ms
Monteurin-e1442949254227.jpg
325 ms
Streit_Fotolia_37618493_XS.jpg
326 ms
540x293_20140108_cbefab2b0502fba75fa0e79bf80fc41c_jpg.jpg
269 ms
ga.js
80 ms
shrMain.min.js
19 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
161 ms
nj47mAZe0mYUIySgfn0wpQ.ttf
162 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
162 ms
4cKlrioa77J2iqTqBgkRWg.ttf
162 ms
WyXtbLelkv62W9rJf1sl7ohV7ohV7ohV7ohV7ohV7RK3pFr+gVvaJX9Ipe0St6tV6tV+vVerVerVfr1Xq1Xq3X6DV6jV7T9Yr3qXifivepdPIfY1AvlQABUnNepwAA
4 ms
LqowQDslGv4DmUBAfWa2Vw.ttf
163 ms
2HG_tEPiQ4Z6795cGfdivKCWcynf_cDxXwCLxiixG1c.ttf
161 ms
HkF_qI1x_noxlxhrhMQYEKCWcynf_cDxXwCLxiixG1c.ttf
160 ms
g.gif
106 ms
__utm.gif
63 ms
jquery.min.js
56 ms
analytics.js
111 ms
pageview.gif
41 ms
vglnk.js
10 ms
partners.js
43 ms
pixel.gif
8 ms
pixel.gif
8 ms
sholic.js
22 ms
usermatch
113 ms
beacon.js
9 ms
cms-sh2c.html
73 ms
eexelate.js
15 ms
95 ms
ep
40 ms
58 ms
ping_match.gif
5 ms
2964
30 ms
pixel
44 ms
usermatch
70 ms
net.php
10 ms
ep
24 ms
generic
9 ms
pixel
26 ms
pixel
17 ms
generic
9 ms
pixel
40 ms
match-result
106 ms
pixel
37 ms
xrefid.xgi
26 ms
141 ms
casale
135 ms
i.gif
178 ms
pixel
49 ms
rs
40 ms
pixel.gif
82 ms
crum
121 ms
crum
115 ms
pixel.gif
40 ms
check
14 ms
cfcm.ashx
8 ms
rum
54 ms
xrefid.xgi
7 ms
ermcm
30 ms
rum
69 ms
rum
67 ms
martinrein.com 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.
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
martinrein.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
martinrein.com SEO score
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Martinrein.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Martinrein.com 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.
martinrein.com
Open Graph description is not detected on the main page of Martinrein. 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: