12.2 sec in total
527 ms
11.4 sec
254 ms
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.jpWe analyzed Rionet.jp page load time and found that the first response time was 527 ms and then it took 11.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rionet.jp performance score
name
value
score
weighting
Value5.1 s
9/100
10%
Value7.6 s
3/100
25%
Value13.2 s
2/100
10%
Value3,550 ms
1/100
30%
Value0.392
26/100
15%
Value23.5 s
1/100
10%
527 ms
903 ms
352 ms
350 ms
357 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 90% of them (92 requests) were addressed to the original Rionet.jp, 3% (3 requests) were made to Rs-j.adtdp.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.3 sec) belongs to the original domain Rionet.jp.
Page size can be reduced by 240.8 kB (20%)
1.2 MB
945.5 kB
In fact, the total size of Rionet.jp main page is 1.2 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. 25% of websites need less resources to load. Images take 882.9 kB which makes up the majority of the site volume.
Potential reduce by 20.0 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 3.9 kB, which is 15% 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 20.0 kB or 76% of the original size.
Potential reduce by 19.7 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. Rionet images are well optimized though.
Potential reduce by 133.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 133.6 kB or 66% of the original size.
Potential reduce by 67.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. Rionet.jp needs all CSS files to be minified and compressed as it can save up to 67.5 kB or 89% of the original size.
Number of requests can be reduced by 47 (47%)
99
52
The browser has sent 99 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 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
rionet.jp
527 ms
www.rionet.jp
903 ms
common.css
352 ms
library.js
350 ms
siteTop.js
357 ms
smp.js
381 ms
fontsize.js
381 ms
cssimporter.css
370 ms
u.js
642 ms
base.css
992 ms
thickbox.css
348 ms
jquery-1.7.1.min.js
1258 ms
thickbox.js
540 ms
globalNavigation.js
362 ms
scroll.js
362 ms
rollover.js
369 ms
localNavConnect.js
379 ms
ga.js
27 ms
convert.js
581 ms
logo_rionet.gif
350 ms
logo_rion.gif
357 ms
img01_off.gif
371 ms
img02_off.gif
382 ms
img03_off.gif
572 ms
img04_off.gif
393 ms
img05_off.gif
887 ms
img06_off.gif
876 ms
img07_off.gif
884 ms
img08_off.gif
741 ms
img01.jpg
1346 ms
btn01.gif
940 ms
btn02.gif
1090 ms
img01.jpg
1771 ms
btn01.gif
1244 ms
btn02.gif
1270 ms
img01.jpg
1904 ms
btn01.gif
1425 ms
btn02.gif
1615 ms
heading-lv201.gif
1615 ms
topics.gif
1716 ms
banner_catalog_top_btn.gif
2100 ms
heading-lv202.png
1961 ms
product_year_01.png
1983 ms
product_year_02.png
2084 ms
product_year_03.png
2130 ms
product_year_04.png
2263 ms
product_year_05.png
2309 ms
banner_catalog_download.jpg
2692 ms
title.gif
2446 ms
022.jpg
2846 ms
015.jpg
2870 ms
003.jpg
3021 ms
005.jpg
2862 ms
title02.gif
2805 ms
021.jpg
3544 ms
d.js
65 ms
__utm.gif
12 ms
collect
69 ms
cc.html
28 ms
cc.js
29 ms
398 ms
023.jpg
3179 ms
019.jpg
3167 ms
011.jpg
3392 ms
01.png
2863 ms
02.png
3004 ms
03.png
3054 ms
pv_beacon.gif
379 ms
04.png
3002 ms
05.png
3000 ms
06.png
3018 ms
07.png
3048 ms
08.png
3043 ms
logo.gif
3024 ms
04.png
2877 ms
bg01.gif
2954 ms
img09.jpg
4272 ms
bg01.gif
2887 ms
bg01.gif
2704 ms
bg02.gif
2867 ms
01.png
2774 ms
pdf.png
2800 ms
bg02.png
2768 ms
product_bg01.png
3226 ms
product_bg02.png
3219 ms
bg01.gif
2772 ms
bg02.gif
2851 ms
bg03.gif
2888 ms
bg04.gif
2965 ms
bg05.gif
2999 ms
04_top.png
2942 ms
bg01.png
4016 ms
bg02.png
2745 ms
newwin.png
2751 ms
fontSizeM_on.gif
2815 ms
fontSizeL_off.gif
2866 ms
fontSizeXL_off.gif
2912 ms
loadingAnimation.gif
2874 ms
mark_current.gif
2614 ms
mark_normal.gif
2528 ms
img11.jpg
1292 ms
print.css
373 ms
rionet.jp accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
rionet.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
rionet.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
JA
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.
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: