Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

hirochi.co.jp

ヒロチー商事 バイク部品、バイク関連用品の通販 |ヒロチー商事

Page Load Speed

5.2 sec in total

First Response

708 ms

Resources Loaded

4.2 sec

Page Rendered

282 ms

hirochi.co.jp screenshot

About Website

Visit hirochi.co.jp now to see the best up-to-date Hirochi content for Japan and also check out these interesting facts you probably never knew about hirochi.co.jp

バイク部品・バイク用品・純正部品の取扱点数160万点以上!厳選されたオートバイ部品関連商品を販売!国内・海外の有名メーカーの入手困難なパーツを豊富に取り揃えています!

Visit hirochi.co.jp

Key Findings

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

Performance Metrics

hirochi.co.jp performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,820 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value1.011

2/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

www.hirochi.com

708 ms

96590c5debe57e47488f1df0f7f94d67.min.css

15 ms

styles-l.min.css

10 ms

bike_icon_white.svg

52 ms

coins.svg

51 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hirochi.co.jp, 3% (2 requests) were made to Googletagmanager.com and 2% (1 request) were made to Apay-up-banner.com. The less responsive or slowest element that took the longest time to load (2.9 sec) relates to the external source Hirochi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 371.7 kB (2%)

Content Size

15.3 MB

After Optimization

15.0 MB

In fact, the total size of Hirochi.co.jp main page is 15.3 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. Only a small number of websites need less resources to load. Images take 15.1 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 73.0 kB

  • Original 89.5 kB
  • After minification 87.5 kB
  • After compression 16.6 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 73.0 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 188.8 kB

  • Original 15.1 MB
  • After minification 14.9 MB

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. Hirochi images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 14.6 kB

  • Original 21.4 kB
  • After minification 16.0 kB
  • After compression 6.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 14.6 kB or 68% of the original size.

CSS Optimization

-80%

Potential reduce by 95.3 kB

  • Original 119.4 kB
  • After minification 24.2 kB
  • After compression 24.1 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. Hirochi.co.jp needs all CSS files to be minified and compressed as it can save up to 95.3 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (8%)

Requests Now

63

After Optimization

58

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

Accessibility Review

hirochi.co.jp accessibility score

74

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

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

High

[role]s are not contained by their required parent element

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Image elements do not have [alt] attributes

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

hirochi.co.jp best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

hirochi.co.jp SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hirochi.co.jp 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 Hirochi.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 Hirochi. 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: