Tools & Wizards About Us
ikina.ikidane.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 62

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

ikina.ikidane.com

トップページ

Page Load Speed

6.5 sec in total

First Response

563 ms

Resources Loaded

5.4 sec

Page Rendered

566 ms

ikina.ikidane.com screenshot

About Website

Click here to check amazing Ikina Ikidane content for Japan. Otherwise, check out these important facts you probably never knew about ikina.ikidane.com

Visit ikina.ikidane.com

Key Findings

We analyzed Ikina.ikidane.com page load time and found that the first response time was 563 ms and then it took 5.9 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

ikina.ikidane.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

83/100

25%

SI (Speed Index)

Value9.1 s

14/100

10%

TBT (Total Blocking Time)

Value1,950 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.175

69/100

15%

TTI (Time to Interactive)

Value19.6 s

3/100

10%

Network Requests Diagram

ikina.ikidane.com

563 ms

commercial.css

351 ms

HFwD9Tgl3fo

99 ms

encount

373 ms

fire

375 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 80% of them (79 requests) were addressed to the original Ikina.ikidane.com, 5% (5 requests) were made to Asumi.shinobi.jp and 4% (4 requests) were made to St.shinobi.jp. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Ikina.ikidane.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 374.7 kB (42%)

Content Size

894.8 kB

After Optimization

520.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ikina.ikidane.com main page is 894.8 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. 50% of websites need less resources to load. Images take 399.9 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 28.2 kB

  • Original 32.5 kB
  • After minification 21.1 kB
  • After compression 4.3 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 11.5 kB, which is 35% 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.2 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 399.9 kB
  • After minification 399.9 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. Ikina Ikidane images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 144.1 kB

  • Original 218.7 kB
  • After minification 218.1 kB
  • After compression 74.6 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 144.1 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 202.4 kB

  • Original 243.7 kB
  • After minification 243.5 kB
  • After compression 41.3 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. Ikina.ikidane.com needs all CSS files to be minified and compressed as it can save up to 202.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (11%)

Requests Now

98

After Optimization

87

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 98 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ikina Ikidane. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

ikina.ikidane.com

ikina.ikidane.com

563 ms

commercial.css

commercial.css

351 ms

HFwD9Tgl3fo

HFwD9Tgl3fo

99 ms

encount

encount

373 ms

fire

fire

375 ms

img001.gif

img001.gif

521 ms

img002.gif

img002.gif

372 ms

img003.jpg

img003.jpg

523 ms

img004.jpg

img004.jpg

696 ms

img002.jpg

img002.jpg

371 ms

img005.gif

img005.gif

375 ms

img003.gif

img003.gif

694 ms

img008.gif

img008.gif

708 ms

img013.gif

img013.gif

720 ms

img004.gif

img004.gif

857 ms

img010.gif

img010.gif

866 ms

img006.gif

img006.gif

1037 ms

img011.gif

img011.gif

1058 ms

img007.gif

img007.gif

1053 ms

img015.gif

img015.gif

1061 ms

img012.gif

img012.gif

1189 ms

img009.gif

img009.gif

1208 ms

img014.gif

img014.gif

1359 ms

img006.jpg

img006.jpg

1391 ms

img007.jpg

img007.jpg

1408 ms

img017.gif

img017.gif

1407 ms

img018.gif

img018.gif

1531 ms

img058.jpg

img058.jpg

2040 ms

img005.jpg

img005.jpg

1706 ms

img026.jpg

img026.jpg

1723 ms

img027.jpg

img027.jpg

1745 ms

img025.gif

img025.gif

1768 ms

img028.jpg

img028.jpg

1885 ms

img029.jpg

img029.jpg

2037 ms

img030.jpg

img030.jpg

2070 ms

img031.jpg

img031.jpg

2076 ms

img032.jpg

img032.jpg

2115 ms

img033.jpg

img033.jpg

2234 ms

img034.jpg

img034.jpg

2380 ms

img035.jpg

img035.jpg

2393 ms

img036.jpg

img036.jpg

2392 ms

IbtF5h_wywM

IbtF5h_wywM

63 ms

ji7ih6y2Hyk

ji7ih6y2Hyk

57 ms

afL2DIvhLek

afL2DIvhLek

87 ms

www-embed-player-vflQrT_sR.css

www-embed-player-vflQrT_sR.css

36 ms

www-embed-player.js

www-embed-player.js

66 ms

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js

35 ms

ad_status.js

ad_status.js

36 ms

img037.jpg

img037.jpg

2043 ms

1.13.17

1.13.17

387 ms

img038.jpg

img038.jpg

2082 ms

img039.jpg

img039.jpg

2197 ms

img026.gif

img026.gif

2198 ms

img028.gif

img028.gif

2201 ms

img040.jpg

img040.jpg

2039 ms

img041.jpg

img041.jpg

2065 ms

img042.jpg

img042.jpg

2086 ms

img031.gif

img031.gif

2195 ms

al.gif

al.gif

175 ms

pr.gif

pr.gif

331 ms

link.gif

link.gif

347 ms

track

track

172 ms

embed.js

embed.js

606 ms

track

track

173 ms

img043.jpg

img043.jpg

2204 ms

img044.jpg

img044.jpg

2198 ms

img045.jpg

img045.jpg

2026 ms

img046.jpg

img046.jpg

2038 ms

img047.jpg

img047.jpg

2076 ms

img048.jpg

img048.jpg

2187 ms

sync

sync

174 ms

img049.jpg

img049.jpg

2205 ms

img050.jpg

img050.jpg

2393 ms

img019.gif

img019.gif

2043 ms

img008.jpg

img008.jpg

2064 ms

img009.jpg

img009.jpg

2071 ms

img010.jpg

img010.jpg

2186 ms

img011.jpg

img011.jpg

2193 ms

img012.jpg

img012.jpg

2027 ms

img020.gif

img020.gif

2071 ms

img021.gif

img021.gif

2231 ms

img013.jpg

img013.jpg

2160 ms

img014.jpg

img014.jpg

2050 ms

delivery

delivery

153 ms

img022.gif

img022.gif

2028 ms

img023.gif

img023.gif

2023 ms

img015.jpg

img015.jpg

2045 ms

img016.jpg

img016.jpg

2184 ms

img017.jpg

img017.jpg

2155 ms

img018.jpg

img018.jpg

2089 ms

img019.jpg

img019.jpg

2018 ms

img020.jpg

img020.jpg

2008 ms

img021.jpg

img021.jpg

2048 ms

img022.jpg

img022.jpg

2190 ms

img023.jpg

img023.jpg

2153 ms

img024.jpg

img024.jpg

2094 ms

img025.jpg

img025.jpg

2026 ms

img056.jpg

img056.jpg

2047 ms

img001.jpg

img001.jpg

2070 ms

Accessibility Review

ikina.ikidane.com accessibility score

66

Accessibility Issues

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

ikina.ikidane.com best practices score

62

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

Browser errors were logged to the console

SEO Factors

ikina.ikidane.com SEO score

58

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ikina.ikidane.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Ikina.ikidane.com main page’s claimed encoding is shift_jis. 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

ikina.ikidane.com

Open Graph description is not detected on the main page of Ikina Ikidane. 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: