Tools & Wizards About Us
okadora.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

okadora.co.jp

株式会社オカドラ｜乾燥機で未来を造る。｜株式会社オカドラは神奈川県横浜市の縦型間接乾燥機「オカドラサイクロンドライヤー」を 世界で初めて開発しました。

Page Load Speed

4.9 sec in total

First Response

1.2 sec

Resources Loaded

3.2 sec

Page Rendered

421 ms

okadora.co.jp screenshot

About Website

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

株式会社オカドラは神奈川県横浜市にある、生ゴミ・残飯・食品残滓乾燥 、廃死魚・魚残滓乾燥など様々な廃棄物を乾燥させ、リサイクル化や飼料化が行えるスーパーマルチ乾燥「サイクロンドライヤー」や「超高速炭化機」をはじめとした乾燥機技術開発メーカーです。

Visit okadora.co.jp

Key Findings

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

Performance Metrics

okadora.co.jp performance score

0

Network Requests Diagram

okadora.co.jp

1219 ms

system.css

334 ms

bootstrap.css

1223 ms

template.css

1232 ms

bootstrap-responsive.css

705 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 593.3 kB (57%)

Content Size

1.0 MB

After Optimization

455.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Okadora.co.jp main page is 1.0 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. 35% of websites need less resources to load. CSS take 375.3 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 11.5 kB

  • Original 15.3 kB
  • After minification 13.8 kB
  • After compression 3.8 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 11.5 kB or 75% of the original size.

Image Optimization

-9%

Potential reduce by 29.1 kB

  • Original 322.1 kB
  • After minification 293.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. Okadora images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 228.9 kB

  • Original 336.5 kB
  • After minification 289.8 kB
  • After compression 107.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 228.9 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 323.8 kB

  • Original 375.3 kB
  • After minification 302.5 kB
  • After compression 51.5 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. Okadora.co.jp needs all CSS files to be minified and compressed as it can save up to 323.8 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (64%)

Requests Now

47

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

okadora.co.jp

okadora.co.jp

1219 ms

system.css

system.css

334 ms

bootstrap.css

bootstrap.css

1223 ms

template.css

template.css

1232 ms

bootstrap-responsive.css

bootstrap-responsive.css

705 ms

template-responsive.css

template-responsive.css

911 ms

off-canvas.css

off-canvas.css

497 ms

prettify.css

prettify.css

525 ms

megamenu.css

megamenu.css

828 ms

megamenu-responsive.css

megamenu-responsive.css

699 ms

megamenu.css

megamenu.css

1051 ms

megamenu-responsive.css

megamenu-responsive.css

880 ms

animate.css

animate.css

991 ms

mod_jaslideshowlite.css

mod_jaslideshowlite.css

1055 ms

mod_jaslideshowlite-fade.css

mod_jaslideshowlite-fade.css

1091 ms

mootools-core.js

mootools-core.js

1529 ms

core.js

core.js

1239 ms

caption.js

caption.js

1239 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1636 ms

jquery.noconflict.js

jquery.noconflict.js

1392 ms

bootstrap.js

bootstrap.js

1575 ms

off-canvas.js

off-canvas.js

1400 ms

script.js

script.js

1406 ms

menu.js

menu.js

1568 ms

responsive.js

responsive.js

1577 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1585 ms

jquery.inview.min.js

jquery.inview.min.js

1694 ms

script.js

script.js

1742 ms

prettify.js

prettify.js

1748 ms

script.js

script.js

1589 ms

system.css

system.css

1434 ms

getseal

getseal

161 ms

body.png

body.png

179 ms

logo.png

logo.png

179 ms

anniversary_logo.jpg

anniversary_logo.jpg

179 ms

gb_flag.jpg

gb_flag.jpg

185 ms

decor-ltr.png

decor-ltr.png

167 ms

sl-01_840_356.jpg

sl-01_840_356.jpg

355 ms

sl-02_840_356.jpg

sl-02_840_356.jpg

498 ms

sl-03_840_420.jpg

sl-03_840_420.jpg

527 ms

FB-f-Logo__blue_58.png

FB-f-Logo__blue_58.png

350 ms

rfq.jpg

rfq.jpg

353 ms

footer_logo01.png

footer_logo01.png

364 ms

contactus.jpg

contactus.jpg

497 ms

ga.js

ga.js

19 ms

__utm.gif

__utm.gif

21 ms

backtotop.png

backtotop.png

420 ms

slideloading.gif

slideloading.gif

420 ms

SEO Factors

okadora.co.jp SEO score

0

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

okadora.co.jp

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