11.1 sec in total
561 ms
10.2 sec
297 ms
Visit runen.net now to see the best up-to-date Runen content for Germany and also check out these interesting facts you probably never knew about runen.net
Runen und Ihre Bedeutung - Ihr Horoskop - Horoskope und Voodookult - Befragen Sie das Orakel - Runenkunde und Sternzeichen - Ihr Mondzeichen
Visit runen.netWe analyzed Runen.net page load time and found that the first response time was 561 ms and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
runen.net performance score
name
value
score
weighting
Value4.2 s
19/100
10%
Value5.9 s
14/100
25%
Value6.1 s
45/100
10%
Value980 ms
28/100
30%
Value0.128
82/100
15%
Value8.4 s
39/100
10%
561 ms
203 ms
191 ms
11 ms
134 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 9% of them (8 requests) were addressed to the original Runen.net, 24% (21 requests) were made to Ih.adscale.de and 11% (10 requests) were made to Dmp.theadex.com. The less responsive or slowest element that took the longest time to load (8.8 sec) relates to the external source Ih.adscale.de.
Page size can be reduced by 31.5 kB (30%)
106.1 kB
74.6 kB
In fact, the total size of Runen.net main page is 106.1 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. 40% of websites need less resources to load. Javascripts take 46.0 kB which makes up the majority of the site volume.
Potential reduce by 11.7 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 11.7 kB or 71% of the original size.
Potential reduce by 1.9 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. Runen images are well optimized though.
Potential reduce by 13.0 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 13.0 kB or 28% of the original size.
Potential reduce by 4.9 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. Runen.net needs all CSS files to be minified and compressed as it can save up to 4.9 kB or 77% of the original size.
Number of requests can be reduced by 50 (68%)
74
24
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Runen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
runen.net
561 ms
styles.css
203 ms
cm
191 ms
adsbygoogle.js
11 ms
tracking.js
134 ms
getads.js
5 ms
cookiechoices.js
402 ms
de_cookie_ansage.js
402 ms
51LUni4TpVL._SL110_.jpg
33 ms
155 ms
buy-from-tan.gif
30 ms
ca-pub-4592258043425445.js
82 ms
zrt_lookup.html
80 ms
show_ads_impl.js
91 ms
cm
125 ms
logo_facebook.png
563 ms
leiste.gif
127 ms
bg-high.gif
127 ms
navibg.gif
221 ms
Aquarius.gif
220 ms
bratwurst.png
363 ms
logo_twitter.png
664 ms
logo_google.png
771 ms
analytics.js
45 ms
t.js
118 ms
collect
14 ms
ads
142 ms
31GjLznIkvL._SL110_.jpg
19 ms
80 ms
osd.js
15 ms
ads
196 ms
ads
210 ms
impr
237 ms
m_js_controller.js
26 ms
abg.js
36 ms
favicon
86 ms
googlelogo_color_112x36dp.png
102 ms
nessie_icon_thin_arrow_big_white.png
24 ms
s
57 ms
x_button_blue2.png
46 ms
favicon
122 ms
2199116833792721228
21 ms
MdyApZkAHG2-UELdOwjNjjFZXSz-CGj4o1JtDR7aGgs.js
14 ms
adex.js
258 ms
rtb
97 ms
match
87 ms
728x90.gif
11 ms
loadImages.js
4 ms
t.js
89 ms
t.js
171 ms
0
102 ms
nuggad
8756 ms
analytic.js
87 ms
168 ms
1.gif
172 ms
pixel
23 ms
redirect
271 ms
cm.gif
89 ms
2.gif
87 ms
2.gif
88 ms
179
88 ms
redirect
349 ms
activeview
15 ms
activeview
21 ms
activeview
32 ms
632
90 ms
2.gif
89 ms
924
89 ms
1193
92 ms
pixel
32 ms
gum
188 ms
pixel
20 ms
1839
115 ms
0
88 ms
usersync.aspx
20 ms
0
89 ms
324 ms
2535
90 ms
2940
90 ms
adscaleRedirect
170 ms
3218
89 ms
3477
87 ms
1by1.png
5 ms
3858
87 ms
adscale
7 ms
adscale
9 ms
4302
87 ms
usermatchredir
10 ms
0
87 ms
runen.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
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
Links do not have a discernible name
runen.net 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
runen.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Runen.net can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Runen.net 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.
runen.net
Open Graph description is not detected on the main page of Runen. 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: