7.2 sec in total
528 ms
6 sec
764 ms
Welcome to hokepon.com homepage info - get ready to check Hokepon best content for Japan right away, or after learning these important things about hokepon.com
保険見直しや選び方をすべて無料でアドバイス。全国300店舗を超える保険相談窓口、取扱保険会社40社以上の保険商品の中から「あなたにぴったりの保険」をご提案します。
Visit hokepon.comWe analyzed Hokepon.com page load time and found that the first response time was 528 ms and then it took 6.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
hokepon.com performance score
528 ms
944 ms
307 ms
460 ms
1071 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 70% of them (81 requests) were addressed to the original Hokepon.com, 2% (2 requests) were made to S.yimg.jp and 2% (2 requests) were made to Googleadservices.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Hokepon.com.
Page size can be reduced by 340.4 kB (42%)
816.2 kB
475.8 kB
In fact, the total size of Hokepon.com main page is 816.2 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. 35% of websites need less resources to load. Images take 371.9 kB which makes up the majority of the site volume.
Potential reduce by 43.0 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 43.0 kB or 74% of the original size.
Potential reduce by 59.6 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, Hokepon needs image optimization as it can save up to 59.6 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 203.0 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 203.0 kB or 59% of the original size.
Potential reduce by 34.8 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. Hokepon.com needs all CSS files to be minified and compressed as it can save up to 34.8 kB or 84% of the original size.
Number of requests can be reduced by 38 (35%)
110
72
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hokepon. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
hokepon.com
528 ms
www.hokepon.com
944 ms
import.css
307 ms
top.css
460 ms
jquery.js
1071 ms
put_cookie.js
646 ms
base.js
493 ms
ld.js
25 ms
booth-search-form.js
310 ms
reset.css
301 ms
base.css
608 ms
shop-search.css
305 ms
conversion_async.js
21 ms
conversion_async.js
478 ms
jquery.bxSlider.min.js
368 ms
jquery.easing-1.3.min.js
306 ms
top.js
312 ms
analytics.js
48 ms
hdrlogo.png
160 ms
pfm.png
160 ms
event
49 ms
nwtel-0120330526.png
306 ms
hdrnav1.png
167 ms
hdrnav2.png
165 ms
hdrnav3.png
167 ms
hdrnav6.png
299 ms
hdrnav5.png
298 ms
tip1.png
306 ms
tip2.png
324 ms
btn-nwrsv.png
323 ms
spacer.gif
444 ms
mainvisual.jpg
748 ms
mainvisual-5.gif
754 ms
mainvisual-4.jpg
454 ms
mainvisual-2.gif
840 ms
mainvisual-3.gif
688 ms
mi-topsearch.png
595 ms
icon-parking.gif
578 ms
icon-kids.gif
720 ms
icon-top1.png
730 ms
listmark.gif
824 ms
icon-top2.png
871 ms
icon-top3.png
873 ms
topimg.gif
1027 ms
flow-arw.png
892 ms
flow-img1.png
931 ms
flow-img2.png
985 ms
flow-op.png
1023 ms
flow-img3.png
1023 ms
flow-img4.png
1043 ms
flow-img5.png
1092 ms
arrow-b.png
1148 ms
voice_00436.jpg
1325 ms
voice-img1.jpg
1175 ms
voice-img3.jpg
1178 ms
event
338 ms
voice-img5.jpg
1087 ms
collect
10 ms
collect
59 ms
voice_00424.jpg
1299 ms
voice-img2.jpg
1191 ms
voice-img4.jpg
1211 ms
tag.js
189 ms
conversion_async.js
638 ms
voice-img6.jpg
1210 ms
bnr-faq.jpg
1092 ms
bnr-voice.jpg
1221 ms
bnr-visit.jpg
1218 ms
bnr-info.jpg
1218 ms
bnr-recruit.jpg
1203 ms
arw-infotab.png
1219 ms
tag
8 ms
icon-shop.gif
1172 ms
icon-other.gif
1222 ms
icon-media.gif
1070 ms
logo-mdrt.gif
1064 ms
logo-ccaj.gif
984 ms
logo-iso.gif
943 ms
logo-newton.gif
1029 ms
bnr-msf.png
1066 ms
qr.jpg
1213 ms
xsync
772 ms
ct_tag.php
561 ms
ya.js
384 ms
conversion_async.js
29 ms
blade_track_jp.js
348 ms
990 ms
bnr-twitter.png
988 ms
44 ms
conversion.js
849 ms
39 ms
listmark2.gif
939 ms
listmark3.gif
1037 ms
44 ms
60 ms
ftrlogo.png
1050 ms
rsv-visual.png
1019 ms
mi-srh.png
976 ms
btn-nwsrh.png
949 ms
pagetop.png
1045 ms
arw-lft.png
1067 ms
arw-rgt.png
1050 ms
cookie_enabled_get.html
339 ms
pb.js
155 ms
365 ms
log.php
390 ms
pta.js
341 ms
fbevents.js
15 ms
95 ms
bl_track.cgi
364 ms
conversion.js
899 ms
21898572.js
508 ms
pn
366 ms
797 ms
conversion_async.js
157 ms
dis.aspx
398 ms
hokepon.com SEO score
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hokepon.com 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 Hokepon.com 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.
hokepon.com
Open Graph data is detected on the main page of Hokepon. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: