Tools & Wizards About Us
rion.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

rion.co.jp

リオン株式会社

Page Load Speed

4.8 sec in total

First Response

742 ms

Resources Loaded

3.8 sec

Page Rendered

212 ms

rion.co.jp screenshot

About Website

Click here to check amazing Rion content for Japan. Otherwise, check out these important facts you probably never knew about rion.co.jp

音のテクノロジーで世界を変えるーリオネット補聴器,聴能設備機器,医用検査機器,音響・振動計測器,微粒子計測器など、さまざまな分野で暮らしとビジネスを支えている、リオン株式会社のウェブサイトです。

Visit rion.co.jp

Key Findings

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

Performance Metrics

rion.co.jp performance score

0

Network Requests Diagram

rion.co.jp

742 ms

common.css

536 ms

top.css

365 ms

analytics.js

370 ms

jquery-1.10.2.min.js

959 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 91% of them (73 requests) were addressed to the original Rion.co.jp, 5% (4 requests) were made to Google-analytics.com and 3% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Rion.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 179.4 kB (19%)

Content Size

943.4 kB

After Optimization

763.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 16.0 kB

  • Original 21.9 kB
  • After minification 21.0 kB
  • After compression 5.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 16.0 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 23.7 kB

  • Original 697.8 kB
  • After minification 674.1 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. Rion images are well optimized though.

JavaScript Optimization

-58%

Potential reduce by 105.4 kB

  • Original 181.1 kB
  • After minification 176.0 kB
  • After compression 75.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 105.4 kB or 58% of the original size.

CSS Optimization

-81%

Potential reduce by 34.4 kB

  • Original 42.7 kB
  • After minification 32.5 kB
  • After compression 8.2 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. Rion.co.jp needs all CSS files to be minified and compressed as it can save up to 34.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (14%)

Requests Now

77

After Optimization

66

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rion.co.jp

rion.co.jp

742 ms

common.css

common.css

536 ms

top.css

top.css

365 ms

analytics.js

analytics.js

370 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

959 ms

smoothScroll.js

smoothScroll.js

355 ms

jquery.cookie.js

jquery.cookie.js

396 ms

jquery.biggerlink.js

jquery.biggerlink.js

395 ms

common.js

common.js

394 ms

top.js

top.js

535 ms

organictabs.jquery.js

organictabs.jquery.js

545 ms

xml_display.js

xml_display.js

575 ms

ga.js

ga.js

59 ms

bg_body.gif

bg_body.gif

416 ms

logo_rion.gif

logo_rion.gif

211 ms

gnav_01_cur.gif

gnav_01_cur.gif

338 ms

gnav_02.gif

gnav_02.gif

350 ms

gnav_03.gif

gnav_03.gif

383 ms

gnav_04.gif

gnav_04.gif

403 ms

gnav_05.gif

gnav_05.gif

513 ms

gnav_06.gif

gnav_06.gif

525 ms

gnav_07.gif

gnav_07.gif

579 ms

gnav_08.gif

gnav_08.gif

621 ms

recommend01.jpg

recommend01.jpg

972 ms

recommend02.jpg

recommend02.jpg

1060 ms

recommend03.jpg

recommend03.jpg

879 ms

recommend04.jpg

recommend04.jpg

1313 ms

recommend05.jpg

recommend05.jpg

958 ms

img_pickup_01.jpg

img_pickup_01.jpg

981 ms

icon_pickup.png

icon_pickup.png

1062 ms

img_pickup_02.jpg

img_pickup_02.jpg

1157 ms

title_products.gif

title_products.gif

1160 ms

nav_products01.jpg

nav_products01.jpg

1389 ms

nav_products02.jpg

nav_products02.jpg

1238 ms

nav_products03.jpg

nav_products03.jpg

1245 ms

nav_products04.jpg

nav_products04.jpg

1345 ms

nav_products05.jpg

nav_products05.jpg

1343 ms

infotab01_01_cur.gif

infotab01_01_cur.gif

1415 ms

infotab01_02.gif

infotab01_02.gif

1421 ms

infotab01_03.gif

infotab01_03.gif

1492 ms

infotab01_04.gif

infotab01_04.gif

1525 ms

gtm.js

gtm.js

75 ms

title_event.gif

title_event.gif

1519 ms

bnr_navi.jpg

bnr_navi.jpg

1585 ms

bnr_shop.gif

bnr_shop.gif

1587 ms

bnr_important_218.gif

bnr_important_218.gif

1565 ms

__utm.gif

__utm.gif

12 ms

collect

collect

59 ms

analytics.js

analytics.js

22 ms

collect

collect

12 ms

collect

collect

20 ms

bnr_notification.gif

bnr_notification.gif

1520 ms

bnr_kobayasi-riken.jpg

bnr_kobayasi-riken.jpg

1554 ms

bnr_majes.jpg

bnr_majes.jpg

1531 ms

bnr_support.jpg

bnr_support.jpg

1587 ms

bnr_tvcm.jpg

bnr_tvcm.jpg

1449 ms

copyright.gif

copyright.gif

1442 ms

arrow01_blue.png

arrow01_blue.png

1480 ms

bg_search.gif

bg_search.gif

1505 ms

fontsize.png

fontsize.png

1505 ms

bg_fontsize.png

bg_fontsize.png

1450 ms

bg_globalnav.gif

bg_globalnav.gif

1442 ms

bg_container_02.png

bg_container_02.png

1418 ms

news.xml

news.xml

1427 ms

products.xml

products.xml

1474 ms

ir.xml

ir.xml

1223 ms

info.xml

info.xml

1182 ms

info_importance.xml

info_importance.xml

1174 ms

arrow02_lblue.png

arrow02_lblue.png

1206 ms

icon_blank_gray.gif

icon_blank_gray.gif

1169 ms

pagetop.png

pagetop.png

1213 ms

arrow01_white.png

arrow01_white.png

1132 ms

recommend_thumb.png

recommend_thumb.png

1157 ms

icon_release.gif

icon_release.gif

262 ms

icon_news.gif

icon_news.gif

325 ms

icon_pdf.gif

icon_pdf.gif

354 ms

icon_communication.gif

icon_communication.gif

361 ms

icon_sound.gif

icon_sound.gif

386 ms

icon_particle.gif

icon_particle.gif

394 ms

print.css

print.css

182 ms

SEO Factors

rion.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rion.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 Rion.co.jp 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

rion.co.jp

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