4.7 sec in total
528 ms
3.8 sec
357 ms
Click here to check amazing Rc I 2 content for Japan. Otherwise, check out these important facts you probably never knew about rc.i2i.jp
i2iアクセス解析はリアルタイム結果表示。全ページ共通のタグを設置するだけでPCとスマホ・携帯に対応!生ログ検索や足あと追跡など全て無料で高機能。
Visit rc.i2i.jpWe analyzed Rc.i2i.jp page load time and found that the first response time was 528 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
rc.i2i.jp performance score
name
value
score
weighting
Value6.5 s
2/100
10%
Value7.3 s
5/100
25%
Value10.0 s
9/100
10%
Value160 ms
94/100
30%
Value0
100/100
15%
Value7.3 s
50/100
10%
528 ms
483 ms
831 ms
337 ms
86 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Rc.i2i.jp, 3% (2 requests) were made to I2i.jp and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Img.i2i.jp.
Page size can be reduced by 237.5 kB (28%)
837.2 kB
599.7 kB
In fact, the total size of Rc.i2i.jp main page is 837.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. Images take 610.8 kB which makes up the majority of the site volume.
Potential reduce by 27.8 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 5.1 kB, which is 14% 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 27.8 kB or 79% of the original size.
Potential reduce by 85.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, Rc I 2 needs image optimization as it can save up to 85.8 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 96.7 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 96.7 kB or 61% of the original size.
Potential reduce by 27.2 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. Rc.i2i.jp needs all CSS files to be minified and compressed as it can save up to 27.2 kB or 85% of the original size.
Number of requests can be reduced by 22 (31%)
71
49
The browser has sent 71 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Rc I 2. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
www.i2i.jp
528 ms
o_base.css
483 ms
jquery.js
831 ms
common.js
337 ms
plusone.js
86 ms
logincheck.js
335 ms
checklogin.php
450 ms
o_base.js
337 ms
jquery-1.6.2.min.js
335 ms
jquery.gpfloat-1.0.min.js
483 ms
2nd_gets.php
360 ms
start.php
386 ms
cb=gapi.loaded_0
43 ms
inc.js
328 ms
167 ms
i2i_icon.gif
180 ms
bnr.gif
345 ms
crowd_logo.png
171 ms
gamerch_logo.png
172 ms
wazap_logo.png
171 ms
i2ipoint_logo.png
170 ms
head_settei.png
174 ms
head_hatena.png
320 ms
head_haguruma.png
311 ms
head_settei_out.png
314 ms
i2i_head2.png
309 ms
i2i_head.png
309 ms
rc_new.png
807 ms
ac_icon100.png
461 ms
ads_icon100.png
491 ms
sr_icon100.png
491 ms
rc_icon100.png
491 ms
sogo_icon100.png
492 ms
cc_icon100.png
626 ms
flash_icon100.png
629 ms
rank_icon100.png
627 ms
check_icon100.png
625 ms
setu_icon100.png
634 ms
ch_icon100.png
797 ms
top_ac.png
798 ms
top_sr.png
944 ms
top_ar.png
803 ms
top_sogo.png
942 ms
top_ch.png
1109 ms
top_cc.png
945 ms
top_flash.png
956 ms
top_seo.png
956 ms
top_jun.png
1234 ms
topcharge.png
1092 ms
rss.png
1090 ms
smo.png
1107 ms
ac_icon150.png
1106 ms
i2i.gif
324 ms
illegal.gif
321 ms
sr_icon150.png
1080 ms
rc_icon150.png
1079 ms
sogo_icon150.png
1090 ms
cc_icon150.png
1096 ms
ch_icon150.png
1090 ms
flash_icon150.png
1247 ms
rank_icon150.png
1113 ms
check_icon150.png
1112 ms
setu_icon150.png
1124 ms
i2i_icon_footer.png
1123 ms
ga.js
15 ms
__utm.gif
71 ms
b_back.png
949 ms
top_hajimete.png
1374 ms
top_sinkinew.png
1375 ms
titleback.png
1080 ms
new_ban.png
1238 ms
chargebotton.png
1184 ms
riyou_site.png
960 ms
i2i_icon_text.png
1094 ms
rc.i2i.jp accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
[role]s do not have all required [aria-*] attributes
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
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.
rc.i2i.jp 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
Issues were logged in the Issues panel in Chrome Devtools
rc.i2i.jp SEO score
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
JA
N/A
EUC-JP
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rc.i2i.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Rc.i2i.jp main page’s claimed encoding is euc-jp. 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.
rc.i2i.jp
Open Graph description is not detected on the main page of Rc I 2. 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: