7.7 sec in total
345 ms
3.3 sec
4.1 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 345 ms and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
richardrae.de performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value4.1 s
46/100
25%
Value5.7 s
51/100
10%
Value570 ms
52/100
30%
Value0.011
100/100
15%
Value12.9 s
13/100
10%
345 ms
132 ms
172 ms
259 ms
202 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 23% of them (22 requests) were addressed to the original Richardrae.de, 33% (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 (1.9 sec) relates to the external source Usercontent.one.
Page size can be reduced by 550.6 kB (9%)
6.5 MB
5.9 MB
In fact, the total size of Richardrae.de main page is 6.5 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. 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 5.1 MB which makes up the majority of the site volume.
Potential reduce by 115.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 115.3 kB or 76% 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 13.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. This website has mostly compressed JavaScripts.
Potential reduce by 5.2 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 31 (38%)
82
51
The browser has sent 82 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 24 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.richardrae.de
345 ms
twemoji.js
132 ms
wp-emoji.js
172 ms
style.css
259 ms
classic-themes.css
202 ms
merriweather-plus-montserrat-plus-inconsolata.css
202 ms
genericons.css
303 ms
style.css
217 ms
blocks.css
255 ms
jquery.js
613 ms
jquery-migrate.js
305 ms
widgets.js
46 ms
skip-link-focus-fix.js
261 ms
functions.js
301 ms
cropped-13640935_10154421724418478_2435218486946085053_o-1.jpg
441 ms
57c18caf9b2d14085aee1775535237c3
90 ms
JQYsGaQ9U2Q
287 ms
image-1024x695.png
923 ms
1-1024x768.jpeg
1322 ms
image-1-1024x695.png
1206 ms
2-1024x768.jpeg
1321 ms
image-2-1024x695.png
1203 ms
3-1024x768.jpeg
1320 ms
IMG_5262-1024x768.jpeg
1364 ms
237435733-681x1024.jpeg
1409 ms
237459719-682x1024.jpeg
1359 ms
237487440-1024x682.jpeg
1569 ms
237502677-1-682x1024.jpeg
1594 ms
15257ADC-7C19-43C8-9644-267B605615BC-1024x768.jpeg
1523 ms
AD7159F8-D848-403C-A173-FFD0E619E382-1024x768.jpeg
1442 ms
217842080-1024x682.jpeg
1569 ms
217897739-682x1024.jpeg
1487 ms
217860011-1024x684.jpeg
1537 ms
217958076-1024x682.jpeg
1576 ms
EFA72354-B4CB-48F2-A180-FF7B97C4C3EB-1024x768.jpeg
1611 ms
F72369F1-96AB-47F3-B877-82D863E47F85_1_105_c-1024x768.jpeg
1615 ms
Koppenberg-1024x768.jpeg
1665 ms
FA633B23-F85A-48E0-87DF-A5557A19A82E_1_105_c-1024x768.jpeg
1672 ms
B21E3D7F-7886-49EF-B584-64CFC951F2A9-1024x768.jpeg
1666 ms
image.png
1933 ms
F71D3D01-B7E8-46F9-BE34-7D248F321EF1-683x1024.jpeg
1697 ms
gptempdownload-2-1024x768.jpg
1702 ms
gptempdownload-1-1024x768.jpg
1768 ms
gptempdownload-4-1024x768.jpg
1750 ms
gptempdownload-3-1024x768.jpg
1774 ms
gptempdownload-2-1-1024x768.jpg
1784 ms
gptempdownload-5-1024x768.jpg
1788 ms
57c18caf9b2d14085aee1775535237c3
282 ms
34cc750d3e2ad872e7cb23bc1092458be794695b
348 ms
montserrat-all-700-normal.woff
206 ms
montserrat-all-400-normal.woff
274 ms
merriweather-all-400-normal.woff
214 ms
merriweather-all-700-normal.woff
341 ms
merriweather-all-900-normal.woff
274 ms
merriweather-all-400-italic.woff
340 ms
merriweather-all-700-italic.woff
679 ms
merriweather-all-900-italic.woff
340 ms
Genericons.svg
686 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
1 ms
1f600.svg
138 ms
widget_iframe.2f70fb173b9000da126c79afe2098f02.html
600 ms
1f642.svg
122 ms
www-player.css
54 ms
www-embed-player.js
74 ms
base.js
141 ms
strava-widget-57f8c0aa9220188ce714dc93618b4cb11455e84b230e835418f41d1701e545f6.css
457 ms
global-c6da620d.css
404 ms
runtime-c3e21f700a03d0048acc.js
404 ms
21944-240906e77f25c9c206d0.js
479 ms
10603-0d2522db11b3d61a86c0.js
455 ms
59306-96215e282c5134f91839.js
480 ms
73170-6a2a12718c143cf50118.js
499 ms
global-090250b91a2f60cff8af.js
500 ms
strava-head-1d4a9d2681e471734266f7b43fe544210c9f0d14dc0753baea00408575ff81ab.js
508 ms
mapbox-4ecafb38693c79d49c3eb41078a955d2b71c58fbfb97afc0f6b2ed54bb0cef6a.js
536 ms
en-US-55c02fa130616624f80ce0dcd214afa0e2f3aa7368c1074df95c77782a2396ed.js
553 ms
application-6db870d3d6cab736a9dd7b0a99b44d3945e2a1d3ac674233cf5066c32357c449.js
601 ms
manifest-2a89cc3366e87358ac7498b4b4a62274d5c662ed1a41efc7a54c228da8728fad.js
553 ms
ad_status.js
390 ms
Ds_pDKslpu-iWcXddHrDyyVH9ulM38tH3FG5TexbKIk.js
306 ms
embed.js
112 ms
settings
442 ms
KFOmCnqEu92Fr1Mu4mxM.woff
255 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
298 ms
I2KVLFCFVEBLUDNE353RME4SHFV3FKTWHBTJ25B3OH4PQTCMST54BE7W6WSIN6MN2ZZFRW22GMWVAVZGDDIQTFZ3D2AHSIDF
392 ms
K4XZOVHI6DFBFNKMH3I55QFMQEW7FNUF52GPJNNNF7INT6OPRG3GMUU4C5MQIJFZ7RY7ZWJ5IOCZKRVPWQFR3YA5TOM3SAT5
607 ms
ZZXKT7WJ7LK5NO3XMQTLSI6A234CRIKLSODMDNBGAJD4SVVESBSVR2A7I2OKJU2DFNBJADA3DGW4IT4WD44PXCXOWHW5K73G
609 ms
LFVKKL43BKC2Q2BZ3O5TVWQZXIAH4GC7T7AT3XJZO3LNLCN2GSXB6CDXARAWPNIPLTFRWJFLCGL6EZBNCKIQ5IUQS4DWTU5U
477 ms
KSCQDIVH7SFTS3XVWRP5PQO54PWSKOZJE3V2IW6KHFTLSPG3XZFJAYPSQ75E7N3NIMCOV4F2SX5CDO52I4K7MHELFZ4T6UE4
636 ms
Create
142 ms
id
139 ms
button.856debeac157d9669cf51e73a08fbc93.js
29 ms
GenerateIT
14 ms
embeds
43 ms
follow_button.2f70fb173b9000da126c79afe2098f02.en-gb.html
39 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: