19.7 sec in total
511 ms
18.3 sec
843 ms
Click here to check amazing Hokugin content for Japan. Otherwise, check out these important facts you probably never knew about hokugin.co.jp
北陸銀行のホームページです。口座開設から各種ローン、投資信託などの個人向けサービスから、法人向けコンサルティングサービスまでご案内しています。
Visit hokugin.co.jpWe analyzed Hokugin.co.jp page load time and found that the first response time was 511 ms and then it took 19.2 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.
hokugin.co.jp performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value28.7 s
0/100
25%
Value22.8 s
0/100
10%
Value1,300 ms
18/100
30%
Value0.46
19/100
15%
Value30.3 s
0/100
10%
511 ms
2238 ms
65 ms
765 ms
765 ms
Our browser made a total of 178 requests to load all elements on the main page. We found that 64% of them (114 requests) were addressed to the original Hokugin.co.jp, 4% (7 requests) were made to F1-as.readspeaker.com and 3% (5 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5.5 sec) belongs to the original domain Hokugin.co.jp.
Page size can be reduced by 682.1 kB (9%)
7.4 MB
6.8 MB
In fact, the total size of Hokugin.co.jp main page is 7.4 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. 65% of websites need less resources to load. Images take 6.5 MB which makes up the majority of the site volume.
Potential reduce by 90.3 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 22.4 kB, which is 21% 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 90.3 kB or 85% of the original size.
Potential reduce by 59.2 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. Hokugin images are well optimized though.
Potential reduce by 311.8 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 311.8 kB or 52% of the original size.
Potential reduce by 220.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. Hokugin.co.jp needs all CSS files to be minified and compressed as it can save up to 220.7 kB or 87% of the original size.
Number of requests can be reduced by 72 (42%)
173
101
The browser has sent 173 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hokugin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 39 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
hokugin.co.jp
511 ms
www.hokugin.co.jp
2238 ms
gtm.js
65 ms
reset.css
765 ms
slick.css
765 ms
slick-theme.css
758 ms
common.css
1644 ms
top.css
1250 ms
sp.css
1338 ms
top_sp.css
1146 ms
jquery.js
1856 ms
jquery.cookie.js
1012 ms
jquery.heightLine.js
1346 ms
jquery.easing.1.3.js
1316 ms
slick.js
1919 ms
common.js
1996 ms
top.js
1534 ms
geolocation.search.js
1534 ms
ReadSpeaker.js
716 ms
js
52 ms
analytics.js
17 ms
destination
41 ms
collect
157 ms
collect
32 ms
js
50 ms
ga-audiences
217 ms
helpfeel-element.js
143 ms
s_retargeting.js
734 ms
bn_smp_app.jpg
830 ms
bn_smp_app_close.png
228 ms
header_logo.gif
358 ms
btn_branch_pc.gif
226 ms
character_size.gif
227 ms
btn_small.gif
226 ms
btn_medium.gif
358 ms
btn_large.gif
358 ms
btn_search_keyword.gif
361 ms
btn_menu_off.gif
384 ms
header_img_directa.png
536 ms
index_list01_img01_pc.png
521 ms
header_img_business01.gif
528 ms
header_img_business02.jpg
713 ms
header_img_business03.jpg
912 ms
header_img_business04.jpg
1026 ms
side_btn_open_close_off.png
708 ms
icon_window.gif
720 ms
index_mv20_pc.jpg
2628 ms
index_mv06_pc.jpg
2289 ms
index_mv01_pc.jpg
2538 ms
index_list01_img05_pc.png
1005 ms
index_list01_img02_pc.png
1105 ms
index_list01_img03_pc.png
1158 ms
index_list01_img04_pc.png
1193 ms
index_list02_img01_off_pc.png
1458 ms
index_list02_img02_off_pc.png
1337 ms
index_list02_img03_off_pc.png
1525 ms
index_list02_img04_off_pc.png
1517 ms
index_list02_img05_off_pc.png
1636 ms
index_list02_img10_off_pc.png
1684 ms
index_list02_img07_off_pc.png
1691 ms
index_list02_img08_off_pc.png
1819 ms
index_list02_img09_off_pc.png
1859 ms
index_campaign_img54.jpg
3182 ms
vts2.js
24 ms
index_campaign_img53.jpg
2894 ms
ReadSpeaker.Styles.css
140 ms
ReadSpeaker.Core.js
331 ms
ReadSpeaker.pub.Config.js
469 ms
search_tool_n3.js
713 ms
rs_button.png
512 ms
index_campaign_img52.jpg
2656 ms
index_campaign_img51.jpg
3441 ms
index_seminar_plaza.jpg
2833 ms
index_campaign_img55.jpg
3442 ms
ytag.js
733 ms
fe23ce3a12e28b29_2812.js
131 ms
tag.js
131 ms
od.js
117 ms
slick.woff
2712 ms
index_purpose_icon_plus.gif
2740 ms
index_purpose_img01_pc.jpg
3037 ms
tracking.min.js
10 ms
js
41 ms
index_purpose_img02_pc.jpg
3214 ms
index_purpose_img03_pc.jpg
3234 ms
lt.js
26 ms
conversion.js
680 ms
err.gif
836 ms
ReadSpeaker.lib.Facade.adapter.jquery.js
135 ms
index_purpose_img04_pc.jpg
3003 ms
index_purpose_img05_smp.jpg
3895 ms
index_life_plan_img01.jpg
3345 ms
ReadSpeaker.Base.js
281 ms
index_life_plan_img02.jpg
3565 ms
index_life_plan_img03.jpg
3471 ms
index_life_plan_img04.jpg
3289 ms
index_life_plan_img05.jpg
3533 ms
index_life_plan_img06.jpg
3136 ms
tr
247 ms
index_life_plan_img07.jpg
3701 ms
index_life_plan_img08.jpg
3854 ms
icon_personal.gif
3270 ms
conversion_async.js
1518 ms
conversion.js
89 ms
icon_corp.gif
3287 ms
icon_ir.gif
3339 ms
34 ms
76 ms
71 ms
fbevents.js
25 ms
pixel2.js
14 ms
err.gif
223 ms
46 ms
15 ms
19 ms
index_recommended_img28.jpg
4279 ms
index_recommended_img26.jpg
3789 ms
index_recommended_img22.jpg
3260 ms
index_recommended_img13.jpg
4037 ms
index_recommended_img12.jpg
3447 ms
index_recommended_img01.jpg
3776 ms
index_recommended_img02.jpg
4043 ms
index_recommended_img03.jpg
4301 ms
index_recommended_img04.jpg
4550 ms
pixel
169 ms
iframe
190 ms
index_recommended_img15.jpg
4506 ms
pixel
110 ms
Pug
102 ms
hs
833 ms
sync.ad-stir.com
718 ms
tap.php
99 ms
sync
817 ms
101 ms
cookiesync
722 ms
cs
726 ms
sync.ad
251 ms
cs
689 ms
sync
270 ms
sync
99 ms
169 ms
sd
6 ms
bounce
10 ms
sync
19 ms
index_recommended_img06.jpg
3891 ms
index_recommended_img07.jpg
3877 ms
606 ms
635 ms
index_recommended_img09.jpg
3730 ms
index_banner_img01.jpg
3407 ms
index_banner_img02.jpg
3762 ms
index_banner_img03.jpg
3678 ms
index_banner_img04.jpg
4039 ms
index_banner_img05.jpg
3857 ms
footer_btn_pagetop.png
3382 ms
footer_img_chara_off.gif
3399 ms
footer_img_copyright.gif
3378 ms
btn_procedure_pc_off.png
3534 ms
arrow05.gif
3348 ms
arrow03.gif
3434 ms
bg_01.gif
3257 ms
index_list01_bg01_pc.jpg
5099 ms
index_list01_icon_win.gif
3180 ms
index_list01_icon_login.gif
3085 ms
index_list02_bg_pc.gif
3206 ms
index_icon_dot.png
2962 ms
common_bg_title01.gif
2948 ms
index_common_bg_title02_pc.png
2988 ms
arrow27.png
2995 ms
icon_win.png
2953 ms
icon_footer_plus.png
2782 ms
arrow02.gif
2823 ms
btn_small_on.gif
2739 ms
ajax-loader.gif
3483 ms
index_list01_bg02_pc.jpg
5536 ms
rep
171 ms
new_i_search_assist.js
3575 ms
new_ac.css
507 ms
hokugin.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-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
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.
[aria-*] attributes do not have valid values
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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>).
hokugin.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
hokugin.co.jp SEO score
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hokugin.co.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Hokugin.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.
hokugin.co.jp
Open Graph description is not detected on the main page of Hokugin. 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: