10.4 sec in total
482 ms
9.6 sec
270 ms
Welcome to rodea.jp homepage info - get ready to check Rodea best content for Japan right away, or after learning these important things about rodea.jp
This domain may be for sale!
Visit rodea.jpWe analyzed Rodea.jp page load time and found that the first response time was 482 ms and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
rodea.jp performance score
name
value
score
weighting
Value0.9 s
100/100
10%
Value0.9 s
100/100
25%
Value3.0 s
94/100
10%
Value1,740 ms
10/100
30%
Value0.197
62/100
15%
Value4.4 s
83/100
10%
482 ms
377 ms
388 ms
385 ms
598 ms
Our browser made a total of 97 requests to load all elements on the main page. We found that 75% of them (73 requests) were addressed to the original Rodea.jp, 8% (8 requests) were made to Apis.google.com and 3% (3 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Rodea.jp.
Page size can be reduced by 566.3 kB (20%)
2.8 MB
2.3 MB
In fact, the total size of Rodea.jp 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.2 MB which makes up the majority of the site volume.
Potential reduce by 22.1 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 22.1 kB or 70% of the original size.
Potential reduce by 64.4 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. Rodea images are well optimized though.
Potential reduce by 433.0 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 433.0 kB or 79% of the original size.
Potential reduce by 46.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. Rodea.jp needs all CSS files to be minified and compressed as it can save up to 46.7 kB or 85% of the original size.
Number of requests can be reduced by 50 (53%)
95
45
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rodea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
rodea.jp
482 ms
bookblock.css
377 ms
jquery.maximage.min.css
388 ms
jquery.fancybox-1.3.4.css
385 ms
top.css
598 ms
import.js
391 ms
modernizr.custom.js
402 ms
snowfall.jquery.min.js
759 ms
jquery.fancybox-1.3.4.js
953 ms
jquery.jscrollpane.min.js
777 ms
jquery.mousewheel.min.js
773 ms
jquery.jscrollpane.css
790 ms
jplayer.css
978 ms
jquery.cookie.js
1136 ms
jquery.jplayer.min.js
1530 ms
jplayer.playlist.js
1346 ms
jquery.jplayer.inspector.js
1358 ms
bgm.js
1329 ms
top_setting.js
1552 ms
jquerypp.custom.js
1509 ms
jquery.bookblock.js
1905 ms
jquery-1.8.3.js
2286 ms
jquery.easing.js
1133 ms
jquery.backstretch.min.js
1289 ms
jquery.sticky.js
1313 ms
base.css
1339 ms
loading.gif
591 ms
analytics.js
14 ms
logo_kadokawa.png
402 ms
logo-wiiU.png
386 ms
logo-3ds.png
394 ms
nav_bg.png
777 ms
nav_text.png
1166 ms
icon_new.png
764 ms
nav_current_mark.png
770 ms
top_movie05_ov.png
1160 ms
top_movie05.png
1337 ms
mainimg_frame.png
1134 ms
top02_catchcopy.png
1527 ms
logo.png
1749 ms
top02_rodea.png
1749 ms
top02_bg.jpg
2435 ms
top02_cloud_05_rb.png
2509 ms
top02_cloud_04_lb.png
2705 ms
top02_cloud_03_rt.png
2694 ms
top02_cloud_02_lt.png
2481 ms
top02_cloud_01_cb.png
2706 ms
top02_cloud_bg.jpg
3197 ms
top03_catchcopy.png
3248 ms
top03_fix.jpg
3658 ms
white.png
3078 ms
mainimg_catchcopy.png
3465 ms
top01_fix.jpg
3858 ms
banner_shokai_link.png
3646 ms
banner_taiken.png
3786 ms
sound_bg.png
3645 ms
icon_sound.png
3840 ms
btn_play.png
4024 ms
btn_pause.png
4048 ms
btn_bgm_on.png
4044 ms
btn_bgm_off.png
4169 ms
seek.png
4222 ms
progress.png
4249 ms
widgets.js
11 ms
collect
13 ms
sdk.js
96 ms
plusone.js
105 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
40 ms
97 ms
cb=gapi.loaded_0
36 ms
cb=gapi.loaded_1
55 ms
fastbutton
93 ms
xd_arbiter.php
79 ms
xd_arbiter.php
136 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html
13 ms
postmessageRelay
75 ms
cb=gapi.loaded_0
33 ms
cb=gapi.loaded_1
33 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
32 ms
3193398744-postmessagerelay.js
19 ms
rpc:shindig_random.js
50 ms
jot
89 ms
cb=gapi.loaded_0
4 ms
vol_seek.png
4037 ms
vol_progress.png
4045 ms
spec.png
4447 ms
topics.png
4179 ms
spec_topics_gear.png
4061 ms
mainimg_gear.png
4065 ms
fancybox-x.png
4034 ms
fancybox.png
3656 ms
fancybox-y.png
3975 ms
blank.gif
4012 ms
bg_01_c.jpg
951 ms
like.php
76 ms
wy1X4hBW7e7.js
142 ms
LVx-xkvaJ0b.png
154 ms
rodea.jp 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
<frame> or <iframe> elements do not have a title
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.
rodea.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Issues were logged in the Issues panel in Chrome Devtools
rodea.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rodea.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Rodea.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.
rodea.jp
Open Graph data is detected on the main page of Rodea. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: