5.3 sec in total
826 ms
4.3 sec
206 ms
Click here to check amazing AIZ content. Otherwise, check out these important facts you probably never knew about aiz.info
Visit aiz.infoWe analyzed Aiz.info page load time and found that the first response time was 826 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
aiz.info performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value4.9 s
29/100
25%
Value7.8 s
23/100
10%
Value90 ms
98/100
30%
Value0
100/100
15%
Value9.4 s
30/100
10%
826 ms
104 ms
207 ms
319 ms
308 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 91% of them (79 requests) were addressed to the original Aiz.info, 8% (7 requests) were made to Cdn.lko.at and 1% (1 request) were made to Stat1.netletter.at. The less responsive or slowest element that took the longest time to load (1.6 sec) relates to the external source Cdn.lko.at.
Page size can be reduced by 238.5 kB (32%)
742.3 kB
503.8 kB
In fact, the total size of Aiz.info main page is 742.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. 50% of websites need less resources to load. Images take 452.4 kB which makes up the majority of the site volume.
Potential reduce by 23.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 23.8 kB or 76% of the original size.
Potential reduce by 7.6 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. AIZ images are well optimized though.
Potential reduce by 207.2 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. Aiz.info needs all CSS files to be minified and compressed as it can save up to 207.2 kB or 80% of the original size.
Number of requests can be reduced by 67 (79%)
85
18
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AIZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
aiz.info
826 ms
minimalist.css
104 ms
jquery-ui.css
207 ms
bootstrap.css
319 ms
responsive.css
308 ms
chosen.css
311 ms
portal-styles.css
305 ms
jquery.selectBoxIt.css
315 ms
jquery.js
413 ms
jquery.easing.js
407 ms
jquery.browser.js
406 ms
jquery.form.js
408 ms
jbox.js
513 ms
jbox.ready.js
407 ms
modernizr.js
508 ms
digitalworkroom.js
507 ms
base64.js
509 ms
chosen.js
510 ms
select_chosen.js
512 ms
jquery-ui.js
828 ms
2510.js
610 ms
diagram.js
617 ms
jquery.selectBoxIt.js
717 ms
jquery.ui.touch-punch.min.js
612 ms
bootstrap-affix.js
614 ms
bootstrap-carousel.js
708 ms
bootstrap-collapse.js
714 ms
bootstrap-dropdown.js
715 ms
bootstrap-transition.js
714 ms
bootstrap-typeahead.js
810 ms
bootstrap-tab.js
815 ms
bootstrap-modal.js
815 ms
custom-bootstrap-carousel.js
816 ms
main.js
815 ms
jbox-draggable.js
909 ms
custom_dwandweb.js
917 ms
custom_web.js
918 ms
jquery.customclone.js
818 ms
imgTransformer.js
718 ms
body.css
624 ms
headings.css
711 ms
links.css
712 ms
forms.css
705 ms
lists.css
704 ms
buttons.css
625 ms
header.css
627 ms
footer.css
713 ms
boxes.css
722 ms
navigation.css
722 ms
breadcrumb.css
626 ms
utilities.css
620 ms
mediabox.css
625 ms
tables.css
709 ms
pagination.css
718 ms
site-styles.css
719 ms
print.css
622 ms
customer.css
618 ms
portal_jbox.css
618 ms
gallery.css
703 ms
modalbox_styling.css
619 ms
modalbx-ie7.css
616 ms
modalbox.css
616 ms
pdf_print.js
666 ms
jquery.touchSwipe.js
667 ms
jquery.placeholder.js
608 ms
web.js
613 ms
flowplayer.min.js
739 ms
flowplayer.config.js
612 ms
jquery.mousewheel.min.js
612 ms
jquery.imagereader-min.js
613 ms
bg-background.gif
140 ms
stat-data.js
146 ms
144431373119830.gif
1609 ms
1431077093683834.gif
1192 ms
1380736166152868.jpg
558 ms
1418128453294710.jpg
831 ms
1437476293511130.jpg
1203 ms
1382181504184562.jpg
601 ms
1456494859156136.jpg
648 ms
logo.png
105 ms
printlogo.gif
104 ms
wirsindfuenfzig.png
105 ms
wetterkreuz.gif
104 ms
ad.png
104 ms
marker-small.png
106 ms
down.gif
225 ms
counter_.php
844 ms
aiz.info accessibility score
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
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.
aiz.info 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
aiz.info 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
N/A
ISO-8859-15
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aiz.info 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 Aiz.info main page’s claimed encoding is iso-8859-15. 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.
aiz.info
Open Graph description is not detected on the main page of AIZ. 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: