4.3 sec in total
391 ms
3.7 sec
231 ms
Click here to check amazing AMS content for Austria. Otherwise, check out these important facts you probably never knew about ams.at
Dies ist eine Kurzanleitung, wie Sie in Ihrem Browser Java Script aktivieren können.
Visit ams.atWe analyzed Ams.at page load time and found that the first response time was 391 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
ams.at performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.7 s
7/100
25%
Value10.9 s
6/100
10%
Value510 ms
57/100
30%
Value0.037
100/100
15%
Value10.1 s
26/100
10%
391 ms
738 ms
572 ms
230 ms
229 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 93% of them (80 requests) were addressed to the original Ams.at, 2% (2 requests) were made to Widget.surveymonkey.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (993 ms) belongs to the original domain Ams.at.
Page size can be reduced by 253.3 kB (42%)
607.0 kB
353.7 kB
In fact, the total size of Ams.at main page is 607.0 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. 30% of websites need less resources to load. Images take 330.3 kB which makes up the majority of the site volume.
Potential reduce by 27.6 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 27.6 kB or 74% of the original size.
Potential reduce by 56.2 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. Obviously, AMS needs image optimization as it can save up to 56.2 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 112.8 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 112.8 kB or 66% of the original size.
Potential reduce by 56.6 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. Ams.at needs all CSS files to be minified and compressed as it can save up to 56.6 kB or 83% of the original size.
Number of requests can be reduced by 39 (46%)
84
45
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of AMS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
ams.at
391 ms
www.ams.at
738 ms
style_master.css
572 ms
page_panel.css
230 ms
jquery.selectbox.css
229 ms
fancybox.css
356 ms
jquery.js
704 ms
jquery_selectbox.js
465 ms
fancybox.js
577 ms
script.js
448 ms
background_top.jpg
245 ms
Logo_AMS_Oesterreich.png
245 ms
map_homepage.gif
144 ms
navi_bg.png
142 ms
input_suche.jpg
249 ms
suche_button.jpg
141 ms
search_button_bg.jpg
265 ms
start_lock.gif
264 ms
start_pencil.gif
265 ms
start_community.gif
367 ms
start_lupe.gif
368 ms
beste3_news1.jpg
607 ms
dummy_aktuelles.png
383 ms
ams_az_button_200x120.jpg
497 ms
banner-einstellungssache50plus-752x120px.jpg
624 ms
esf.jpg
536 ms
eures.jpg
648 ms
footer_img.jpg
539 ms
gtm.js
70 ms
top_navi_border.jpg
614 ms
link_arrow.gif
651 ms
mainnavi_active_left.png
633 ms
mainnavi_active_right.png
704 ms
main_li_border.jpg
711 ms
main_li.jpg
719 ms
searchPanelHomepage_tr.jpg
975 ms
searchPanelHomepage_tl.jpg
751 ms
searchPanelHomepage_br.jpg
753 ms
searchPanelHomepage_bl.jpg
824 ms
job-room.png
827 ms
search_active_left.png
837 ms
search_active_right.png
872 ms
search_right.png
873 ms
rightLinkArrow.png
945 ms
shadow.png
951 ms
searchfield_bg_tr.jpg
958 ms
searchfield_bg_br.jpg
993 ms
iP0CVazKJzXdIDZpR2Nu2g4cR2OURJv4f_2BWKcYW9olBgnYsNVd1Lfy9Nrx07Nmoy.js
36 ms
analytics.js
20 ms
jquery.js
102 ms
cookie.js
64 ms
collect
30 ms
882 ms
searchfield_bg_bl.jpg
957 ms
searchfield.png
954 ms
start_personal_line_vert.gif
862 ms
start_personal_line.gif
876 ms
li.png
886 ms
navi_header_big.jpg
871 ms
navi_border.jpg
946 ms
home.gif
947 ms
eservice.gif
854 ms
login.gif
868 ms
daten.gif
869 ms
gebaerden.gif
758 ms
kalender.gif
790 ms
news_bg.png
790 ms
galleryMenu_bg.jpg
731 ms
footer_li.png
733 ms
print.gif
744 ms
mail.gif
831 ms
background_footer.jpg
786 ms
footer_border_right.jpg
796 ms
footer_li2.jpg
726 ms
footer_border_bottom.jpg
734 ms
amc5lscaled.css
464 ms
_bOOtstrap.js
549 ms
bPicoDefault.css
569 ms
bg.values.png
125 ms
dblnk.gif
123 ms
map.png
124 ms
fallback-button.png
122 ms
bMtFLdr5.js
117 ms
print.css
130 ms
bConsole.js
121 ms
mobile.css
136 ms
ams.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
ARIA IDs are not unique
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
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
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.
ams.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Page has valid source maps
ams.at 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
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ams.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 Ams.at 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.
ams.at
Open Graph description is not detected on the main page of AMS. 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: