Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

hokugin.co.jp

北陸銀行 | 個人のお客さまトップページ

Page Load Speed

12.7 sec in total

First Response

851 ms

Resources Loaded

11.6 sec

Page Rendered

221 ms

hokugin.co.jp screenshot

About Website

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.jp

Key Findings

We analyzed Hokugin.co.jp page load time and found that the first response time was 851 ms and then it took 11.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.

Performance Metrics

hokugin.co.jp performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.3 s

1/100

10%

LCP (Largest Contentful Paint)

Value25.3 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value470 ms

61/100

30%

CLS (Cumulative Layout Shift)

Value0.507

16/100

15%

TTI (Time to Interactive)

Value31.6 s

0/100

10%

Network Requests Diagram

hokugin.co.jp

851 ms

reset.css

353 ms

jquery.bxslider.css

360 ms

flexslider.css

360 ms

common.css

1081 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 98% of them (147 requests) were addressed to the original Hokugin.co.jp, 1% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to B92.yahoo.co.jp. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Hokugin.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 456.1 kB (30%)

Content Size

1.5 MB

After Optimization

1.0 MB

In fact, the total size of Hokugin.co.jp main page is 1.5 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. 45% of websites need less resources to load. Images take 943.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 49.4 kB

  • Original 57.9 kB
  • After minification 47.4 kB
  • After compression 8.5 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 10.5 kB, which is 18% 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 49.4 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 13.7 kB

  • Original 943.9 kB
  • After minification 930.1 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.

JavaScript Optimization

-74%

Potential reduce by 238.8 kB

  • Original 323.1 kB
  • After minification 247.7 kB
  • After compression 84.3 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 238.8 kB or 74% of the original size.

CSS Optimization

-89%

Potential reduce by 154.2 kB

  • Original 174.1 kB
  • After minification 136.7 kB
  • After compression 19.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. Hokugin.co.jp needs all CSS files to be minified and compressed as it can save up to 154.2 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (14%)

Requests Now

149

After Optimization

128

The browser has sent 149 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 14 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

hokugin.co.jp accessibility score

69

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA toggle fields do not have accessible names

High

[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

High

<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

High

Form elements do not have associated labels

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

hokugin.co.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

hokugin.co.jp SEO score

98

Search Engine Optimization Advices

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: