Tools & Wizards About Us
i2i.jp screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

i2i.jp

i2i 無料Webパーツ - アクセス解析パーツ

Page Load Speed

5.7 sec in total

First Response

344 ms

Resources Loaded

5.2 sec

Page Rendered

202 ms

i2i.jp screenshot

About Website

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.jp

Key Findings

We analyzed I2i.jp page load time and found that the first response time was 344 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

i2i.jp performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.4 s

59/100

10%

Network Requests Diagram

i2i.jp

344 ms

www.i2i.jp

340 ms

www.i2i.jp

678 ms

s.i2i.jp

1074 ms

adsbygoogle.js

116 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 6% of them (4 requests) were addressed to the original I2i.jp, 77% (49 requests) were made to Img.i2i.jp and 3% (2 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Img.i2i.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 190.5 kB (19%)

Content Size

1.0 MB

After Optimization

820.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of I2i.jp main page is 1.0 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. Images take 486.0 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 23.3 kB

  • Original 31.0 kB
  • After minification 26.1 kB
  • After compression 7.7 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 4.9 kB, which is 16% 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 23.3 kB or 75% of the original size.

Image Optimization

-11%

Potential reduce by 55.6 kB

  • Original 486.0 kB
  • After minification 430.5 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 55.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-18%

Potential reduce by 84.6 kB

  • Original 462.0 kB
  • After minification 456.9 kB
  • After compression 377.4 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 84.6 kB or 18% of the original size.

CSS Optimization

-85%

Potential reduce by 27.1 kB

  • Original 31.7 kB
  • After minification 25.8 kB
  • After compression 4.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 27.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (37%)

Requests Now

57

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 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 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

i2i.jp

i2i.jp

344 ms

www.i2i.jp

www.i2i.jp

340 ms

www.i2i.jp

www.i2i.jp

678 ms

s.i2i.jp

s.i2i.jp

1074 ms

adsbygoogle.js

adsbygoogle.js

116 ms

o_base.css

o_base.css

875 ms

jquery.js

jquery.js

1208 ms

common.js

common.js

709 ms

plusone.js

plusone.js

34 ms

logincheck.js

logincheck.js

713 ms

checklogin.php

checklogin.php

176 ms

o_base.js

o_base.js

713 ms

jquery-1.6.2.min.js

jquery-1.6.2.min.js

714 ms

jquery.gpfloat-1.0.min.js

jquery.gpfloat-1.0.min.js

875 ms

2nd_gets.php

2nd_gets.php

793 ms

start.php

start.php

719 ms

show_ads_impl.js

show_ads_impl.js

319 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

63 ms

i2i_icon.gif

i2i_icon.gif

169 ms

crowd_logo.png

crowd_logo.png

169 ms

gamerch_logo.png

gamerch_logo.png

170 ms

wazap_logo.png

wazap_logo.png

168 ms

i2ipoint_logo.png

i2ipoint_logo.png

167 ms

head_settei.png

head_settei.png

165 ms

head_hatena.png

head_hatena.png

332 ms

head_haguruma.png

head_haguruma.png

335 ms

head_settei_out.png

head_settei_out.png

334 ms

i2i_head2.png

i2i_head2.png

333 ms

i2i_head.png

i2i_head.png

336 ms

rc_new.png

rc_new.png

687 ms

ac_icon100.png

ac_icon100.png

496 ms

ads_icon100.png

ads_icon100.png

497 ms

sr_icon100.png

sr_icon100.png

500 ms

rc_icon100.png

rc_icon100.png

501 ms

sogo_icon100.png

sogo_icon100.png

502 ms

cc_icon100.png

cc_icon100.png

686 ms

rank_icon100.png

rank_icon100.png

686 ms

top_ac.png

top_ac.png

688 ms

top_sr.png

top_sr.png

836 ms

top_ar.png

top_ar.png

837 ms

top_sogo.png

top_sogo.png

991 ms

top_cc.png

top_cc.png

835 ms

top_jun.png

top_jun.png

836 ms

topcharge.png

topcharge.png

836 ms

rss.png

rss.png

993 ms

smo.png

smo.png

995 ms

ac_icon150.png

ac_icon150.png

998 ms

sr_icon150.png

sr_icon150.png

1004 ms

rc_icon150.png

rc_icon150.png

1003 ms

sogo_icon150.png

sogo_icon150.png

1155 ms

cc_icon150.png

cc_icon150.png

1158 ms

rank_icon150.png

rank_icon150.png

1160 ms

i2i_icon_footer.png

i2i_icon_footer.png

1168 ms

zrt_lookup.html

zrt_lookup.html

61 ms

ads

ads

62 ms

ga.js

ga.js

19 ms

__utm.gif

__utm.gif

47 ms

b_back.png

b_back.png

570 ms

top_hajimete.png

top_hajimete.png

736 ms

top_sinkinew.png

top_sinkinew.png

884 ms

titleback.png

titleback.png

724 ms

new_ban.png

new_ban.png

726 ms

chargebotton.png

chargebotton.png

734 ms

i2i_icon_text.png

i2i_icon_text.png

697 ms

Accessibility Review

i2i.jp accessibility score

73

Accessibility Issues

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

High

ARIA input fields do not have accessible names

High

[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

High

<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

High

Image elements do not have [alt] attributes

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

i2i.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

i2i.jp SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    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.

Social Sharing Optimization

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: