Tools & Wizards About Us
aiko.com screenshot

Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

aiko.com

aiko official website

Page Load Speed

6.9 sec in total

First Response

779 ms

Resources Loaded

6 sec

Page Rendered

143 ms

aiko.com screenshot

About Website

Click here to check amazing Aiko content for Japan. Otherwise, check out these important facts you probably never knew about aiko.com

aikoのオフィシャルウェブサイト。新譜、ライブ情報、ファンクラブ情報など掲載しています。

Visit aiko.com

Key Findings

We analyzed Aiko.com page load time and found that the first response time was 779 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

aiko.com performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value24.4 s

0/100

10%

TBT (Total Blocking Time)

Value17,840 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.443

21/100

15%

TTI (Time to Interactive)

Value41.7 s

0/100

10%

Network Requests Diagram

aiko.com

779 ms

www.aiko.com

1415 ms

gtm.js

43 ms

2024.css

734 ms

mediaelementplayer.css

639 ms

Our browser made a total of 76 requests to load all elements on the main page. We found that 58% of them (44 requests) were addressed to the original Aiko.com, 28% (21 requests) were made to Platform.twitter.com and 7% (5 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Aiko.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 544.8 kB (40%)

Content Size

1.3 MB

After Optimization

801.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 29.3 kB

  • Original 35.7 kB
  • After minification 24.1 kB
  • After compression 6.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.6 kB, which is 33% 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 29.3 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 45.3 kB

  • Original 741.3 kB
  • After minification 695.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. Aiko images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 214.3 kB

  • Original 281.0 kB
  • After minification 220.7 kB
  • After compression 66.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 214.3 kB or 76% of the original size.

CSS Optimization

-89%

Potential reduce by 255.9 kB

  • Original 288.4 kB
  • After minification 215.2 kB
  • After compression 32.5 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. Aiko.com needs all CSS files to be minified and compressed as it can save up to 255.9 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (52%)

Requests Now

73

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

aiko.com

aiko.com

779 ms

www.aiko.com

www.aiko.com

1415 ms

gtm.js

gtm.js

43 ms

2024.css

2024.css

734 ms

mediaelementplayer.css

mediaelementplayer.css

639 ms

lity.min.css

lity.min.css

629 ms

viewport.js

viewport.js

630 ms

jquery.js

jquery.js

856 ms

jquery.easing.js

jquery.easing.js

628 ms

mediaelement-and-player.js

mediaelement-and-player.js

1303 ms

jquery.bxslider.min.4.2.0.js

jquery.bxslider.min.4.2.0.js

945 ms

common.js

common.js

924 ms

lity.min.js

lity.min.js

939 ms

top.js

top.js

1025 ms

like.php

like.php

149 ms

logo_pc.png

logo_pc.png

339 ms

icon_x.png

icon_x.png

339 ms

icon_ig.png

icon_ig.png

297 ms

icon_fb.png

icon_fb.png

293 ms

icon_yt.png

icon_yt.png

295 ms

gnavi.png

gnavi.png

375 ms

667e71fb4f2fa.jpg

667e71fb4f2fa.jpg

747 ms

667d2d428b34d.jpg

667d2d428b34d.jpg

1055 ms

667e1a7ef3a92.jpg

667e1a7ef3a92.jpg

1130 ms

bn_goods.png

bn_goods.png

665 ms

bn_store.png

bn_store.png

717 ms

bn_digital_store.jpg

bn_digital_store.jpg

798 ms

h3_news.png

h3_news.png

956 ms

h3_news.png

h3_news.png

1019 ms

bg_arr.png

bg_arr.png

1042 ms

h3_topmedia.png

h3_topmedia.png

1092 ms

h3_media01.png

h3_media01.png

1246 ms

h3_media01.png

h3_media01.png

1317 ms

h3_media02.png

h3_media02.png

1338 ms

h3_media02.png

h3_media02.png

1350 ms

h3_media03.png

h3_media03.png

1385 ms

h3_media03.png

h3_media03.png

1428 ms

h3_media05.png

h3_media05.png

1536 ms

h3_media05.png

h3_media05.png

1611 ms

h3_x.png

h3_x.png

1633 ms

h3_x.png

h3_x.png

1641 ms

bt_top_pv_231127.jpg

bt_top_pv_231127.jpg

1745 ms

bt_top_pv.png

bt_top_pv.png

1722 ms

bt_top_pv.png

bt_top_pv.png

1827 ms

point_foot.png

point_foot.png

1902 ms

linebutton_82x20.png

linebutton_82x20.png

1939 ms

widgets.js

widgets.js

35 ms

933231400

933231400

178 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

18 ms

settings

settings

94 ms

7Sq0vGHTbTI.js

7Sq0vGHTbTI.js

19 ms

FEppCFCt76d.png

FEppCFCt76d.png

17 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

5 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

9 ms

embeds

embeds

31 ms

embeds

embeds

55 ms

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

follow_button.2f70fb173b9000da126c79afe2098f02.ja.html

24 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

18 ms

aiko_dochibi

aiko_dochibi

1683 ms

aiko_dochibi

aiko_dochibi

913 ms

api.js

api.js

7 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

6 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

7 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

13 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

13 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

13 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

14 ms

_buildManifest.js

_buildManifest.js

14 ms

_ssgManifest.js

_ssgManifest.js

14 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

8 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

9 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

4 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

8 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

7 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

19 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

6 ms

Accessibility Review

aiko.com accessibility score

89

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

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

aiko.com 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

Browser errors were logged to the console

SEO Factors

aiko.com SEO score

89

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aiko.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 Aiko.com 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.

Social Sharing Optimization

aiko.com

Open Graph data is detected on the main page of Aiko. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: