23.5 sec in total
913 ms
22.2 sec
388 ms
Click here to check amazing HUNTER Investigate content for Japan. Otherwise, check out these important facts you probably never knew about hunter-investigate.jp
調査報道サイト。HUNTER(ハンター)
Visit hunter-investigate.jpWe analyzed Hunter-investigate.jp page load time and found that the first response time was 913 ms and then it took 22.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
hunter-investigate.jp performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value4.6 s
34/100
25%
Value6.3 s
41/100
10%
Value700 ms
42/100
30%
Value0.202
61/100
15%
Value14.5 s
8/100
10%
913 ms
1086 ms
2004 ms
546 ms
546 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 21% of them (29 requests) were addressed to the original Hunter-investigate.jp, 9% (12 requests) were made to Adm.shinobi.jp and 6% (8 requests) were made to Ssp.advg.jp. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Hunter-investigate.jp.
Page size can be reduced by 256.8 kB (34%)
744.9 kB
488.1 kB
In fact, the total size of Hunter-investigate.jp main page is 744.9 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. 45% of websites need less resources to load. Images take 356.0 kB which makes up the majority of the site volume.
Potential reduce by 24.2 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 4.3 kB, which is 13% 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 24.2 kB or 75% of the original size.
Potential reduce by 25.3 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 Investigate images are well optimized though.
Potential reduce by 192.6 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 192.6 kB or 57% of the original size.
Potential reduce by 14.7 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-investigate.jp needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 85% of the original size.
Number of requests can be reduced by 84 (67%)
126
42
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HUNTER Investigate. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
hunter-investigate.jp
913 ms
styles.css
1086 ms
head_rogo.jpg
2004 ms
head_rogo02.gif
546 ms
menu01.jpg
546 ms
menu02.jpg
1292 ms
menu04.jpg
1211 ms
menu05.jpg
894 ms
menu03.jpg
717 ms
head03.jpg
1062 ms
%E5%85%AC%E6%98%8E%E5%85%9A%E3%80%80%E7%9C%8B%E6%9D%BF-thumb-240x192-16985.jpg
1509 ms
kji_zenbun_btn.jpg
1254 ms
20160407_h01-01s-thumb-120x120-16967.jpg
4964 ms
212db1905dd233d801eeeeda5c5dc612
663 ms
brand
304 ms
61bb946ec8b230697df38e7770d3ea8c
640 ms
451905fc50dc7c57b3def7b365cfbb3a
632 ms
show_ads.js
298 ms
fukuoka-shiyakusho06_s-thumb-120x120-16849.jpg
1899 ms
20160405_h01-01s-thumb-120x120-16922.jpg
3480 ms
20160404_h01-01s-thumb-120x120-16888.jpg
3583 ms
list_01.jpg
3056 ms
list_bar02.jpg
1965 ms
list_02.jpg
2100 ms
list_03.jpg
2269 ms
list_04.jpg
2580 ms
brand
165 ms
403138493058891.2532.211529871.png
146 ms
oneshot03.jpg
3827 ms
%E5%A4%A9%E7%A5%9E%E5%9C%B0%E4%B8%8B%E8%A1%97-thumb-4912x3264-16271.jpg
20416 ms
shin-list.jpg
2630 ms
chu-list.jpg
3020 ms
goiken.jpg
3767 ms
support_side_bnr02.gif
3606 ms
footer.jpg
3501 ms
google_custom_search_watermark.gif
90 ms
widgets.js
157 ms
ca-pub-6016018401358213.js
233 ms
zrt_lookup.html
219 ms
show_ads_impl.js
250 ms
1.0.1.js
626 ms
ga.js
60 ms
new.png
3517 ms
__utm.gif
110 ms
timeline.0eae788bc4fdbe9cd3e72dca3bc26358.js
390 ms
ads
96 ms
osd.js
130 ms
syndication
153 ms
397873207597731840
346 ms
1.0.0.js
208 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
64 ms
timeline.f7130f11be9c2719286897ede16853b9.light.ltr.css
237 ms
sync
371 ms
hunter_twitter_normal.jpg
360 ms
212db1905dd233d801eeeeda5c5dc612
763 ms
61bb946ec8b230697df38e7770d3ea8c
784 ms
451905fc50dc7c57b3def7b365cfbb3a
433 ms
sync
491 ms
sync
543 ms
push_sync
432 ms
jot
71 ms
js1
506 ms
ib
506 ms
cookiesync
356 ms
1.1.0.js
216 ms
sync
390 ms
js1
441 ms
ib
411 ms
js1
459 ms
ib
391 ms
js
547 ms
receive_sync
209 ms
js
583 ms
js
467 ms
jstag
108 ms
sh.adingo.jp
482 ms
show.php
416 ms
sync
890 ms
push_sync
766 ms
cm
429 ms
sync
236 ms
ads.js
161 ms
i.adingo.jp
428 ms
acj
313 ms
adcomp_pc.js
79 ms
sspcore_spot.js
303 ms
ri
46 ms
ssp_spot.ashx
559 ms
imp
203 ms
acj
51 ms
764 ms
imp
310 ms
ri
58 ms
729 ms
709 ms
a1033891.js
411 ms
sync
80 ms
adcore.js
59 ms
adcore_pc.js
70 ms
a1033893.js
421 ms
sync
19 ms
adcore_pc_inline.js
95 ms
ad_spot.aspx
591 ms
jsk
443 ms
jsk
525 ms
ssp_spot.ashx
762 ms
gl0
1045 ms
style.css
661 ms
ad_creative.ashx
302 ms
js0
372 ms
gl0
190 ms
js
676 ms
ad_spot.aspx
217 ms
ad_creative.ashx
327 ms
defaultAd.gif
202 ms
yads.js
588 ms
acs
292 ms
acs
190 ms
pixel
98 ms
cs
240 ms
cs
427 ms
sync
14 ms
cs
362 ms
yads_vimps-1.4.1.js
630 ms
tag
661 ms
1335 ms
yads-iframe.html
178 ms
tag
389 ms
oi
401 ms
cs
205 ms
bd
46 ms
cs
182 ms
sync
323 ms
push_sync
162 ms
acs
363 ms
cs
206 ms
gcs
426 ms
cs
224 ms
sync
697 ms
hunter-investigate.jp accessibility score
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
hunter-investigate.jp 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
Serves images with low resolution
hunter-investigate.jp SEO score
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
![]()
JA
![]()
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hunter-investigate.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-investigate.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-investigate.jp
Open Graph data is detected on the main page of HUNTER Investigate. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: