5.7 sec in total
528 ms
4.9 sec
303 ms
Welcome to hays.co.jp homepage info - get ready to check Hays best content for Japan right away, or after learning these important things about hays.co.jp
ヘイズジャパンは外資系・グローバル企業の転職エージェントです。IT、製薬・医療、製造業でのプログラマー、プロジェクトマネージャー、MR、CRA、エンジニア、セールスなど高いスキルを持つプロフェッショナルの転職をヘイズジャパンのコンサルタントがサポート。非公開求人も多数掲載。
Visit hays.co.jpWe analyzed Hays.co.jp page load time and found that the first response time was 528 ms and then it took 5.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
hays.co.jp performance score
name
value
score
weighting
Value10.0 s
0/100
10%
Value16.9 s
0/100
25%
Value13.3 s
2/100
10%
Value1,950 ms
8/100
30%
Value0.053
98/100
15%
Value19.9 s
2/100
10%
528 ms
908 ms
71 ms
934 ms
2049 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 57% of them (26 requests) were addressed to the original Hays.co.jp, 20% (9 requests) were made to and 9% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Hays.co.jp.
Page size can be reduced by 1.1 MB (52%)
2.1 MB
1.0 MB
In fact, the total size of Hays.co.jp main page is 2.1 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. 35% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 74.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 74.8 kB or 80% of the original size.
Potential reduce by 103.0 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, Hays needs image optimization as it can save up to 103.0 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 775.2 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 775.2 kB or 75% of the original size.
Potential reduce by 129.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. Hays.co.jp needs all CSS files to be minified and compressed as it can save up to 129.2 kB or 41% of the original size.
Number of requests can be reduced by 7 (21%)
34
27
The browser has sent 34 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 8 to 1 for JavaScripts and as a result speed up the page load time.
hays.co.jp
528 ms
index.htm
908 ms
572110822.js
71 ms
sitenavigationfunctions.js
934 ms
custom.js
2049 ms
fonts.css
52 ms
jquery-ui.css
1153 ms
main.css
1609 ms
A49AB006F6B3461B7.css
1279 ms
geo2.js
37 ms
event
12 ms
event
5 ms
document_r6_hdb.js
2482 ms
ga.js
34 ms
img_logo_hays.gif
242 ms
hays_291582.jpg
962 ms
hays_283503.jpg
962 ms
hays_318987.jpg
692 ms
hays_296129.jpg
1325 ms
hays_277330.jpg
513 ms
hays_288207.jpg
748 ms
hays_313614.png
1388 ms
hays_284548.jpg
1000 ms
hays_301791.jpg
1095 ms
hays_284551.jpg
1114 ms
hays_313618.png
1815 ms
hays_290628.jpg
1233 ms
hays_284484.jpg
1321 ms
hays_284558.jpg
1354 ms
hays_284432.jpg
1464 ms
hays_306305.png
1546 ms
hays_278234.jpg
1558 ms
gtm.js
73 ms
dhMBTfBew05g77R0pFR+x0C4176IbNZBr2FUnysZL3qWPtKlyMRP8+T23zHwYyPT3mZ4snx71L8AqJbQeU=
7 ms
SD5nNMugtlOJjJetVx9pXuhyJ+Hme3OY7DWZ8fMrLFE9Of5fiF1DUQdE=
7 ms
nyW2+42DGx6e8TPHk+HcpfgHC+UHt
6 ms
AKiW0Hl
5 ms
l+IXUNRB0Q==
6 ms
9kNksg95CKT5Wsl51rH2ly5GIn+fJbb7jYMbHp7xM8eT4dyl+AcL5Qe0=
5 ms
fontello.woff
1559 ms
__utm.gif
14 ms
AWTrQdk=
4 ms
9kNksg95CKT5Wsl52rH2ly5GIn+fJTb7jYMbHp7xM8eT4dyl+AbZyQe0=
4 ms
IyxZPj36X4BdcQQfU=
3 ms
analytics.js
11 ms
collect
12 ms
hays.co.jp 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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
hays.co.jp 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
hays.co.jp 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
Document doesn't have a valid hreflang
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
JA
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hays.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Hays.co.jp 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.co.jp
Open Graph description is not detected on the main page of Hays. 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: