Tools & Wizards About Us
hozan.co.jp screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 67% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

hozan.co.jp

【HOZAN】　ホーザン株式会社

Page Load Speed

4.2 sec in total

First Response

1.3 sec

Resources Loaded

2.7 sec

Page Rendered

186 ms

hozan.co.jp screenshot

About Website

Welcome to hozan.co.jp homepage info - get ready to check HOZAN best content for Japan right away, or after learning these important things about hozan.co.jp

工具メーカー　ホーザン株式会社の公式サイトです。弱電作業環境に必要な製品や電気工事士技能試験用工具などを幅広くラインナップ。精密ニッパー・圧着工具・ピンセット等の手工具、工具セット、静電気対策品、クリーン環境対策品など。

Visit hozan.co.jp

Key Findings

We analyzed Hozan.co.jp page load time and found that the first response time was 1.3 sec and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

hozan.co.jp performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

hozan.co.jp

1326 ms

default_index.css

523 ms

HOZAN.gif

361 ms

hozan_kabu.gif

364 ms

yajirusi_ue.gif

375 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 84% of them (52 requests) were addressed to the original Hozan.co.jp, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Hozan.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 425.0 kB (55%)

Content Size

773.9 kB

After Optimization

348.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hozan.co.jp main page is 773.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. 30% of websites need less resources to load. CSS take 252.0 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 70.2 kB

  • Original 77.7 kB
  • After minification 55.8 kB
  • After compression 7.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 21.9 kB, which is 28% 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 70.2 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 13.1 kB

  • Original 225.2 kB
  • After minification 212.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. HOZAN images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 132.3 kB

  • Original 219.0 kB
  • After minification 218.9 kB
  • After compression 86.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 132.3 kB or 60% of the original size.

CSS Optimization

-83%

Potential reduce by 209.3 kB

  • Original 252.0 kB
  • After minification 250.4 kB
  • After compression 42.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. Hozan.co.jp needs all CSS files to be minified and compressed as it can save up to 209.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (40%)

Requests Now

58

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HOZAN. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

hozan.co.jp

hozan.co.jp

1326 ms

default_index.css

default_index.css

523 ms

HOZAN.gif

HOZAN.gif

361 ms

hozan_kabu.gif

hozan_kabu.gif

364 ms

yajirusi_ue.gif

yajirusi_ue.gif

375 ms

kensaku.gif

kensaku.gif

366 ms

w.gif

w.gif

365 ms

image1.jpg

image1.jpg

1375 ms

mark_1.gif

mark_1.gif

211 ms

2016-F751.jpg

2016-F751.jpg

331 ms

2016-L505.jpg

2016-L505.jpg

354 ms

2016-F717.jpg

2016-F717.jpg

358 ms

2016-P640.jpg

2016-P640.jpg

396 ms

2016-L600.jpg

2016-L600.jpg

503 ms

2016-F720.jpg

2016-F720.jpg

531 ms

2015-L803.jpg

2015-L803.jpg

539 ms

2015-L715.jpg

2015-L715.jpg

554 ms

2015-L717.jpg

2015-L717.jpg

558 ms

2015-Z268.jpg

2015-Z268.jpg

683 ms

2015-DK18.jpg

2015-DK18.jpg

724 ms

2015-P958.jpg

2015-P958.jpg

725 ms

2014-P925.jpg

2014-P925.jpg

739 ms

2014-P926.jpg

2014-P926.jpg

743 ms

yajirusi_naka.jpg

yajirusi_naka.jpg

857 ms

back_img_ue1.gif

back_img_ue1.gif

719 ms

back_img_main3.jpg

back_img_main3.jpg

735 ms

back_img_left1.gif

back_img_left1.gif

753 ms

back_img_left2.gif

back_img_left2.gif

757 ms

back_img_left4a.gif

back_img_left4a.gif

859 ms

back_img_left5a.gif

back_img_left5a.gif

898 ms

back_img_left3.gif

back_img_left3.gif

916 ms

back_img_naka1.gif

back_img_naka1.gif

937 ms

back_img_naka2.gif

back_img_naka2.gif

941 ms

back_img_naka3.gif

back_img_naka3.gif

1033 ms

back_img_right1a.gif

back_img_right1a.gif

1047 ms

back_img_right2.gif

back_img_right2.gif

1066 ms

catalog.jpg

catalog.jpg

1092 ms

yajirusi_right_1.jpg

yajirusi_right_1.jpg

1095 ms

back_img_right1b.gif

back_img_right1b.gif

1166 ms

denko.jpg

denko.jpg

1174 ms

yajirusi_right_2.jpg

yajirusi_right_2.jpg

1063 ms

esd2.jpg

esd2.jpg

1084 ms

shopp.gif

shopp.gif

1114 ms

buty.jpg

buty.jpg

1107 ms

QR.jpg

QR.jpg

1178 ms

back_img_right3.gif

back_img_right3.gif

1176 ms

ga.js

ga.js

33 ms

back_img_right4.gif

back_img_right4.gif

1222 ms

mark_3.gif

mark_3.gif

1242 ms

44_E_JtR7zQ

44_E_JtR7zQ

125 ms

__utm.gif

__utm.gif

17 ms

collect

collect

62 ms

back_img_right5.gif

back_img_right5.gif

1170 ms

yajirusi_right_3.gif

yajirusi_right_3.gif

1143 ms

back_img_right6.gif

back_img_right6.gif

1192 ms

www-embed-player-vflZsBgOl.css

www-embed-player-vflZsBgOl.css

70 ms

www-embed-player.js

www-embed-player.js

92 ms

back_img_sita1.gif

back_img_sita1.gif

1190 ms

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js

38 ms

ad_status.js

ad_status.js

40 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

74 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

83 ms

Accessibility Review

hozan.co.jp accessibility score

87

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

hozan.co.jp best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hozan.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 Hozan.co.jp main page’s claimed encoding is shift_jis. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

hozan.co.jp

Open Graph description is not detected on the main page of HOZAN. 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: