10.4 sec in total
504 ms
8.9 sec
965 ms
Visit hunter.co.jp now to see the best up-to-date Hunter content for Japan and also check out these interesting facts you probably never knew about hunter.co.jp
Visit hunter.co.jpWe analyzed Hunter.co.jp page load time and found that the first response time was 504 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
hunter.co.jp performance score
name
value
score
weighting
Value9.5 s
0/100
10%
Value64.8 s
0/100
25%
Value22.0 s
0/100
10%
Value1,100 ms
23/100
30%
Value1.46
0/100
15%
Value45.3 s
0/100
10%
504 ms
679 ms
1344 ms
372 ms
512 ms
Our browser made a total of 108 requests to load all elements on the main page. We found that 57% of them (62 requests) were addressed to the original Hunter.co.jp, 8% (9 requests) were made to Scontent-nrt1-1.cdninstagram.com and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3.7 sec) relates to the external source Scontent-nrt1-1.cdninstagram.com.
Page size can be reduced by 847.3 kB (14%)
6.1 MB
5.2 MB
In fact, the total size of Hunter.co.jp main page is 6.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 61.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. 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 61.7 kB or 79% of the original size.
Potential reduce by 57.9 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. Hunter images are well optimized though.
Potential reduce by 284.9 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 284.9 kB or 68% of the original size.
Potential reduce by 442.9 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. Hunter.co.jp needs all CSS files to be minified and compressed as it can save up to 442.9 kB or 91% of the original size.
Number of requests can be reduced by 57 (60%)
95
38
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hunter. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
hunter.co.jp
504 ms
hunter.co.jp
679 ms
1344 ms
base.css
372 ms
style.css
512 ms
style.min.css
1101 ms
styles.css
557 ms
core.css
810 ms
additional_style2.css
608 ms
green.css
850 ms
slick-theme.css
694 ms
slick.css
743 ms
css
31 ms
jquery.bxslider.min.css
811 ms
additional_style.css
1563 ms
jquery.min.js
1116 ms
jquery-migrate.min.js
1011 ms
modal-multi.js
1010 ms
jquery-1.12.4.min.js
17 ms
additional_script2.js
1018 ms
css2
45 ms
ofi.min.js
1033 ms
platform.js
25 ms
index.js
1033 ms
index.js
1009 ms
jquery.easing.1.3.js
1101 ms
core.js
1121 ms
jquery.bxslider.js
1348 ms
index.min.js
33 ms
additional_script.js
1234 ms
jquery.pagetop.js
1234 ms
postviews-cache.js
1282 ms
slick.js
1512 ms
gtm.js
149 ms
441654901_455545756987056_1716471331337387173_n.webp
1727 ms
440393540_1155813789185148_3452409351296173657_n.jpg
2813 ms
439236627_1443561499596280_5072517588492048454_n.jpg
3212 ms
435476531_18392101321076153_3531303013604415628_n.jpg
3105 ms
435469833_18391910923076153_1267410048358761999_n.jpg
2898 ms
435644640_332749012726839_1029039986545512532_n.webp
2906 ms
435641107_467248405729521_821677807158494659_n.webp
2897 ms
435274924_438950772216256_5066820379599989130_n.webp
3344 ms
435277653_972610567828016_1814661647171629687_n.webp
3655 ms
logo-300x42.png
252 ms
top_bana.jpg
476 ms
main_ttl_pc.png
254 ms
mainvisual.jpg
1204 ms
mainvisual01.jpg
1060 ms
mainvisual02.jpg
851 ms
mainvisual03.jpg
951 ms
mainvisual04.jpg
476 ms
54945e17883133e80cd1bcd54cf6fa7c.jpg
1263 ms
85c6fbadd054eab762f7638ab498b253.jpg
658 ms
4642ad893e345c0bd05aa41fd52d1052.jpg
837 ms
671f45d3d2beff4e3bb24ef9e1ade2c1.png
1012 ms
15a06b5e669b4ad147f5ab7099a92c80.png
1038 ms
2022_SDGs_192px_71px.jpg
1121 ms
logo.png
1186 ms
social_facebook.png
1224 ms
social_twitter.png
1262 ms
social_instagram.png
1290 ms
social_line.png
1359 ms
logo_tokyusnowresort.png
1387 ms
map.png
1410 ms
sdk.js
54 ms
tokyu.png
1461 ms
nav-splitline.png
1461 ms
title_line.gif
1433 ms
YuGothicM.woff
2382 ms
YuGothicB.woff
3200 ms
KFOlCnqEu92Fr1MmEU9vAw.ttf
74 ms
KFOmCnqEu92Fr1Me5Q.ttf
190 ms
KFOlCnqEu92Fr1MmSU5vAw.ttf
247 ms
KFOkCnqEu92Fr1MmgWxP.ttf
284 ms
KFOlCnqEu92Fr1MmWUlvAw.ttf
284 ms
KFOlCnqEu92Fr1MmYUtvAw.ttf
284 ms
icon_instagram.png
1561 ms
icon_facebook.png
1594 ms
icon_twitter.png
1629 ms
embed
421 ms
80ebc9dea9a1bd2fe4ed2ee3f9e3f7c1.png
1612 ms
8201d40135deb7c259359243bd95d008.png
1730 ms
admin-ajax.php
2179 ms
7Auup_AqnyWWAxW2Wk3swUz56MS91Eww8SX21nejpw.ttf
157 ms
sdk.js
128 ms
ajax-loader.gif
1727 ms
slick.woff
1726 ms
js
117 ms
js
275 ms
analytics.js
270 ms
ytag.js
797 ms
destination
229 ms
destination
267 ms
fbevents.js
70 ms
lt.js
265 ms
kitchen.juicer.cc
779 ms
227 ms
209 ms
js
233 ms
155 ms
collect
125 ms
err.gif
703 ms
collect
12 ms
ga-audiences
63 ms
19 ms
pd.js
54 ms
collect
33 ms
analytics
24 ms
hunter.co.jp accessibility score
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
<frame> or <iframe> elements do not have a title
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
hunter.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
hunter.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
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
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hunter.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Hunter.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.
hunter.co.jp
Open Graph description is not detected on the main page of Hunter. 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: