2.3 sec in total
353 ms
1.8 sec
149 ms
Click here to check amazing Rilke content for Germany. Otherwise, check out these important facts you probably never knew about rilke.de
Rilke: tausende Gedichte im Volltext, Prosatexte, Briefe, eine Biographie und ein Forum mit hunderten Beiträgen.
Visit rilke.deWe analyzed Rilke.de page load time and found that the first response time was 353 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
rilke.de performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.11
87/100
15%
Value0
0/100
10%
353 ms
97 ms
196 ms
196 ms
198 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 42% of them (39 requests) were addressed to the original Rilke.de, 22% (20 requests) were made to Static.xx.fbcdn.net and 16% (15 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (540 ms) belongs to the original domain Rilke.de.
Page size can be reduced by 7.4 kB (7%)
102.5 kB
95.1 kB
In fact, the total size of Rilke.de main page is 102.5 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. 45% of websites need less resources to load. Images take 98.3 kB which makes up the majority of the site volume.
Potential reduce by 2.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. 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 2.8 kB or 67% of the original size.
Potential reduce by 4.6 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. Rilke images are well optimized though.
Potential reduce by 0 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.
Number of requests can be reduced by 27 (30%)
91
64
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rilke. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
rilke.de
353 ms
logo_top_left.htm
97 ms
left_menu.htm
196 ms
left_middle.htm
196 ms
left_bottom.htm
198 ms
middle_top.htm
198 ms
right_top.htm
199 ms
main.htm
209 ms
middle_bottom.htm
280 ms
right_bottom.shtml
280 ms
logo_top_left.gif
200 ms
home_ph.gif
201 ms
left_menu.gif
105 ms
biografie_off.gif
105 ms
biografie_on.gif
187 ms
roman_off.gif
188 ms
roman_on.gif
197 ms
gedichte_off.gif
200 ms
gedichte_on.gif
198 ms
erzaehlungen_off.gif
198 ms
erzaehlungen_on.gif
279 ms
kunst_off.gif
280 ms
kunst_on.gif
291 ms
briefe_off.gif
290 ms
briefe_on.gif
293 ms
forum_off.gif
293 ms
forum_on.gif
372 ms
left_middle.gif
371 ms
left_bottom.gif
380 ms
links_off.gif
379 ms
middle_top.gif
383 ms
amazonklein.gif
384 ms
right_top.gif
458 ms
brand
24 ms
rilke_main_pic.jpg
540 ms
brand
41 ms
cm
473 ms
google_custom_search_watermark.gif
34 ms
middle_bottom.gif
386 ms
impressum_off.gif
386 ms
impressum_on.gif
392 ms
partner.gif
393 ms
right_bottom.gif
466 ms
link-enhancer-common.js
158 ms
likebox.php
461 ms
schwarz466x28.gif
8 ms
156 ms
51iK4ateHHL._SL60_.jpg
15 ms
61QejmPAQhL._SL60_.jpg
15 ms
41FJMcxmOBL._SL60_.jpg
9 ms
51JvoPCc8GL._SL60_.jpg
10 ms
51MdGVu+vLL._SL60_.jpg
15 ms
51Fj-a7IXBL._SL60_.jpg
10 ms
41AH3LxGOcL._SL60_.jpg
20 ms
4171n+oMDnL._SL60_.jpg
17 ms
51DAuSYKxzL._SL60_.jpg
17 ms
E3TzvQNU166.css
84 ms
Q-OWgaJvbhn.css
105 ms
mJ3scex-8ho.css
127 ms
wYbR6_M9nOB.css
156 ms
EQVvsAj4CHs.css
166 ms
q68gy-v_YMF.js
164 ms
FJmpeSpHpjS.js
194 ms
0wM5s1Khldu.js
139 ms
1bNoFZUdlYZ.js
143 ms
njO1TPvGzoR.js
192 ms
1QuX41zDRrx.js
192 ms
Oagsvfb4VWi.js
214 ms
LTv6ZK-5zxz.js
225 ms
1FCa-btixu2.js
219 ms
543566_372248892807571_1310360329_n.jpg
170 ms
safe_image.php
161 ms
safe_image.php
188 ms
154743_406629652702828_1672786003_n.jpg
155 ms
11902236_108199156198615_1400832784964348599_n.jpg
170 ms
12742701_229237904086646_8348932552311175649_n.jpg
173 ms
401392_290121244383685_1928689834_n.jpg
172 ms
1234734_613680838684479_742800865_n.jpg
180 ms
12249864_1647370975502747_3996443918134421112_n.jpg
173 ms
12631503_766758196789856_683207148271680056_n.jpg
174 ms
11167668_888221431236134_7012319902802704488_n.jpg
187 ms
934065_939460906133605_3258633433499910130_n.jpg
336 ms
11892276_391891957678203_3603167887743965620_n.jpg
190 ms
1924114_1058824794148440_796962609475178503_n.jpg
197 ms
12118821_10207842268116051_1307401095602337590_n.jpg
190 ms
12800142_10206140781861838_5971334760059239351_n.jpg
197 ms
1660234_10202429546453693_1646346068_n.jpg
204 ms
wL6VQj7Ab77.png
96 ms
s7jcwEQH7Sx.png
95 ms
QDwYpIaRyfG.png
95 ms
K00K-UgnsKu.png
95 ms
I6-MnjEovm5.js
19 ms
pQrUxxo5oQp.js
36 ms
rilke.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
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
rilke.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
rilke.de SEO score
DE
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rilke.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Rilke.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
rilke.de
Open Graph description is not detected on the main page of Rilke. 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: