8.2 sec in total
572 ms
4 sec
3.6 sec
Visit richardrae.de now to see the best up-to-date Richard Rae content and also check out these interesting facts you probably never knew about richardrae.de
Visit richardrae.deWe analyzed Richardrae.de page load time and found that the first response time was 572 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
richardrae.de performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value5.8 s
15/100
25%
Value8.1 s
21/100
10%
Value660 ms
45/100
30%
Value0.011
100/100
15%
Value14.5 s
9/100
10%
572 ms
305 ms
202 ms
311 ms
306 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 21% of them (19 requests) were addressed to the original Richardrae.de, 34% (31 requests) were made to Usercontent.one and 14% (13 requests) were made to D3nn82uaxijpm6.cloudfront.net. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Usercontent.one.
Page size can be reduced by 769.8 kB (11%)
6.7 MB
5.9 MB
In fact, the total size of Richardrae.de main page is 6.7 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. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 111.5 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 111.5 kB or 75% of the original size.
Potential reduce by 416.4 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. Richard Rae images are well optimized though.
Potential reduce by 236.8 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.8 kB or 19% of the original size.
Potential reduce by 5.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. Richardrae.de has all CSS files already compressed.
Number of requests can be reduced by 28 (36%)
77
49
The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Richard Rae. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.richardrae.de
572 ms
style.css
305 ms
merriweather-plus-montserrat-plus-inconsolata.css
202 ms
genericons.css
311 ms
style.css
306 ms
blocks.css
203 ms
jquery.js
535 ms
jquery-migrate.js
401 ms
widgets.js
7 ms
skip-link-focus-fix.js
205 ms
functions.js
300 ms
cropped-13640935_10154421724418478_2435218486946085053_o-1.jpg
730 ms
57c18caf9b2d14085aee1775535237c3
124 ms
JQYsGaQ9U2Q
261 ms
image-1024x695.png
1141 ms
1-1024x768.jpeg
1546 ms
image-1-1024x695.png
1445 ms
2-1024x768.jpeg
1542 ms
image-2-1024x695.png
1447 ms
3-1024x768.jpeg
1443 ms
IMG_5262-1024x768.jpeg
1445 ms
237435733-681x1024.jpeg
1649 ms
237459719-682x1024.jpeg
1648 ms
237487440-1024x682.jpeg
1651 ms
237502677-1-682x1024.jpeg
1749 ms
15257ADC-7C19-43C8-9644-267B605615BC-1024x768.jpeg
1744 ms
AD7159F8-D848-403C-A173-FFD0E619E382-1024x768.jpeg
1649 ms
217842080-1024x682.jpeg
1851 ms
217897739-682x1024.jpeg
1750 ms
217860011-1024x684.jpeg
1753 ms
217958076-1024x682.jpeg
1753 ms
EFA72354-B4CB-48F2-A180-FF7B97C4C3EB-1024x768.jpeg
1847 ms
F72369F1-96AB-47F3-B877-82D863E47F85_1_105_c-1024x768.jpeg
1853 ms
Koppenberg-1024x768.jpeg
1853 ms
FA633B23-F85A-48E0-87DF-A5557A19A82E_1_105_c-1024x768.jpeg
1857 ms
B21E3D7F-7886-49EF-B584-64CFC951F2A9-1024x768.jpeg
1856 ms
image.png
2148 ms
F71D3D01-B7E8-46F9-BE34-7D248F321EF1-683x1024.jpeg
1951 ms
gptempdownload-2-1024x768.jpg
1957 ms
gptempdownload-1-1024x768.jpg
1958 ms
gptempdownload-4-1024x768.jpg
1958 ms
gptempdownload-3-1024x768.jpg
1959 ms
gptempdownload-2-1-1024x768.jpg
2055 ms
gptempdownload-5-1024x768.jpg
2059 ms
57c18caf9b2d14085aee1775535237c3
380 ms
34cc750d3e2ad872e7cb23bc1092458be794695b
509 ms
montserrat-all-700-normal.woff
140 ms
montserrat-all-400-normal.woff
504 ms
merriweather-all-400-normal.woff
504 ms
merriweather-all-700-normal.woff
504 ms
merriweather-all-900-normal.woff
504 ms
merriweather-all-400-italic.woff
504 ms
merriweather-all-700-italic.woff
504 ms
merriweather-all-900-italic.woff
599 ms
Genericons.svg
714 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
1 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
160 ms
www-player.css
40 ms
www-embed-player.js
77 ms
base.js
101 ms
settings
382 ms
ad_status.js
222 ms
YpaxWjHVNNO6KZk05PsGAol2GFYfBj4WvF05Ro9VHVE.js
176 ms
embed.js
39 ms
strava-widget-6fc80ee6bebee918b12e72ed05ca8cc7a30473960f5dd2f6bcb1d33ceb550783.css
223 ms
global-c6da620d.css
213 ms
runtime-64bebda3ca5eaeab9579.js
234 ms
21944-240906e77f25c9c206d0.js
236 ms
10603-0d2522db11b3d61a86c0.js
233 ms
20459-3bc8c6cf573225ac4291.js
261 ms
73170-6a2a12718c143cf50118.js
237 ms
global-1cd4fdee497f548d12a0.js
260 ms
strava-head-ceb9519e86fef9d99673025e70fdccf83c2eef2f91b8899ddebc50ec183ba5d9.js
263 ms
mapbox-41237022ddc77795df30454a57d30eb5783829220796c9784f6daaf690f26ac3.js
268 ms
en-US-712d256347fff6021e9c5f49aa5733f80ea714d6291d59fbbb0c760aa9f021c0.js
268 ms
application-35fb3d833b6ac1fd03e76741286320e16b3bef64cdb547033ad0184413114310.js
309 ms
manifest-14f15fc01eaabbc5f4c8b205d10f57b06aca17bb87e3345f642873d4a220604c.js
309 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
258 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
267 ms
button.856debeac157d9669cf51e73a08fbc93.js
116 ms
Create
180 ms
id
140 ms
embeds
261 ms
PLVQIHMRW7ZHDHAGDPNNSNYBTSA672RWWVA3GAFA57DKASW4S2GFRAHJJMELKL25W3Q54VKLRVTVD5TFQAWHYBLDVCYUDYTIU4SQ====
467 ms
4W2RVMMBN663WCVOEW4SPNR3O75L4CZQULFZBFRQJFGHDUKVLYKUTFHVYW6IK7LISHES6EAAJNFOFATFWGOGL77QKBWXZFLR537A====
699 ms
U2CGFXY7NWVTF5M3QNO7BULQKPBAXHNSGN3DJRCXOQDFMUZYMJK3K7DQI7IXQ3VDFQKT5ZOCZBWB4BTBHHCOJQ45VLRWFEKNPLDA====
605 ms
54W7SNMTNALDLKCMA3NIPQOECZKGMHFBRC3F4TA3REJJBYTYDFIFDAWP6NBVA5GVYQIGU6HKEMET4PIPGX6QOJQIWSZZISGK63PQ====
654 ms
SU3PORJ57YF4DMA362MTXXUF52KEZEI54EPPOKSZXOGHQQQSRS6CACQWZB63VGJLIOO73LTAK3SELZOP4WGE2SRBPZAARBRZH3EA====
642 ms
follow_button.2f70fb173b9000da126c79afe2098f02.en-gb.html
220 ms
GenerateIT
91 ms
richardrae.de 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
richardrae.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
richardrae.de 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Richardrae.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Richardrae.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.
richardrae.de
Open Graph description is not detected on the main page of Richard Rae. 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: