Tools & Wizards About Us
odi.jp screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

odi.jp

ODI WEB 株式会社オーディーアイ

Page Load Speed

4 sec in total

First Response

732 ms

Resources Loaded

3.1 sec

Page Rendered

190 ms

odi.jp screenshot

About Website

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

odi webのコンテンツページ。米国、ダイアナインダストリーズ社の環境に安全で、高性能な洗浄液シリーズのEP-680、超濃縮型JSB-1を紹介 日本を中心にアジア各国へはオーディーアイがお届けします

Visit odi.jp

Key Findings

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

Performance Metrics

odi.jp performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

51/100

10%

LCP (Largest Contentful Paint)

Value4.5 s

37/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

odi.jp

732 ms

topart.jpg

704 ms

top9.jpg

908 ms

top13.jpg

884 ms

top10.jpg

1069 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 102.3 kB (17%)

Content Size

608.8 kB

After Optimization

506.6 kB

  • HTML
  • Images

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

HTML Optimization

-76%

Potential reduce by 7.0 kB

  • Original 9.2 kB
  • After minification 8.6 kB
  • After compression 2.2 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 7.0 kB or 76% of the original size.

Image Optimization

-16%

Potential reduce by 95.3 kB

  • Original 599.6 kB
  • After minification 504.4 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, ODI needs image optimization as it can save up to 95.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

22

After Optimization

22

  • Images

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ODI. According to our analytics all requests are already optimized.

Network Requests Diagram

odi.jp

odi.jp

732 ms

topart.jpg

topart.jpg

704 ms

top9.jpg

top9.jpg

908 ms

top13.jpg

top13.jpg

884 ms

top10.jpg

top10.jpg

1069 ms

top12.jpg

top12.jpg

1058 ms

top11.jpg

top11.jpg

950 ms

top6.jpg

top6.jpg

708 ms

top7.jpg

top7.jpg

1067 ms

top5.jpg

top5.jpg

893 ms

top8.jpg

top8.jpg

1279 ms

top1.jpg

top1.jpg

1237 ms

top2.jpg

top2.jpg

1244 ms

top3.jpg

top3.jpg

1253 ms

top4.jpg

top4.jpg

1141 ms

UJ.GIF

UJ.GIF

1242 ms

engver.gif

engver.gif

1327 ms

2016top1.jpg

2016top1.jpg

2322 ms

sitemap.gif

sitemap.gif

1418 ms

odideep3D.JPG

odideep3D.JPG

1422 ms

facebook.png

facebook.png

1428 ms

twitter2.png

twitter2.png

1460 ms

insta.png

insta.png

1511 ms

Accessibility Review

odi.jp accessibility score

57

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

odi.jp best practices score

58

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

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

odi.jp SEO score

92

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

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

odi.jp

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