Tools & Wizards About Us
onozo.co.jp screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

onozo.co.jp

ONOMICHI DOCKYARD CO., LTD. ONOMICHI DOCKYARD CO., LTD.

Page Load Speed

5.2 sec in total

First Response

517 ms

Resources Loaded

4.5 sec

Page Rendered

188 ms

onozo.co.jp screenshot

About Website

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

Ship manufacturing, repair and product information Onomichizosen Ltd. , building performance , machinery manufacturing , About Us , will guide the adoption information .

Visit onozo.co.jp

Key Findings

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

onozo.co.jp performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.714

7/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

onozo.co.jp

517 ms

548 ms

wp-emoji-release.min.js

299 ms

style.min.css

623 ms

classic-themes.min.css

499 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 90% of them (43 requests) were addressed to the original Onozo.co.jp, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Onozo.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 434.3 kB (11%)

Content Size

3.9 MB

After Optimization

3.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Onozo.co.jp main page is 3.9 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. 30% of websites need less resources to load. Images take 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 19.5 kB

  • Original 24.6 kB
  • After minification 22.9 kB
  • After compression 5.1 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 19.5 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 113.0 kB

  • Original 3.5 MB
  • After minification 3.3 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. Onozo images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 147.9 kB

  • Original 261.6 kB
  • After minification 252.1 kB
  • After compression 113.7 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 147.9 kB or 57% of the original size.

CSS Optimization

-85%

Potential reduce by 153.8 kB

  • Original 181.2 kB
  • After minification 161.4 kB
  • After compression 27.3 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. Onozo.co.jp needs all CSS files to be minified and compressed as it can save up to 153.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (52%)

Requests Now

46

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

onozo.co.jp

onozo.co.jp

517 ms

548 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

299 ms

style.min.css

style.min.css

623 ms

classic-themes.min.css

classic-themes.min.css

499 ms

styles.css

styles.css

503 ms

style.css

style.css

515 ms

company.css

company.css

524 ms

jquery.remodal.css

jquery.remodal.css

532 ms

main.css

main.css

996 ms

slick.css

slick.css

669 ms

slick-theme.css

slick-theme.css

686 ms

slick-custom.css

slick-custom.css

699 ms

style.css

style.css

710 ms

jquery.min.js

jquery.min.js

17 ms

index.js

index.js

653 ms

index.js

index.js

704 ms

jquery.remodal.min.js

jquery.remodal.min.js

725 ms

TweenMax.min.js

TweenMax.min.js

1088 ms

jquery.superscrollorama.js

jquery.superscrollorama.js

930 ms

jquery.inview.min.js

jquery.inview.min.js

814 ms

slick.min.js

slick.min.js

1037 ms

main.js

main.js

900 ms

slick-active.js

slick-active.js

977 ms

comment-reply.min.js

comment-reply.min.js

1028 ms

css

css

27 ms

slide01.jpg

slide01.jpg

1050 ms

slide02.jpg

slide02.jpg

1292 ms

slide03.jpg

slide03.jpg

749 ms

slide04.jpg

slide04.jpg

1146 ms

unav_completed_en_2024.png

unav_completed_en_2024.png

661 ms

unav_dream_en.jpg

unav_dream_en.jpg

385 ms

unav_story_en.png

unav_story_en.png

561 ms

unav_factory.png

unav_factory.png

736 ms

unav_ceremony.png

unav_ceremony.png

829 ms

unav_recruit.png

unav_recruit.png

912 ms

unav_facebook.png

unav_facebook.png

912 ms

logo_company.png

logo_company.png

997 ms

analytics.js

analytics.js

23 ms

logo_onozo.png

logo_onozo.png

1073 ms

gnav-sfc33ef91ed.png

gnav-sfc33ef91ed.png

1084 ms

ico_recruit.png

ico_recruit.png

1162 ms

collect

collect

12 ms

js

js

63 ms

btn_toTop.png

btn_toTop.png

968 ms

unav_prev.png

unav_prev.png

983 ms

unav_next.png

unav_next.png

1008 ms

ajax-loader.gif

ajax-loader.gif

1059 ms

Accessibility Review

onozo.co.jp accessibility score

93

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-hidden="true"] elements contain focusable descendents

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

onozo.co.jp best practices score

58

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

onozo.co.jp SEO score

86

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

Links do not have descriptive text

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Onozo.co.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Onozo.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

onozo.co.jp

Open Graph data is detected on the main page of Onozo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: