Tools & Wizards About Us
hanway.jp screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

hanway.jp

傘・日傘・レイングッズ専門店　HANWAY（ハンウェイ）

Page Load Speed

14.3 sec in total

First Response

715 ms

Resources Loaded

13.4 sec

Page Rendered

137 ms

hanway.jp screenshot

About Website

Click here to check amazing HANWAY content for Japan. Otherwise, check out these important facts you probably never knew about hanway.jp

新丸ビルにある傘・日傘・オーダーメイド傘・レイングッズの専門店。商品紹介・オーダーメイド・修理について・お手入れ方法など

Visit hanway.jp

Key Findings

We analyzed Hanway.jp page load time and found that the first response time was 715 ms and then it took 13.5 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

hanway.jp performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value36.6 s

0/100

25%

SI (Speed Index)

Value21.9 s

0/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.248

50/100

15%

TTI (Time to Interactive)

Value25.1 s

0/100

10%

Network Requests Diagram

hanway.jp

715 ms

www.hanway.jp

1030 ms

layout.css

564 ms

toppage.css

548 ms

xml_func.js

557 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 93% of them (27 requests) were addressed to the original Hanway.jp, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (10.7 sec) belongs to the original domain Hanway.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.7 kB (24%)

Content Size

281.7 kB

After Optimization

212.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hanway.jp main page is 281.7 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. Only 10% of websites need less resources to load. Images take 205.0 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 3.2 kB

  • Original 5.0 kB
  • After minification 4.7 kB
  • After compression 1.8 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 3.2 kB or 64% of the original size.

Image Optimization

-11%

Potential reduce by 21.7 kB

  • Original 205.0 kB
  • After minification 183.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. Obviously, HANWAY needs image optimization as it can save up to 21.7 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-61%

Potential reduce by 40.7 kB

  • Original 67.1 kB
  • After minification 54.0 kB
  • After compression 26.4 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 40.7 kB or 61% of the original size.

CSS Optimization

-68%

Potential reduce by 3.1 kB

  • Original 4.6 kB
  • After minification 3.5 kB
  • After compression 1.5 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. Hanway.jp needs all CSS files to be minified and compressed as it can save up to 3.1 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (56%)

Requests Now

27

After Optimization

12

  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HANWAY. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

hanway.jp

hanway.jp

715 ms

www.hanway.jp

www.hanway.jp

1030 ms

layout.css

layout.css

564 ms

toppage.css

toppage.css

548 ms

xml_func.js

xml_func.js

557 ms

prototype.js

prototype.js

935 ms

hanway_lib.js

hanway_lib.js

571 ms

base.css

base.css

176 ms

menu.css

menu.css

184 ms

head_title.gif

head_title.gif

505 ms

menu01.gif

menu01.gif

506 ms

menu02.gif

menu02.gif

518 ms

menu03.gif

menu03.gif

518 ms

menu04.gif

menu04.gif

520 ms

menu05.gif

menu05.gif

522 ms

menu06.gif

menu06.gif

5324 ms

menu07.gif

menu07.gif

5310 ms

menu08.gif

menu08.gif

5311 ms

mainb_2015aw01.jpg

mainb_2015aw01.jpg

6562 ms

banner_blog.jpg

banner_blog.jpg

5819 ms

banner_onlineshop.jpg

banner_onlineshop.jpg

5869 ms

banner_shop.jpg

banner_shop.jpg

10709 ms

sns_fb.gif

sns_fb.gif

10022 ms

sns_twitter.gif

sns_twitter.gif

10047 ms

sns_insta.gif

sns_insta.gif

10045 ms

submenu_privacy.gif

submenu_privacy.gif

10033 ms

copyright.gif

copyright.gif

10057 ms

ga.js

ga.js

6 ms

__utm.gif

__utm.gif

13 ms

Accessibility Review

hanway.jp accessibility score

90

Accessibility Issues

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

Links do not have a discernible name

Best Practices

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

hanway.jp SEO score

100

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

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

hanway.jp

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