7.2 sec in total
1.2 sec
5.6 sec
494 ms
Visit rokaki.com now to see the best up-to-date Rokaki content and also check out these interesting facts you probably never knew about rokaki.com
ろ過器,カートリッジフィルター,バッグフィルター,サンドフィルター,中和装置など、水処理に関する各種装置はろ過器ドットコムへ。国内外の優れたろ過器を用意しております。また植物工場の設計、施工もお任せください。
Visit rokaki.comWe analyzed Rokaki.com page load time and found that the first response time was 1.2 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
rokaki.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value16.9 s
0/100
25%
Value8.5 s
17/100
10%
Value350 ms
73/100
30%
Value0
100/100
15%
Value8.0 s
42/100
10%
1168 ms
299 ms
446 ms
318 ms
847 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 98% of them (95 requests) were addressed to the original Rokaki.com, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.7 sec) belongs to the original domain Rokaki.com.
Page size can be reduced by 650.6 kB (23%)
2.8 MB
2.2 MB
In fact, the total size of Rokaki.com main page is 2.8 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. 50% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 40.6 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 40.6 kB or 82% of the original size.
Potential reduce by 393.8 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, Rokaki needs image optimization as it can save up to 393.8 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 182.4 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 182.4 kB or 72% of the original size.
Potential reduce by 33.7 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. Rokaki.com needs all CSS files to be minified and compressed as it can save up to 33.7 kB or 84% of the original size.
Number of requests can be reduced by 13 (14%)
96
83
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rokaki. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and as a result speed up the page load time.
rokaki.com
1168 ms
utility.css
299 ms
skin.css
446 ms
jquery.flexslider.css
318 ms
jquery-1.11.1.min.js
847 ms
current.js
363 ms
smoothScroll.js
441 ms
opacity-rollover2.1.js
471 ms
scrolltopcontrol.js
504 ms
jquery.biggerlink.min.js
542 ms
contentsAccordion.js
585 ms
jquery.easing.1.3.js
591 ms
jquery.transit.js
780 ms
jquery.jrumble.1.3.js
679 ms
areaSlide.js
722 ms
jquery.flexslider.js
1019 ms
jquery.matchHeight-min.js
736 ms
analytics.js
130 ms
NMC-16-Top.jpg
630 ms
logo.png
341 ms
header_contact.jpg
442 ms
header_tel.png
147 ms
nav.png
313 ms
mainimage01.jpg
2717 ms
top_main_txt01.png
337 ms
mainimage02.jpg
2104 ms
mainimage03.jpg
2488 ms
main_image_shadow.jpg
505 ms
top_title01.png
679 ms
top_box01_img01.png
591 ms
top_box01_img04.png
672 ms
top_box01_img03.png
739 ms
NBFS-Top.png
839 ms
top_box01_img05.png
1020 ms
top_box01_img06.png
886 ms
top_box01_img07.png
1175 ms
top_box01_img08.png
1033 ms
top_box01_img09.png
1359 ms
top_box01_img10.png
1328 ms
top_box01_img11.png
1511 ms
top_box01_img12.png
1475 ms
NP8800-Top.png
1701 ms
NDP6000-Top.png
1623 ms
top_box01_img15.png
1679 ms
top_title02.png
1770 ms
top_box02_icon01.png
1846 ms
top_box02_text01.png
1872 ms
top_box02_line01.jpg
1917 ms
top_box02_icon02.png
2014 ms
top_box02_text02.png
2042 ms
top_box02_icon03.png
2063 ms
top_box02_text03.png
2182 ms
top_box02_line02.jpg
2214 ms
top_box02_icon04.png
2214 ms
NRS750-6_Top.png
707 ms
RSC_GSV_Top.png
1003 ms
top_box02_text04.png
2240 ms
collect
11 ms
top_box02_icon05.png
2211 ms
top_box02_text05.png
2077 ms
top_box02_icon06.png
2029 ms
top_box02_text06.png
2055 ms
top_box02_icon07.png
2086 ms
top_box02_text07.png
2009 ms
top_box02_icon08.png
1968 ms
top_box02_text08.png
1868 ms
top_box02_icon09.png
1964 ms
top_box02_text09.png
1922 ms
top_box02_btn.jpg
1853 ms
top_title03.png
1798 ms
top_box03_img01.jpg
2050 ms
top_box03_icon01.png
1764 ms
top_box03_text01.png
1632 ms
top_box03_img02.jpg
1501 ms
top_box03_icon02.png
1499 ms
top_box03_text02.png
1418 ms
top_box03_icon03.png
1443 ms
top_box03_text03.png
1329 ms
top_box03_img03.jpg
1297 ms
top_box03_icon04.png
1324 ms
top_box03_text04.png
1306 ms
top_box03_img04.jpg
1550 ms
top_box03_btn.jpg
1239 ms
top_box04_copy01.png
1205 ms
top_box04_img01.jpg
1511 ms
top_box04_img02.jpg
1198 ms
top_box04_img03.jpg
1193 ms
top_box04_btn.png
1172 ms
top_title04.png
1083 ms
top_rss_btn_on.jpg
1195 ms
top_contact_box_bd.gif
1222 ms
top_contact_title01.gif
1168 ms
top_contact_title02.gif
1076 ms
footer_bg_wrapper.png
1184 ms
footer_logo.png
1198 ms
footer_arr.png
1167 ms
pagetop.jpg
1101 ms
rokaki.com 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
Links do not have a discernible name
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.
rokaki.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
rokaki.com SEO score
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 doesn't use 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 Rokaki.com 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 Rokaki.com 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.
rokaki.com
Open Graph description is not detected on the main page of Rokaki. 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: