5.3 sec in total
768 ms
4.4 sec
192 ms
Click here to check amazing Rokugen content for Japan. Otherwise, check out these important facts you probably never knew about rokugen.net
Visit rokugen.netWe analyzed Rokugen.net page load time and found that the first response time was 768 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
rokugen.net performance score
name
value
score
weighting
Value4.5 s
16/100
10%
Value5.1 s
25/100
25%
Value14.6 s
1/100
10%
Value360 ms
72/100
30%
Value0.167
71/100
15%
Value10.2 s
25/100
10%
768 ms
508 ms
675 ms
712 ms
374 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 95% of them (60 requests) were addressed to the original Rokugen.net, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Rokugen.net.
Page size can be reduced by 307.8 kB (11%)
2.8 MB
2.5 MB
In fact, the total size of Rokugen.net 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. 45% of websites need less resources to load. Images take 2.5 MB which makes up the majority of the site volume.
Potential reduce by 7.4 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 7.4 kB or 70% of the original size.
Potential reduce by 79.3 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. Rokugen images are well optimized though.
Potential reduce by 197.1 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 197.1 kB or 72% of the original size.
Potential reduce by 24.1 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. Rokugen.net needs all CSS files to be minified and compressed as it can save up to 24.1 kB or 85% of the original size.
Number of requests can be reduced by 6 (10%)
60
54
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rokugen. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
rokugen.net
768 ms
style.css
508 ms
skitter.styles.css
675 ms
css3-mediaqueries.js
712 ms
common.js
374 ms
jquery-1.6.3.min.js
1108 ms
jquery.easing.1.3.js
566 ms
jquery.skitter.js
1133 ms
jquery.skitter.min.js
842 ms
ga.js
83 ms
anna_bg.jpg
762 ms
left01.png
379 ms
left05.jpg
172 ms
left04.png
170 ms
logo_off.png
357 ms
menu_bg.png
186 ms
top_off.png
339 ms
about_off.png
341 ms
discography_off.png
370 ms
works_off.png
507 ms
blog_off.png
508 ms
left02.png
533 ms
line_top.png
555 ms
left03.png
564 ms
hitowokanaderu.png
675 ms
red_bg.png
846 ms
s09.png
1598 ms
md2.png
1292 ms
s08.png
1698 ms
s06.png
1683 ms
s05.png
1326 ms
line_bottom.png
1182 ms
right.png
1351 ms
twitter_off.png
1477 ms
twitter_bg.png
1516 ms
youtube_off.png
1519 ms
ustream_off.png
1662 ms
rss_off.png
1709 ms
bottom_bg.png
2195 ms
latest_news.png
1773 ms
date01_news.png
1846 ms
date02_news.png
1849 ms
date03_news.png
1884 ms
latest_video.png
1894 ms
video.jpg
1949 ms
upcoming_events.png
2028 ms
__utm.gif
14 ms
collect
57 ms
date01_events.png
1857 ms
more_infomation_off.png
1912 ms
sprite-clean.png
1908 ms
ajax-loader.gif
1797 ms
logo_on.png
192 ms
top_on.png
191 ms
about_on.png
172 ms
discography_on.png
171 ms
works_on.png
179 ms
blog_on.png
185 ms
twitter_on.png
338 ms
youtube_on.png
338 ms
ustream_on.png
356 ms
rss_on.png
370 ms
more_infomation_on.png
379 ms
rokugen.net accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
rokugen.net 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
rokugen.net 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
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
JA
JA
SHIFT_JIS
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rokugen.net 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 Rokugen.net 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.
rokugen.net
Open Graph description is not detected on the main page of Rokugen. 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: