Tools & Wizards About Us
ozak.co.jp screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

ozak.co.jp

オザック精工 | 搬送装置、リニアガイド、メンテナンスフリーベアリング、リニアローラースライダーなどの研究開発・製造｜オザック精工株式会社

Page Load Speed

8 sec in total

First Response

545 ms

Resources Loaded

6.9 sec

Page Rendered

558 ms

ozak.co.jp screenshot

About Website

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

リニアベアリングのプロフェッショナル　オザック精工オザック精工（株）は、日本で最も古くからリニアベアリング（リニアブッシュ）を研究開発し、製造してまいりましたが、その実績を生かし、リニアベアリングのシステムメーカーとして発展してまいりました

Visit ozak.co.jp

Key Findings

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

Performance Metrics

ozak.co.jp performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value23.7 s

0/100

25%

SI (Speed Index)

Value14.8 s

1/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.713

7/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

ozak.co.jp

545 ms

www.ozak.co.jp

1660 ms

js

57 ms

js

108 ms

style.css

349 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 87% of them (69 requests) were addressed to the original Ozak.co.jp, 4% (3 requests) were made to Googletagmanager.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Ozak.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 683.4 kB (16%)

Content Size

4.3 MB

After Optimization

3.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 214.1 kB

  • Original 244.0 kB
  • After minification 241.2 kB
  • After compression 29.9 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 214.1 kB or 88% of the original size.

Image Optimization

-10%

Potential reduce by 358.1 kB

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

JavaScript Optimization

-4%

Potential reduce by 13.4 kB

  • Original 328.0 kB
  • After minification 327.7 kB
  • After compression 314.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. This website has mostly compressed JavaScripts.

CSS Optimization

-55%

Potential reduce by 97.9 kB

  • Original 179.5 kB
  • After minification 179.2 kB
  • After compression 81.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. Ozak.co.jp needs all CSS files to be minified and compressed as it can save up to 97.9 kB or 55% of the original size.

Requests Breakdown

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

Requests Now

75

After Optimization

36

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ozak.co.jp

ozak.co.jp

545 ms

www.ozak.co.jp

www.ozak.co.jp

1660 ms

js

js

57 ms

js

js

108 ms

style.css

style.css

349 ms

keyframes.css

keyframes.css

521 ms

font-awesome.min.css

font-awesome.min.css

535 ms

style.css

style.css

534 ms

baguetteBox.min.css

baguetteBox.min.css

562 ms

style.css

style.css

565 ms

style.css

style.css

566 ms

keyframes.css

keyframes.css

685 ms

style.min.css

style.min.css

706 ms

styles.css

styles.css

705 ms

ivory-search.min.css

ivory-search.min.css

743 ms

pum-site.min.css

pum-site.min.css

745 ms

css

css

67 ms

jquery.min.js

jquery.min.js

42 ms

jquery-migrate.min.js

jquery-migrate.min.js

69 ms

js

js

81 ms

kitchen.juicer.cc

kitchen.juicer.cc

601 ms

owl.carousel.css

owl.carousel.css

795 ms

sa-owl-theme.css

sa-owl-theme.css

853 ms

animate.min.css

animate.min.css

879 ms

shortcodes.css

shortcodes.css

880 ms

icons.css

icons.css

925 ms

baguetteBox.min.js

baguetteBox.min.js

943 ms

comment-reply.min.js

comment-reply.min.js

946 ms

javascript.js

javascript.js

1023 ms

javascript.js

javascript.js

1054 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1055 ms

wp-polyfill.min.js

wp-polyfill.min.js

1111 ms

index.js

index.js

1116 ms

core.min.js

core.min.js

1132 ms

site.min.js

site.min.js

1195 ms

mobile-detect.min.js

mobile-detect.min.js

1406 ms

api.js

api.js

62 ms

index.js

index.js

1230 ms

ivory-search.min.js

ivory-search.min.js

1296 ms

owl.carousel.min.js

owl.carousel.min.js

1303 ms

jquery.mousewheel.min.js

jquery.mousewheel.min.js

1320 ms

clipboard.min.js

clipboard.min.js

59 ms

logo3-1.png

logo3-1.png

1005 ms

vrtopimg-1024x522.png

vrtopimg-1024x522.png

3160 ms

sl02.png

sl02.png

2058 ms

lsinew.jpg

lsinew.jpg

1137 ms

iot.jpg

iot.jpg

1006 ms

OB.jpg

OB.jpg

1090 ms

lfw-c-726x1024-1.jpg

lfw-c-726x1024-1.jpg

1534 ms

BLSL4080-leaflet2.jpg

BLSL4080-leaflet2.jpg

1537 ms

tmrh.png

tmrh.png

1943 ms

umf.jpg

umf.jpg

1516 ms

wds.jpg

wds.jpg

1710 ms

fsh.jpg

fsh.jpg

1888 ms

phlsi.jpg

phlsi.jpg

1715 ms

hst-mod.jpg

hst-mod.jpg

1902 ms

mfb.jpg

mfb.jpg

1894 ms

ppsamrleaflet.jpg

ppsamrleaflet.jpg

2384 ms

noimg01.png

noimg01.png

2020 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2005 ms

hyoushi20231026.jpg

hyoushi20231026.jpg

2165 ms

M-SDGs-2.jpg

M-SDGs-2.jpg

2497 ms

c01-210x210.jpg

c01-210x210.jpg

2071 ms

c02-210x210.jpg

c02-210x210.jpg

2103 ms

forkawesome-webfont.woff

forkawesome-webfont.woff

2253 ms

c04-210x210.jpg

c04-210x210.jpg

2188 ms

c05-210x210.jpg

c05-210x210.jpg

2185 ms

c07-210x210.jpg

c07-210x210.jpg

2297 ms

c08-210x210.jpg

c08-210x210.jpg

2260 ms

c09-210x210.jpg

c09-210x210.jpg

2272 ms

c10-210x210.jpg

c10-210x210.jpg

2295 ms

c11-210x210.jpg

c11-210x210.jpg

2328 ms

c12-210x210.jpg

c12-210x210.jpg

2322 ms

no-amp-logo.png

no-amp-logo.png

2268 ms

ctldl.jpg

ctldl.jpg

2426 ms

onlineicon3.png

onlineicon3.png

2299 ms

recaptcha__en.js

recaptcha__en.js

103 ms

icon_pdf.gif

icon_pdf.gif

2206 ms

style-bubbles.png

style-bubbles.png

2222 ms

Accessibility Review

ozak.co.jp accessibility score

88

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

ozak.co.jp SEO score

90

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

ozak.co.jp

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