Tools & Wizards About Us
hayabusa.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

hayabusa.com

株式会社ハヤブサドットコム

Page Load Speed

5.8 sec in total

First Response

900 ms

Resources Loaded

4.7 sec

Page Rendered

117 ms

hayabusa.com screenshot

About Website

Visit hayabusa.com now to see the best up-to-date Hayabusa content and also check out these interesting facts you probably never knew about hayabusa.com

ハヤブサグループは、1960年に「隼電機商会」として創業し、1973年に「ハヤブサ電装株式会社」と社名を変更、2000年には現在の社名に変更した「株式会社ハヤブサドットコム」を中核会社として、自動車電装品事業を分社独立させ、2022年に新規事業展開の一環として、「株式会社ハヤブサ総研」を設立し、グループ事業を展開しています。創業以来、永きにわたり事業を続けることができましたのは、お客様をはじめとす...

Visit hayabusa.com

Key Findings

We analyzed Hayabusa.com page load time and found that the first response time was 900 ms and then it took 4.9 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

hayabusa.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0.209

59/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

hayabusa.com

900 ms

hayabusa.css

355 ms

home_b.gif

179 ms

about_b2.gif

177 ms

gyomu_b3.gif

432 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that all of those requests were addressed to Hayabusa.com and no external sources were called. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Hayabusa.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.8 kB (10%)

Content Size

288.6 kB

After Optimization

259.9 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Hayabusa.com main page is 288.6 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. 15% of websites need less resources to load. Images take 263.5 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 20.3 kB

  • Original 23.9 kB
  • After minification 11.8 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 12.0 kB, which is 50% 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 20.3 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 7.5 kB

  • Original 263.5 kB
  • After minification 256.0 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. Hayabusa images are well optimized though.

CSS Optimization

-79%

Potential reduce by 998 B

  • Original 1.3 kB
  • After minification 1.1 kB
  • After compression 265 B

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. Hayabusa.com needs all CSS files to be minified and compressed as it can save up to 998 B or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (29%)

Requests Now

34

After Optimization

24

  • Images
  • CSS

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

Network Requests Diagram

hayabusa.com

hayabusa.com

900 ms

hayabusa.css

hayabusa.css

355 ms

home_b.gif

home_b.gif

179 ms

about_b2.gif

about_b2.gif

177 ms

gyomu_b3.gif

gyomu_b3.gif

432 ms

recruit_b4.gif

recruit_b4.gif

1441 ms

contact_b5.gif

contact_b5.gif

352 ms

bg.gif

bg.gif

358 ms

wireless_japan.jpg

wireless_japan.jpg

3172 ms

hayabusa.png

hayabusa.png

2186 ms

grey_frame_1.gif

grey_frame_1.gif

527 ms

docomo.gif

docomo.gif

535 ms

pointer.gif

pointer.gif

593 ms

what17.jpg

what17.jpg

704 ms

denso.gif

denso.gif

714 ms

diag-station_icon.gif

diag-station_icon.gif

757 ms

car-security.gif

car-security.gif

879 ms

privacy.gif

privacy.gif

891 ms

whats_new.gif

whats_new.gif

918 ms

what26.jpg

what26.jpg

1054 ms

line_parts.gif

line_parts.gif

1069 ms

pref_tochigi_bannar_m1.gif

pref_tochigi_bannar_m1.gif

1080 ms

about_b2_on.gif

about_b2_on.gif

180 ms

gyomu_b3_on.gif

gyomu_b3_on.gif

178 ms

recruit_b4_on.gif

recruit_b4_on.gif

180 ms

contact_b5_on.gif

contact_b5_on.gif

187 ms

beone_on.gif

beone_on.gif

165 ms

au_on.gif

au_on.gif

185 ms

docomo_on.gif

docomo_on.gif

329 ms

softbank_on.gif

softbank_on.gif

355 ms

denso_on.gif

denso_on.gif

358 ms

community_on.gif

community_on.gif

356 ms

tvcm_on.gif

tvcm_on.gif

369 ms

hayabusa_on.png

hayabusa_on.png

374 ms

wireless_japan_on.jpg

wireless_japan_on.jpg

652 ms

Accessibility Review

hayabusa.com accessibility score

94

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

hayabusa.com best practices score

83

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

Page has valid source maps

SEO Factors

hayabusa.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 doesn't use 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 Hayabusa.com 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 Hayabusa.com 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

hayabusa.com

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