8.7 sec in total
1.1 sec
6.8 sec
834 ms
Click here to check amazing Hays content for Denmark. Otherwise, check out these important facts you probably never knew about hays.dk
I en verden der konstant udvikler sig, er Hays stadig fast besluttet på at hjælpe dig. Vores rekrutteringsspecialister er klar til at hjælpe dig både på kort- og på lang sigt.
Visit hays.dkWe analyzed Hays.dk page load time and found that the first response time was 1.1 sec and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
hays.dk performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value15.5 s
0/100
25%
Value17.2 s
0/100
10%
Value2,710 ms
3/100
30%
Value0.09
92/100
15%
Value22.4 s
1/100
10%
1087 ms
30 ms
143 ms
123 ms
575 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 86% of them (59 requests) were addressed to the original Hays.dk, 6% (4 requests) were made to Consent.trustarc.com and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Hays.dk.
Page size can be reduced by 274.5 kB (11%)
2.5 MB
2.3 MB
In fact, the total size of Hays.dk main page is 2.5 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. 60% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 237.7 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 41.0 kB, which is 15% 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 237.7 kB or 85% of the original size.
Potential reduce by 22.4 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.4 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 42 (67%)
63
21
The browser has sent 63 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 36 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.hays.dk
1087 ms
irthy-for-them-well-put-rect-Wassation-Was-those
30 ms
notice
143 ms
trustarc_events.js
123 ms
combo
575 ms
main.css
293 ms
clay.css
857 ms
combo
445 ms
loader.js
201 ms
combo
669 ms
log
75 ms
v1.7-3281
4 ms
main.css
1561 ms
main.css
460 ms
jquery-ui.min.js
3445 ms
haysFormularParser.js
489 ms
jquery.ui.totop.js
558 ms
eyeAble.js
966 ms
www.hays.de.js
654 ms
11925.play
32 ms
js.cookie.js
707 ms
jquery.searchHistory.js
675 ms
rrssb.min.js
695 ms
jquery.sticky.js
716 ms
picturePolyfill.min.js
768 ms
hays.tracking.js
795 ms
html2canvas.js
1015 ms
jspdf.umd.min.js
1059 ms
html2pdf.bundle.min.js
1595 ms
hays-non-ie9.css
982 ms
combo
850 ms
main.js
843 ms
searchbar.js
896 ms
mainnavi.js
990 ms
bildarchiv.js
947 ms
presseartikel.js
996 ms
slick.min.js
38 ms
ics.js
1045 ms
selectize.js
1116 ms
geo_field.js
1097 ms
_Incapsula_Resource
1058 ms
font-roboto-style.css
108 ms
jquery-ui.css
115 ms
lr-hays-logo.svg
143 ms
lr-hays-logo-mobil.svg
145 ms
3eb4b8f9-62a6-9a5d-8fa7-0dbac53869c2
180 ms
54d2175b-016b-145a-3fa1-ee84d03e4c6f
146 ms
29820c9d-c6d2-56ba-c8de-7cefa4952d89
145 ms
b32be7d7-84ba-49a8-159f-b77d6b928eb2
145 ms
960c0d6d-1414-b046-f664-577163cd7928
210 ms
a65fa4ff-db10-18ad-23f1-49cd12a170c8
421 ms
efa17c4c-445e-7e64-b90c-488bf2c4d466
267 ms
3aac2dea-a889-e655-d4e2-4088dc6782d0
266 ms
0497d008-e883-bccd-1b7b-5a864add8883
266 ms
get
137 ms
gtm.js
95 ms
eye-able_whitelabel-icon_2.svg
126 ms
Sticky-kontakt_icon.svg
169 ms
Roboto-Regular.ttf
1419 ms
Roboto-Medium.ttf
297 ms
Roboto-Light.ttf
297 ms
Roboto-Bold.ttf
297 ms
header-keyvisual-desktop.png
1406 ms
arrow_for_txt_links.svg
286 ms
home-keyvisual-branchen-desktop
153 ms
_Incapsula_Resource
33 ms
js
57 ms
insight.min.js
186 ms
irthy-for-them-well-put-rect-Wassation-Was-those
51 ms
hays.dk 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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
hays.dk 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
Missing source maps for large first-party JavaScript
hays.dk 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
DA
DA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hays.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and it matches the claimed language. Our system also found out that Hays.dk 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.dk
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: