21.5 sec in total
317 ms
21.1 sec
106 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 317 ms and then it took 21.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
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.123
84/100
15%
Value0
0/100
10%
317 ms
509 ms
99 ms
198 ms
286 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 58% of them (40 requests) were addressed to the original Rilke.de, 25% (17 requests) were made to Static.xx.fbcdn.net and 4% (3 requests) were made to External-iad3-2.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (20 sec) relates to the external source Assoc-amazon.de.
Page size can be reduced by 3.7 kB (5%)
81.3 kB
77.6 kB
In fact, the total size of Rilke.de main page is 81.3 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. 55% of websites need less resources to load. Images take 71.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 762 B
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 140 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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 22 (35%)
63
41
The browser has sent 63 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 as a result speed up the page load time.
rilke.de
317 ms
www.rilke.de
509 ms
logo_top_left.htm
99 ms
left_menu.htm
198 ms
left_middle.htm
286 ms
left_bottom.htm
290 ms
middle_top.htm
289 ms
right_top.htm
290 ms
main.htm
299 ms
middle_bottom.htm
294 ms
right_bottom.shtml
379 ms
logo_top_left.gif
288 ms
home_ph.gif
289 ms
left_menu.gif
191 ms
biografie_off.gif
197 ms
biografie_on.gif
197 ms
roman_off.gif
282 ms
roman_on.gif
284 ms
gedichte_off.gif
287 ms
gedichte_on.gif
287 ms
erzaehlungen_off.gif
293 ms
erzaehlungen_on.gif
293 ms
kunst_off.gif
378 ms
kunst_on.gif
380 ms
briefe_off.gif
383 ms
briefe_on.gif
383 ms
forum_off.gif
389 ms
forum_on.gif
389 ms
left_middle.gif
382 ms
left_bottom.gif
383 ms
links_off.gif
387 ms
middle_top.gif
386 ms
amazonklein.gif
392 ms
right_top.gif
392 ms
middle_bottom.gif
483 ms
impressum_off.gif
484 ms
impressum_on.gif
486 ms
partner.gif
486 ms
brand
21 ms
link-enhancer
19970 ms
rilke_main_pic.jpg
606 ms
brandjs.js
18 ms
likebox.php
432 ms
cm
12 ms
branding.png
21 ms
right_bottom.gif
413 ms
8zUKAIFBjy-.css
32 ms
lFC1eVji7gN.css
41 ms
p1qWOgvDEaf.css
47 ms
css;%20charset=utf-8;base64,LmxfYzNweW8ydjB1e21hcmdpbi1ib3R0b206NnB4fS5hX2MzcHlvNG9uMnttYXJnaW4tcmlnaHQ6OHB4fS5yX2MzcHlvMmV5MSAuaF9jM3B5bzRveTV7YWxpZ24taXRlbXM6Y2VudGVyO2Rpc3BsYXk6ZmxleH0ueV9jM3B5bzJ0YTN7bWFyZ2luLWJvdHRvbTotNnB4fS51X2MzcHlvMnRhNHtwYWRkaW5nLWJvdHRvbTo2cHh9Ll81djNxIC5sX2MzcHlvMnYwdXttYXJnaW4tYm90dG9tOjExcHh9Ll81djNxIC5sX2MzcHlvMnYwdS5pX2MzcHlueWkyZnttYXJnaW4tYm90dG9tOi0xcHh9Ll81djNxIC5sX2MzcHlvMnYwdS5pX2MzcHlueWkyZiAub19jM3B5bnlpMmd7cGFkZGluZy1ib3R0b206M3B4fS5fNXYzcSAuXzVwYS0gLmxfYzNweW8ydjB1e21hcmdpbi1ib3R0b206N3B4fS5yX2MzcHlvMmV5MXtib3JkZXItYm90dG9tOjFweCBzb2xpZCAjZTllOWU5O2NvbG9yOiM3ZjdmN2Y7ZGlzcGxheTpibG9jaztmb250LXNpemU6MTNweDttYXJnaW46LTE4cHggMCAxNHB4O3BhZGRpbmc6MTNweCAwIDEzcHh9Ll81djNxIC5fOTBvZCAucl9jM3B5bzJleTF7Ym9yZGVyLWJvdHRvbTpub25lO3BhZGRpbmctYm90dG9tOjA7cGFkZGluZy10b3A6MTJweH0uXzV2M3EgLl85MG9jIC5fMXMzMSAucl9jM3B5bzJleTEsLl81djNxIC5fOTBvYyAuXzFzMzEgLnJfYzNweW8yZXkxIGF7Y29sb3I6IzYwNjc3MH0uXzV2M3EgLl85MG9jIC5fMXMzMSAucl9jM3B5bzJleTEgLnByb2ZpbGVMaW5re2ZvbnQtd2VpZ2h0OjUwMH0uXzV2M3EgLnJfYzNweW8yZXkxe2JvcmRlci1ib3R0b20tY29sb3I6I2U1ZTVlNTtjb2xvcjojOTA5NDljO2xpbmUtaGVpZ2h0OjE1cHg7bWFyZ2luOi0xMnB4IDAgMTJweDtwYWRkaW5nOjEwcHggMjNweCAxMHB4IDB9Ll81djNxIC5yX2MzcHlvMmV5MS54X2MzcHluenFfNCwuXzFzMzEueF9jM3B5bnpxXzQgLnJfYzNweW8yZXkxe2NvbG9yOiM2MTY3NzB9Ll81djNxIC5yX2MzcHlvMmV5MS52X2MzcHluenFfNiwuXzFzMzEudl9jM3B5bnpxXzYgLnJfYzNweW8yZXkxe2ZvbnQtc2l6ZToxM3B4fS5fM2NjYiAucl9jM3B5bzJleTF7Zm9udC1zaXplOjEycHg7cGFkZGluZy1ib3R0b206OXB4O3BhZGRpbmctdG9wOjExcHh9Ll82cTFhIC5pX2MzcHlvNHJkcC5yX2MzcHlvMmV5MXthbGlnbi1pdGVtczpjZW50ZXI7ZGlzcGxheTpmbGV4fS5fNnExYSAuaV9jM3B5bzRyZHAgLndfYzNweW80cmU3e2ZvbnQtc2l6ZToxNHB4O2xpbmUtaGVpZ2h0OjE2cHh9Ll82cTFhIC5pX2MzcHlvNHJkcCAud19jM3B5bzRyZTcgLnByb2ZpbGVMaW5re2ZvbnQtd2VpZ2h0OmJvbGR9Ll82cTFhIC5pX2MzcHlvNHJkcCAuZV9jM3B5bzRyZTh7YWxpZ24taXRlbXM6Y2VudGVyO2JhY2tncm91bmQtY29sb3I6IzQyYjcyYTtib3JkZXItcmFkaXVzOjUwJTtib3gtc2hhZG93OjAgMnB4IDRweCAwIHJnYmEoMCwgMCwgMCwgLjEpO2Rpc3BsYXk6aW5saW5lLWZsZXg7ZmxleC1zaHJpbms6MDtoZWlnaHQ6MjRweDtqdXN0aWZ5LWNvbnRlbnQ6Y2VudGVyO21hcmdpbi1yaWdodDo4cHg7d2lkdGg6MjRweH0jYm9vdGxvYWRlcl9Udm9BQWIze2hlaWdodDo0MnB4O30uYm9vdGxvYWRlcl9Udm9BQWIze2Rpc3BsYXk6YmxvY2shaW1wb3J0YW50O30=
11 ms
VWDhCULazb5.js
53 ms
mP12tTiNgO_.js
48 ms
o1ndYS2og_B.js
44 ms
owo2sPJxB2z.js
34 ms
p55HfXW__mM.js
78 ms
E6qR0C8WEpl.js
51 ms
5xOV5e9oy4e.js
48 ms
D94KH2dXN-z.js
48 ms
M1MQmWsK7ID.js
50 ms
g2XPN2wRGmV.js
76 ms
DPxpTcknHiI.js
90 ms
327195671_1366845080758733_6237906056028195770_n.jpg
59 ms
327159504_1812155625827008_4790786489618409213_n.jpg
70 ms
9018335611290252052
61 ms
ie38mp0O07P.js
35 ms
UXtr_j2Fwe-.png
32 ms
mUnDZSrH5OM.png
32 ms
15878582167042254373
41 ms
8717398713787287726
39 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: