18.3 sec in total
739 ms
16.9 sec
674 ms
Click here to check amazing Rotco content for Japan. Otherwise, check out these important facts you probably never knew about rotco.jp
さまざまなジャンルのRSS更新速報とリンクをまとめたアンテナサイト。ログインするとマイアンテナがつくれます。
Visit rotco.jpWe analyzed Rotco.jp page load time and found that the first response time was 739 ms and then it took 17.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.
rotco.jp performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value8.1 s
2/100
25%
Value5.8 s
49/100
10%
Value750 ms
39/100
30%
Value0.01
100/100
15%
Value9.7 s
29/100
10%
739 ms
216 ms
364 ms
378 ms
722 ms
Our browser made a total of 193 requests to load all elements on the main page. We found that 9% of them (17 requests) were addressed to the original Rotco.jp, 7% (14 requests) were made to Aladdin.genieesspv.jp and 6% (12 requests) were made to Cs.gssprt.jp. The less responsive or slowest element that took the longest time to load (6.6 sec) belongs to the original domain Rotco.jp.
Page size can be reduced by 383.1 kB (59%)
648.2 kB
265.1 kB
In fact, the total size of Rotco.jp main page is 648.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 477.5 kB which makes up the majority of the site volume.
Potential reduce by 53.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. 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 53.9 kB or 83% of the original size.
Potential reduce by 373 B
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. Rotco images are well optimized though.
Potential reduce by 318.2 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 318.2 kB or 67% of the original size.
Potential reduce by 10.6 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. Rotco.jp needs all CSS files to be minified and compressed as it can save up to 10.6 kB or 77% of the original size.
Number of requests can be reduced by 149 (89%)
167
18
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rotco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 50 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
rotco.jp
739 ms
style.css
216 ms
user.css
364 ms
meerkat.css
378 ms
dcbdfab7a2e3864497fc58330eab7952
722 ms
jquery-1.7.2.min.js
984 ms
jquery-ui.min.js
6577 ms
jquery.tablesorter.min.js
594 ms
jquery.autopager-1.0.0.min.js
486 ms
scrolltopcontrol.js
538 ms
jquery.meerkat.1.3.js
583 ms
rotco.min.js
673 ms
rotco.user.min.js
742 ms
sh.adingo.jp
647 ms
rank.php
1783 ms
Script
700 ms
btn_search.png
807 ms
rranking.gif
877 ms
bg.jpg
1785 ms
bg_header.gif
536 ms
1.0.1.js
595 ms
1.0.0.js
264 ms
sync
245 ms
dcbdfab7a2e3864497fc58330eab7952
502 ms
sync
1529 ms
sync
784 ms
push_sync
418 ms
js1
648 ms
ib
239 ms
cookiesync
797 ms
1.1.0.js
226 ms
sync
301 ms
js
657 ms
receive_sync
198 ms
jstag
179 ms
acj
68 ms
ri
52 ms
imp
210 ms
a1033894.js
483 ms
sync
41 ms
jsk
466 ms
js1
405 ms
gl0
193 ms
js
572 ms
cs
216 ms
push_sync
188 ms
sync
768 ms
sync
609 ms
pixel
563 ms
cm
440 ms
sync
217 ms
sync
233 ms
c0bd6001e75213826778a4fea47395ec
263 ms
i.adingo.jp
432 ms
acs
233 ms
sync
242 ms
acs
427 ms
cs
247 ms
acs
292 ms
pixel
90 ms
412 ms
sync
35 ms
gcs
410 ms
759 ms
pixel
150 ms
837 ms
cs
193 ms
NewReceive
508 ms
up.png
263 ms
sh.adingo.jp
460 ms
c0bd6001e75213826778a4fea47395ec
242 ms
ad_1_inline_1.gif
707 ms
cs
208 ms
cs
211 ms
close-x.png
204 ms
cs
202 ms
ajs.php
103 ms
c0bd6001e75213826778a4fea47395ec
278 ms
pixel
45 ms
cs
212 ms
561 ms
452 ms
yads.js
686 ms
lg.php
61 ms
match.aspx
38 ms
522 ms
js1
482 ms
ib
748 ms
sg.gif
486 ms
410 ms
js
569 ms
172 ms
yads_vimps-1.4.1.js
646 ms
tag
645 ms
yads-iframe.html
220 ms
tag
511 ms
ADTECH;cfp=1;rndc=1460134149;loc=100;target=_blank;key=key1+key2+key3+key4;grp=[group];misc=1460134149385
395 ms
sh.adingo.jp
522 ms
show.php
470 ms
sync
119 ms
pixel
99 ms
generic
172 ms
oi
503 ms
mapuser
867 ms
mapuser
371 ms
mapuser
426 ms
generic
103 ms
mapuser
426 ms
mapuser
365 ms
0.gif
89 ms
push_sync
742 ms
cm
375 ms
sync
59 ms
sync
67 ms
sh.adingo.jp
508 ms
show.php
454 ms
i.adingo.jp
423 ms
mapuser
197 ms
200 ms
mapuser
42 ms
sync
226 ms
sync
31 ms
a1033892.js
535 ms
i.adingo.jp
477 ms
246 ms
jsk
289 ms
ads.js
99 ms
gl3
185 ms
mapuser
154 ms
adcomp_pc.js
39 ms
sspcore_spot.js
327 ms
acs
190 ms
acs
3404 ms
acs
3396 ms
acs
359 ms
ssp_spot.ashx
356 ms
acs
271 ms
acs
399 ms
sync
21 ms
cs
823 ms
acs
430 ms
cs
199 ms
set
481 ms
cs
229 ms
adcore.js
28 ms
adcore_pc.js
42 ms
cs
228 ms
adcore_pc_inline.js
20 ms
ad_spot.aspx
3526 ms
usermatch
27 ms
pixel.htm
81 ms
52154.gif
25 ms
usermatch
34 ms
pixel
32 ms
casale
18 ms
pm_match
68 ms
mapuser
227 ms
pixel.htm
90 ms
crum
152 ms
ddc.htm
249 ms
crum
194 ms
crum
194 ms
rum
342 ms
rum
221 ms
ddc.htm
213 ms
rum
144 ms
sync
237 ms
Pug
176 ms
pixel
90 ms
sd
158 ms
rtset
174 ms
u.php
156 ms
181 ms
mapuser
77 ms
um
142 ms
rum
359 ms
rum
58 ms
crum
67 ms
bd
132 ms
tap.php
57 ms
sync
127 ms
merge
58 ms
xrefid.xgi
98 ms
cs
716 ms
pixel.gif
100 ms
69d1a87d242c3dbc63179315891a6993
96 ms
lr.gif
183 ms
bd
100 ms
NAX8298048635883949512
169 ms
sci
2395 ms
style.css
207 ms
ad_creative.ashx
215 ms
bd
30 ms
rotco.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
rotco.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
Browser errors were logged to the console
Page has valid source maps
rotco.jp SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rotco.jp can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Rotco.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.
rotco.jp
Open Graph description is not detected on the main page of Rotco. 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: