5.3 sec in total
308 ms
4.6 sec
414 ms
Click here to check amazing I 2 content for Japan. Otherwise, check out these important facts you probably never knew about i2i.jp
i2iアクセス解析はリアルタイム結果表示。全ページ共通のタグを設置するだけでPCとスマホ・携帯に対応!生ログ検索や足あと追跡など全て無料で高機能。
Visit i2i.jpWe analyzed I2i.jp page load time and found that the first response time was 308 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
i2i.jp performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value7.5 s
4/100
25%
Value10.1 s
9/100
10%
Value210 ms
88/100
30%
Value0
100/100
15%
Value7.5 s
48/100
10%
308 ms
478 ms
470 ms
816 ms
316 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original I2i.jp, 84% (61 requests) were made to Img.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 (2.2 sec) relates to the external source Img.i2i.jp.
Page size can be reduced by 1.1 MB (50%)
2.2 MB
1.1 MB
In fact, the total size of I2i.jp main page is 2.2 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. 35% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 28.0 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 28.0 kB or 79% of the original size.
Potential reduce by 170.1 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, I 2 needs image optimization as it can save up to 170.1 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 774.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 774.1 kB or 76% of the original size.
Potential reduce by 152.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. I2i.jp needs all CSS files to be minified and compressed as it can save up to 152.6 kB or 83% of the original size.
Number of requests can be reduced by 20 (29%)
69
49
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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.
i2i.jp
308 ms
www.i2i.jp
478 ms
o_base.css
470 ms
jquery.js
816 ms
common.js
316 ms
plusone.js
71 ms
logincheck.js
299 ms
checklogin.php
294 ms
o_base.js
314 ms
jquery-1.6.2.min.js
315 ms
jquery.gpfloat-1.0.min.js
468 ms
2nd_gets.php
475 ms
start.php
399 ms
cb=gapi.loaded_0
15 ms
inc.js
416 ms
170 ms
i2i_icon.gif
166 ms
bnr.gif
666 ms
crowd_logo.png
166 ms
gamerch_logo.png
163 ms
wazap_logo.png
166 ms
i2ipoint_logo.png
166 ms
head_settei.png
164 ms
head_hatena.png
304 ms
head_haguruma.png
311 ms
head_settei_out.png
311 ms
i2i_head2.png
310 ms
i2i_head.png
306 ms
rc_new.png
766 ms
ac_icon100.png
468 ms
ads_icon100.png
473 ms
sr_icon100.png
472 ms
rc_icon100.png
473 ms
sogo_icon100.png
471 ms
cc_icon100.png
648 ms
flash_icon100.png
650 ms
rank_icon100.png
648 ms
check_icon100.png
647 ms
setu_icon100.png
650 ms
ch_icon100.png
770 ms
top_ac.png
770 ms
top_sr.png
923 ms
top_ar.png
913 ms
top_sogo.png
923 ms
top_ch.png
912 ms
top_cc.png
924 ms
top_flash.png
922 ms
top_seo.png
1086 ms
top_jun.png
1414 ms
topcharge.png
1081 ms
rss.png
1086 ms
smo.png
1085 ms
ac_icon150.png
1085 ms
sr_icon150.png
1270 ms
rc_icon150.png
1265 ms
sogo_icon150.png
1270 ms
cc_icon150.png
1272 ms
ch_icon150.png
1272 ms
flash_icon150.png
1815 ms
rank_icon150.png
1452 ms
check_icon150.png
1449 ms
setu_icon150.png
1446 ms
i2i_icon_footer.png
1300 ms
ga.js
26 ms
__utm.gif
63 ms
b_back.png
1094 ms
top_hajimete.png
1812 ms
top_sinkinew.png
2187 ms
titleback.png
1461 ms
new_ban.png
1821 ms
chargebotton.png
1606 ms
riyou_site.png
1492 ms
i2i_icon_text.png
1491 ms
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.
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
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 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 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.
i2i.jp
Open Graph description is not detected on the main page of 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: