Tools & Wizards About Us
rionet.jp screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

rionet.jp

補聴器のことなら、リオネット補聴器 ｜リオネット補聴器 ｜国産メーカーリオンの公式サイト

Page Load Speed

8.1 sec in total

First Response

540 ms

Resources Loaded

6.4 sec

Page Rendered

1.1 sec

rionet.jp screenshot

About Website

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

リオネット補聴器は1948年に国産初の補聴器を開発・発売して以来、先進の技術とサービスでトップランナーとして歩んできました。これから先も使う人の事を第一に考え、社会に、地球に優しい補聴器を作り続けます。

Visit rionet.jp

Key Findings

We analyzed Rionet.jp page load time and found that the first response time was 540 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

rionet.jp performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

8/100

10%

LCP (Largest Contentful Paint)

Value27.4 s

0/100

25%

SI (Speed Index)

Value17.2 s

0/100

10%

TBT (Total Blocking Time)

Value2,150 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.553

13/100

15%

TTI (Time to Interactive)

Value27.6 s

0/100

10%

Network Requests Diagram

rionet.jp

540 ms

www.rionet.jp

1150 ms

gtm.js

74 ms

style.css

164 ms

responsive.css

324 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 95% of them (106 requests) were addressed to the original Rionet.jp, 1% (1 request) were made to Googletagmanager.com and 1% (1 request) were made to Nk-media.org. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Rionet.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.6 kB (5%)

Content Size

3.7 MB

After Optimization

3.5 MB

  • HTML
  • Images

In fact, the total size of Rionet.jp main page is 3.7 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.6 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 88.8 kB

  • Original 102.7 kB
  • After minification 85.6 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 17.1 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 88.8 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 102.8 kB

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

Requests Breakdown

Number of requests can be reduced by 45 (42%)

Requests Now

107

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rionet.jp

rionet.jp

540 ms

www.rionet.jp

www.rionet.jp

1150 ms

gtm.js

gtm.js

74 ms

style.css

style.css

164 ms

responsive.css

responsive.css

324 ms

arrow-s.png

arrow-s.png

877 ms

css

css

38 ms

logo_new.svg

logo_new.svg

528 ms

tel.svg

tel.svg

530 ms

0120-2933-76.png

0120-2933-76.png

530 ms

headerLogo-facebook.svg

headerLogo-facebook.svg

531 ms

headerLogo-x_b.png

headerLogo-x_b.png

532 ms

headerLogo-instagram.svg

headerLogo-instagram.svg

533 ms

headerLogo-line.svg

headerLogo-line.svg

585 ms

raku_icon_b.png

raku_icon_b.png

722 ms

search.svg

search.svg

586 ms

hero-1-1.jpg

hero-1-1.jpg

1171 ms

sp-hero-1-1.jpg

sp-hero-1-1.jpg

1025 ms

top_rionet2b.jpg

top_rionet2b.jpg

1346 ms

top_rionet2_sp.jpg

top_rionet2_sp.jpg

867 ms

hero-3-2.jpg

hero-3-2.jpg

1012 ms

sp-hero-3-1.jpg

sp-hero-3-1.jpg

1153 ms

movie_rionet2_banner.png

movie_rionet2_banner.png

1159 ms

304_135_shop.jpg

304_135_shop.jpg

1159 ms

hba2cc_banner.png

hba2cc_banner.png

1175 ms

support_banner.png

support_banner.png

1299 ms

rionet_brand_message_banner.png

rionet_brand_message_banner.png

1307 ms

side-pc-search2_02.png

side-pc-search2_02.png

1306 ms

side-pc-favorite_01.png

side-pc-favorite_01.png

1319 ms

side-sp-search9.png

side-sp-search9.png

1322 ms

side-sp-favorite1.png

side-sp-favorite1.png

1444 ms

about.jpg

about.jpg

1454 ms

serviceIcon-1.svg

serviceIcon-1.svg

1452 ms

arrow-blue.svg

arrow-blue.svg

1465 ms

serviceIcon-2.svg

serviceIcon-2.svg

1470 ms

serviceIcon-3.svg

serviceIcon-3.svg

1492 ms

serviceIcon-4.svg

serviceIcon-4.svg

1588 ms

serviceIcon-5.svg

serviceIcon-5.svg

1596 ms

top_knowledge_ph@2x.jpg

top_knowledge_ph@2x.jpg

1599 ms

top_choice_ph@2x.jpg

top_choice_ph@2x.jpg

1614 ms

jquery.cookie.min.js

jquery.cookie.min.js

24 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

1630 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

1493 ms

jquery.easing.min.js

jquery.easing.min.js

1218 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

1228 ms

owl.carousel.min.js

owl.carousel.min.js

1230 ms

venobox.min.js

venobox.min.js

1243 ms

aos.js

aos.js

1262 ms

main.js

main.js

1282 ms

emergency.js

emergency.js

1377 ms

font

font

17 ms

localactions.js

localactions.js

1338 ms

NotoSansCJKjp-Medium2.woff

NotoSansCJKjp-Medium2.woff

1752 ms

NotoSansMonoCJKjp-Regular2.woff

NotoSansMonoCJKjp-Regular2.woff

1491 ms

top_family_ph@2x.jpg

top_family_ph@2x.jpg

1078 ms

top_kids_ph@2x.jpg

top_kids_ph@2x.jpg

952 ms

doItem-1.svg

doItem-1.svg

1018 ms

doItem-2.svg

doItem-2.svg

906 ms

doItem-3.svg

doItem-3.svg

934 ms

doItem-4.svg

doItem-4.svg

953 ms

doItem-5.svg

doItem-5.svg

1017 ms

doItem-6.svg

doItem-6.svg

1029 ms

shapeItem-1.png

shapeItem-1.png

980 ms

shapeItem-2.png

shapeItem-2.png

975 ms

shapeItem-3-1.png

shapeItem-3-1.png

1027 ms

shapeItem-4.png

shapeItem-4.png

1035 ms

hba8.jpg

hba8.jpg

1068 ms

hic7.png

hic7.png

1046 ms

hic7_1.png

hic7_1.png

964 ms

product-item-1.jpg

product-item-1.jpg

1025 ms

product-item-2.jpg

product-item-2.jpg

1028 ms

product-item-3.jpg

product-item-3.jpg

1029 ms

product-item-5.jpg

product-item-5.jpg

1035 ms

product-item-6.jpg

product-item-6.jpg

1042 ms

Q.png

Q.png

966 ms

A.png

A.png

1025 ms

top-ferture.svg

top-ferture.svg

1028 ms

top-support.svg

top-support.svg

1026 ms

myrionet_03.png

myrionet_03.png

1029 ms

myrionet-sp_03.png

myrionet-sp_03.png

1316 ms

304_135_factory.jpg

304_135_factory.jpg

962 ms

movie02_banner.png

movie02_banner.png

1016 ms

logo-white_new.svg

logo-white_new.svg

1016 ms

logo-facebook.svg

logo-facebook.svg

1015 ms

logo-x.svg

logo-x.svg

1028 ms

logo-instagram.svg

logo-instagram.svg

1041 ms

logo-line.svg

logo-line.svg

997 ms

raku_icon.png

raku_icon.png

997 ms

logo-white2.svg

logo-white2.svg

989 ms

links-pink.svg

links-pink.svg

1007 ms

backR.svg

backR.svg

960 ms

backR-inversion.svg

backR-inversion.svg

1004 ms

check.svg

check.svg

975 ms

bg_storesearch.png

bg_storesearch.png

968 ms

pages_blue.svg

pages_blue.svg

928 ms

pages.svg

pages.svg

921 ms

triangle.svg

triangle.svg

926 ms

links-blue.svg

links-blue.svg

927 ms

footer-list.svg

footer-list.svg

932 ms

plus-footer.svg

plus-footer.svg

893 ms

barger.svg

barger.svg

912 ms

plus.svg

plus.svg

885 ms

header-list.svg

header-list.svg

909 ms

scroll.svg

scroll.svg

959 ms

bootstrap.min.css

bootstrap.min.css

163 ms

icofont.min.css

icofont.min.css

166 ms

boxicons.min.css

boxicons.min.css

162 ms

animate.min.css

animate.min.css

160 ms

owl.carousel.min.css

owl.carousel.min.css

158 ms

venobox.css

venobox.css

162 ms

aos.css

aos.css

161 ms

Accessibility Review

rionet.jp accessibility score

63

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

Image elements do not have [alt] attributes

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

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

rionet.jp best practices score

75

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

rionet.jp SEO score

73

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

High

Image elements do not have [alt] attributes

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

rionet.jp

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