4.1 sec in total
727 ms
3 sec
337 ms
Click here to check amazing Aoel content. Otherwise, check out these important facts you probably never knew about aoel.org
Just another WordPress site
Visit aoel.orgWe analyzed Aoel.org page load time and found that the first response time was 727 ms and then it took 3.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. This domain responded with an error, which can significantly jeopardize Aoel.org rating and web reputation
aoel.org performance score
name
value
score
weighting
Value14.0 s
0/100
10%
Value50.6 s
0/100
25%
Value31.4 s
0/100
10%
Value3,690 ms
1/100
30%
Value0.067
97/100
15%
Value33.6 s
0/100
10%
727 ms
191 ms
282 ms
189 ms
839 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that all of those requests were addressed to Aoel.org and no external sources were called. The less responsive or slowest element that took the longest time to load (839 ms) belongs to the original domain Aoel.org.
Page size can be reduced by 670.6 kB (52%)
1.3 MB
628.2 kB
In fact, the total size of Aoel.org main page is 1.3 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. 40% of websites need less resources to load. Javascripts take 660.3 kB which makes up the majority of the site volume.
Potential reduce by 69.2 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. This page needs HTML code to be minified as it can gain 19.5 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 69.2 kB or 86% of the original size.
Potential reduce by 52.1 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. Aoel images are well optimized though.
Potential reduce by 505.5 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 505.5 kB or 77% of the original size.
Potential reduce by 43.8 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. Aoel.org needs all CSS files to be minified and compressed as it can save up to 43.8 kB or 82% of the original size.
Number of requests can be reduced by 3 (5%)
58
55
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aoel. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
www.aoel.org
727 ms
stylesheet_139c8ef17c.css
191 ms
jquery-ui-1.10.4.custom.min.css
282 ms
style.css
189 ms
jquery-1.10.2.js
839 ms
jquery-ui-1.10.4.custom.min.js
801 ms
jquery.scroller.js
559 ms
javascript_a708894199.js
287 ms
styleSafari.css
301 ms
header.jpg
210 ms
logo.jpg
100 ms
search.gif
106 ms
clear.gif
99 ms
neu.png
103 ms
submenu.png
101 ms
Das_Podium.JPG
284 ms
Kuh.JPG
292 ms
fertige_brote4.jpg
199 ms
Beck_und_Rammler_web.jpg
207 ms
Aoel1.jpg
210 ms
Symbol1.JPG
233 ms
Noichl.jpg
297 ms
Logo_KMU_gegen_TTIP_web_01.png
314 ms
BKT.jpg
313 ms
4445926b1c.jpg
336 ms
neu-2.png
378 ms
Ruschin.JPG
386 ms
Naturata3.jpg
397 ms
Lebensbaum3.jpg
414 ms
MK3.jpg
421 ms
0cb3474160.jpg
437 ms
0bc66f6b15.jpg
480 ms
be5d3bfb0d.jpg
480 ms
03c02672b6.jpg
498 ms
eeb8103428.jpg
520 ms
57311cae50.jpg
525 ms
8e75b30ec5.jpg
539 ms
46b0cdb027.jpg
578 ms
d425a22510.jpg
583 ms
6184cba571.jpg
592 ms
sommer_02.jpg
629 ms
dc6432f517.jpg
630 ms
glaeserne-moo__kerei.jpg
648 ms
94a8a1bca1.jpg
671 ms
sommer.jpg
683 ms
PT_Sans.woff
591 ms
PT_Sans_Bold.woff
634 ms
icons.woff
640 ms
PT_Sans_Narrow_Bold.woff
654 ms
b1343c7d90.jpg
669 ms
53caef09d2.jpg
657 ms
eada7266e8.jpg
584 ms
64c4d68628.jpg
630 ms
6d6880b2e1.jpg
635 ms
910d16bb60.jpg
623 ms
Platzhalter-quer100.png
584 ms
natfood.jpg
593 ms
c4a7c63ec3.jpg
581 ms
d4ce7af2f5.jpg
627 ms
72e78e962e.jpg
633 ms
1845ce3e89.jpg
630 ms
aoel.org 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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
aoel.org 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
aoel.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aoel.org can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Aoel.org 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.
aoel.org
Open Graph description is not detected on the main page of Aoel. 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: