3 sec in total
17 ms
2.6 sec
461 ms
Welcome to aol.de homepage info - get ready to check Aol best content for Germany right away, or after learning these important things about aol.de
AOL.der
Visit aol.deWe analyzed Aol.de page load time and found that the first response time was 17 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.
aol.de performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value8.5 s
2/100
25%
Value6.8 s
34/100
10%
Value3,070 ms
2/100
30%
Value0.021
100/100
15%
Value17.0 s
4/100
10%
17 ms
185 ms
10 ms
402 ms
31 ms
Our browser made a total of 161 requests to load all elements on the main page. We found that 3% of them (5 requests) were addressed to the original Aol.de, 27% (43 requests) were made to O.aolcdn.com and 5% (8 requests) were made to Washingtonpost.com. The less responsive or slowest element that took the longest time to load (501 ms) relates to the external source Dtm.advertising.com.
Page size can be reduced by 2.3 MB (52%)
4.4 MB
2.1 MB
In fact, the total size of Aol.de main page is 4.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 153.3 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 153.3 kB or 80% of the original size.
Potential reduce by 128.3 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. Aol images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 66% of the original size.
Potential reduce by 920.3 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. Aol.de needs all CSS files to be minified and compressed as it can save up to 920.3 kB or 82% of the original size.
Number of requests can be reduced by 91 (65%)
141
50
The browser has sent 141 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Aol. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
aol.de
17 ms
www.aol.de
185 ms
egc1xbp.js
10 ms
iam.js
402 ms
main_1024.css
31 ms
raindrop.css
24 ms
16 ms
adsWrapperIntl.js
14 ms
omniunih_int.js
14 ms
responsive-main.js
16 ms
outbrain.js
21 ms
egc1xbp-k.css
10 ms
loader.js
78 ms
cobrand.js
19 ms
load_v7_intl.html
53 ms
bc4f3d4e-1020-4447-a6c8-83a085b2127a.png
26 ms
a-MADONNA-233x155.jpg
28 ms
a-YACHT-SMALL-233x155.jpg
28 ms
a-HOENESS-233x155.jpg
31 ms
a-IRON-MAIDEN-233x155.jpg
31 ms
a-NORWEGENKREUZFAHRT-233x155.jpg
31 ms
s-50-SHADES-OF-GREY-small.jpg
31 ms
98cf3292-c32b-498c-a991-be7252de02d3.png
26 ms
Screen+Shot+2016-02-28+at+18.54.48.png
25 ms
65e45794-9279-459c-b7e5-d9183e3db8ba.png
24 ms
ddd04202-214c-4310-9941-a20196378053.png
25 ms
sprite.png
32 ms
2.25488181.jpg
26 ms
ZOOMIN_standard.png
26 ms
x.gif
29 ms
x.gif
29 ms
9d9c7d5a-eb5d-47f7-a837-b68b1b76425c.jpeg
29 ms
13207a0a-bd57-466d-bd1c-ef0502b09458.jpeg
29 ms
c0d7d053-e9cb-4fb7-b551-cbfded32d40c.jpg
30 ms
bbb1ed52-ce73-4a2c-bf53-3f736d4f58e5.png
30 ms
kw1xNLLWQe_KWVnMaxVzXJXuDABPF_-UzDKE9qq2cAGffV1mggMdeMJ6Mk6g5Mw.woff
8 ms
oy82gGnA0hxsVUteTAIXfGhQ32hfN9WEsOj2SUMiecCffHhpEN32IgCjMKM2HMItgM.woff
8 ms
WFPYEk0Ln1FNe-VpmK5wnUeELG7o80Pz4lLG_MLq-H9ffVamggMdeMJ6Mk6g5Mj.woff
8 ms
dXbq0_sc-e1aPptFbyGo3xi-OLZfKcAWwCXSv-a2ejCffOfpEN32IgCjMKM2HMItg3.woff
8 ms
load.js
49 ms
impl.198-RELEASE.js
57 ms
beacon.js
10 ms
guid.html
10 ms
eutcode.html
14 ms
beacon.min.js
8 ms
9cb82d9c-a354-47e3-9e26-ed7ed16e9158.jpg
34 ms
slf.js
21 ms
916f392e-1af6-43dd-bc12-239421d8b718.js
422 ms
rd
19 ms
load_v7_intl.html
18 ms
67 ms
slf.js
7 ms
2DE4E0_4_0.woff
57 ms
id
56 ms
r.js
55 ms
p.gif
132 ms
8c18b227-f615-4d9c-be2f-265718bea824.png
29 ms
29 ms
s34693147202488
11 ms
11 ms
load_v7_intl.html
6 ms
a
59 ms
yi
37 ms
a
35 ms
yi
110 ms
uk-video-play-button.png
107 ms
loading.gif
98 ms
mc.s2c.min.js
67 ms
moth-min.js
52 ms
519538388_c.jpg
23 ms
519538379_c.jpg
8 ms
2.25527686.jpg
10 ms
SPLASH_standard.png
10 ms
2.23927287.jpg
10 ms
2.25570795.jpg
10 ms
2.24737168.jpg
9 ms
2.22215319.jpg
10 ms
mc.s2c.css
18 ms
initialize
78 ms
916f392e-1af6-43dd-bc12-239421d8b718
501 ms
9e865b16-bf55-4ffb-9f2a-70dadfc986c7.js
3 ms
log
75 ms
allowedSizes=728x90,948x250,970x66,970x90,950x252,970x250,940x230,101x1;uuid=56D424CA6E65164303A71399FC2C9B09;cfp=1;rndc=1456745212;noperf=1;alias=100038996;artexc=art_flash,art_rrflash;kvpg=aol.de;kvh5lsid=0;kvmn=100038996;kvgrp=745212511;kvismob=2;kvoch=de.aolportal;extmirroring=0;kvtile=1;target=_blank;aduho=180;grp=745212511
185 ms
noperf=1;uuid=56D424CA6E65164303A71399F19A45C3;cfp=1;rndc=1456745212;alias=100039000;noaddonpl=y;artexc=art_flash,art_rrflash;kvpg=aol.de;kvh5lsid=0;kvmn=100039000;kvgrp=745212511;kvismob=2;kvoch=de.aolportal;extmirroring=0;kvtile=2;target=_blank;aduho=180;grp=745212511
181 ms
adsWrapper3.js
3 ms
size=728x90;alias=100050065;noperf=1;noaddonpl=y;ifv=1;kvorigmn=100038996;kvugc=0;kvpg=aol.de;kvmn=100050065;kv3puac=1;kvgrp=745212511;kvismob=2;extmirroring=0;kvtile=1;aduho=180;artexc=art_flash,art_rrflash;grp=745212511
105 ms
pcreative
181 ms
35 ms
generic
13 ms
sync
23 ms
pixel
31 ms
generic
16 ms
mapuser
178 ms
providerid=1037;userid=124a4273-7e32-425d-a119-8c613801f90e
178 ms
ATCollapse.gif
7 ms
pixel
20 ms
mapuser
177 ms
mapuser
3 ms
in
26 ms
mapuser
181 ms
mapuser
180 ms
mapuser
383 ms
mapuser
116 ms
js
242 ms
gpt.js
5 ms
js
38 ms
pixel
15 ms
pubads_impl_81.js
10 ms
ads
67 ms
container.html
18 ms
pixel.gif
16 ms
300x600.html
94 ms
blank.gif
87 ms
usermatch
42 ms
pixel.htm
82 ms
osd.js
22 ms
img
22 ms
moatad.js
37 ms
usermatch
38 ms
casale
10 ms
pixel
38 ms
gr
15 ms
mapuser
105 ms
casaleopenrtb
9 ms
300x600_hype_generated_script.js
12 ms
ddc.htm
31 ms
crum
36 ms
crum
34 ms
rum
34 ms
rum
31 ms
HYPE-518.thin.min.js
25 ms
rum
25 ms
Pug
71 ms
rtset
80 ms
u.php
87 ms
104 ms
mapuser
31 ms
pixel
30 ms
rum
30 ms
iframe
68 ms
bd
67 ms
underline-1.png
16 ms
stores-1.jpg
56 ms
ribbon-1.png
47 ms
cta-1.png
73 ms
80-years.jpg
73 ms
crum
34 ms
merge
30 ms
pixel.gif
62 ms
tap.php
32 ms
xrefid.xgi
32 ms
m
107 ms
crum
76 ms
sync
81 ms
bd
73 ms
img
68 ms
img
77 ms
NAX6354298003721285923
39 ms
lr.gif
5 ms
sd
72 ms
crum
8 ms
aol.de 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 IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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>).
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Some elements have a [tabindex] value greater than 0
aol.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
aol.de 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
Tap targets are not sized appropriately
DE
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aol.de 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 Aol.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.
aol.de
Open Graph data is detected on the main page of Aol. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: