3.6 sec in total
560 ms
2.8 sec
186 ms
Visit rotenasen.at now to see the best up-to-date ROTE NASEN content and also check out these interesting facts you probably never knew about rotenasen.at
Seit 1994 schenken ROTE NASEN Clowndoctors kleinen und großen Patient*innen Lachen und Lebensfreude.
Visit rotenasen.atWe analyzed Rotenasen.at page load time and found that the first response time was 560 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
rotenasen.at performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value5.9 s
14/100
25%
Value7.0 s
32/100
10%
Value210 ms
89/100
30%
Value0.005
100/100
15%
Value6.6 s
57/100
10%
560 ms
100 ms
193 ms
293 ms
195 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 53% of them (36 requests) were addressed to the original Rotenasen.at, 15% (10 requests) were made to Static.xx.fbcdn.net and 7% (5 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (931 ms) belongs to the original domain Rotenasen.at.
Page size can be reduced by 600.7 kB (43%)
1.4 MB
799.6 kB
In fact, the total size of Rotenasen.at main page is 1.4 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. 55% of websites need less resources to load. Javascripts take 700.5 kB which makes up the majority of the site volume.
Potential reduce by 115.0 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.0 kB or 76% of the original size.
Potential reduce by 22.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. ROTE NASEN images are well optimized though.
Potential reduce by 463.3 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 463.3 kB or 66% of the original size.
Number of requests can be reduced by 32 (50%)
64
32
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ROTE NASEN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.rotenasen.at
560 ms
stylesheet_4cc55212ae.css
100 ms
spendenseite.css
193 ms
jquery-1.4.2.min.js
293 ms
jquery.biggerlink.js
195 ms
master.js
367 ms
swfobject.js
822 ms
iban.js
198 ms
spendenseite.js
288 ms
style.css
290 ms
skripte.js
301 ms
addthis_widget.js
46 ms
ga.js
9 ms
hgBody.png
222 ms
hgSpalten.gif
102 ms
e468178bfa.png
296 ms
f4ad71975e.png
298 ms
e11de8b533.png
238 ms
7b10396584.png
237 ms
blank.gif
237 ms
csm_Logo_Creative_Europe_left__2__03_e62eb223f6.jpg
237 ms
csm_EU-Entwicklung_DT_138b1e382a.jpg
355 ms
csm_QIF_Logo_Kopie_d5431fc3bc.jpg
354 ms
Seniorenkampagne.jpg
520 ms
clownchild_de.png
522 ms
logoRoteNasen_mit_Zusatz.jpg
486 ms
logoRNI.png
398 ms
spendenstempel_rna.png
425 ms
spendenguetesiegel.png
427 ms
gtm.js
52 ms
all.js
48 ms
__utm.gif
50 ms
pfeilWeiter.png
446 ms
hgTrennlinie.gif
473 ms
pfeiloben.png
477 ms
spendenpfeil.png
535 ms
pfeilunten.png
545 ms
flashPromoBox.jpg
566 ms
menuAufzaehlung.gif
529 ms
menuClown.jpg
530 ms
hgFooter.png
931 ms
collect
140 ms
analytics.js
64 ms
300lo.json
83 ms
218 ms
sh.8e5f85691f9aaa082472a194.html
48 ms
xd_arbiter.php
50 ms
xd_arbiter.php
62 ms
collect
38 ms
collect
47 ms
layers.e5ea973510bf60b3db41.js
20 ms
de.js
18 ms
like_box.php
235 ms
kyEKgjk51ZE.css
28 ms
xgj7bXhJNEH.css
37 ms
q68gy-v_YMF.js
43 ms
FJmpeSpHpjS.js
68 ms
0wM5s1Khldu.js
68 ms
1bNoFZUdlYZ.js
65 ms
11147854_10153379849733846_8512328170838051608_n.jpg
58 ms
12803114_10154068696078846_5777784608551745825_n.jpg
13 ms
10983353_890334227676162_2525329935220436658_n.jpg
16 ms
12239999_951441691596819_6615433868004560408_n.jpg
15 ms
12821349_109475566115016_3365940627405211848_n.jpg
14 ms
wL6VQj7Ab77.png
11 ms
s7jcwEQH7Sx.png
10 ms
I6-MnjEovm5.js
8 ms
pQrUxxo5oQp.js
2 ms
rotenasen.at 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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Buttons do not have an accessible name
Form elements do not have associated labels
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
rotenasen.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
rotenasen.at 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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rotenasen.at 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 Rotenasen.at 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.
rotenasen.at
Open Graph description is not detected on the main page of ROTE NASEN. 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: