23.2 sec in total
2 sec
20.6 sec
617 ms
Welcome to hays.at homepage info - get ready to check Hays best content for Austria right away, or after learning these important things about hays.at
Wir beraten Sie zu allen Themen, die Sie für eine erfolgreiche Personalstrategie benötigen.
Visit hays.atWe analyzed Hays.at page load time and found that the first response time was 2 sec and then it took 21.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
hays.at performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value11.2 s
0/100
25%
Value26.7 s
0/100
10%
Value3,350 ms
2/100
30%
Value0.078
95/100
15%
Value24.3 s
0/100
10%
1969 ms
30 ms
128 ms
121 ms
380 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 88% of them (60 requests) were addressed to the original Hays.at, 6% (4 requests) were made to Consent.trustarc.com and 1% (1 request) were made to Arc.nexx.cloud. The less responsive or slowest element that took the longest time to load (12.4 sec) belongs to the original domain Hays.at.
Page size can be reduced by 291.4 kB (10%)
2.9 MB
2.6 MB
In fact, the total size of Hays.at main page is 2.9 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. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 249.4 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 39.9 kB, which is 14% 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 249.4 kB or 86% of the original size.
Potential reduce by 27.5 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. Hays images are well optimized though.
Potential reduce by 14.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 40 (65%)
62
22
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hays. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.hays.at
1969 ms
erfores-and-what-in-away-his-and-bes-thou-time-D
30 ms
notice
128 ms
trustarc_events.js
121 ms
main.css
380 ms
combo
1108 ms
clay.css
2787 ms
combo
469 ms
loader.js
211 ms
combo
1159 ms
log
81 ms
v1.7-3281
4 ms
main.css
12422 ms
main.css
845 ms
jquery-ui.min.js
2530 ms
haysFormularParser.js
1047 ms
jquery.ui.totop.js
1097 ms
eyeAble.js
2801 ms
www.hays.de.js
1196 ms
11925.play
37 ms
js.cookie.js
1198 ms
jquery.searchHistory.js
1497 ms
rrssb.min.js
1295 ms
jquery.sticky.js
1396 ms
picturePolyfill.min.js
1493 ms
hays.tracking.js
1590 ms
html2canvas.js
2235 ms
jspdf.umd.min.js
4134 ms
html2pdf.bundle.min.js
6683 ms
hays-non-ie9.css
2618 ms
combo
2710 ms
main.js
1625 ms
searchbar.js
1727 ms
mainnavi.js
1793 ms
bildarchiv.js
1823 ms
presseartikel.js
1886 ms
slick.min.js
18 ms
ics.js
1922 ms
selectize.js
2515 ms
geo_field.js
2117 ms
_Incapsula_Resource
2124 ms
font-roboto-style.css
100 ms
jquery-ui.css
285 ms
lr-hays-logo.svg
126 ms
lr-hays-logo-mobil.svg
106 ms
06aabe53-bfc9-dcb3-4143-6ebf4d07850b
1485 ms
5fdae5f7-f22b-3bef-4930-89bfbbce9e0d
1481 ms
A1_Telekom_Austria.png
236 ms
ZZD_ref_capgemini-consulting-oesterreich.png
237 ms
T_fsg-raiffeisenbank-int.png
236 ms
Logo_Bayer_300x300px.jpg
319 ms
ZW_ref_laola1-multimedia.png
423 ms
ZZZCref_generali-deutschland-informatik-services.png
426 ms
6110ec21-e036-e038-5b23-3013eea846b8
2085 ms
icon-link-extern-20x20.png
423 ms
get
101 ms
gtm.js
104 ms
eye-able_whitelabel-icon_2.svg
1377 ms
Sticky-kontakt_icon.svg
1375 ms
Roboto-Regular.ttf
1361 ms
Roboto-Medium.ttf
1985 ms
Roboto-Light.ttf
1549 ms
Roboto-Bold.ttf
1357 ms
header-keyvisual-desktop.png
6359 ms
home-keyvisual-branchen-desktop
1193 ms
arrow_for_txt_links.svg
1193 ms
_Incapsula_Resource
1062 ms
erfores-and-what-in-away-his-and-bes-thou-time-D
33 ms
hays.at accessibility score
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
Image elements do not have [alt] attributes
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
Some elements have a [tabindex] value greater than 0
hays.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
hays.at 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
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hays.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 Hays.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.
hays.at
Open Graph data is detected on the main page of Hays. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: