Tools & Wizards About Us
indigoblue.jp screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

indigoblue.jp

indigo blue official site

Page Load Speed

3.3 sec in total

First Response

840 ms

Resources Loaded

2.4 sec

Page Rendered

147 ms

indigoblue.jp screenshot

About Website

Visit indigoblue.jp now to see the best up-to-date Indigo Blue content and also check out these interesting facts you probably never knew about indigoblue.jp

SOUTH POINT INC.によるオフィシャルサイト。プロフィール、LIVE情報等。

Visit indigoblue.jp

Key Findings

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

Performance Metrics

indigoblue.jp performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value7.1 s

32/100

10%

TBT (Total Blocking Time)

Value780 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

indigoblue.jp

840 ms

base.css

292 ms

profile.css

328 ms

news2.html

468 ms

release2.html

483 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 53% of them (23 requests) were addressed to the original Indigoblue.jp, 42% (18 requests) were made to Platform.twitter.com and 5% (2 requests) were made to Syndication.twitter.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Indigoblue.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 9.5 kB (3%)

Content Size

280.4 kB

After Optimization

270.9 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Indigoblue.jp main page is 280.4 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. 45% of websites need less resources to load. Images take 266.6 kB which makes up the majority of the site volume.

HTML Optimization

-58%

Potential reduce by 4.5 kB

  • Original 7.9 kB
  • After minification 7.9 kB
  • After compression 3.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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 4.5 kB or 58% of the original size.

Image Optimization

-0%

Potential reduce by 352 B

  • Original 266.6 kB
  • After minification 266.2 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. Indigo Blue images are well optimized though.

CSS Optimization

-78%

Potential reduce by 4.6 kB

  • Original 6.0 kB
  • After minification 4.7 kB
  • After compression 1.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. Indigoblue.jp needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 78% of the original size.

Requests Breakdown

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

Requests Now

42

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

indigoblue.jp

indigoblue.jp

840 ms

base.css

base.css

292 ms

profile.css

profile.css

328 ms

news2.html

news2.html

468 ms

release2.html

release2.html

483 ms

banar_homepage.jpg

banar_homepage.jpg

399 ms

bar_top.gif

bar_top.gif

398 ms

widgets.js

widgets.js

47 ms

bg.gif

bg.gif

186 ms

header_bg.gif

header_bg.gif

491 ms

menu_bg.gif

menu_bg.gif

246 ms

menu_over.gif

menu_over.gif

253 ms

head11.jpg

head11.jpg

1185 ms

bar_end.gif

bar_end.gif

330 ms

shorely.png

shorely.png

539 ms

sh.png

sh.png

621 ms

myspebana01.jpg

myspebana01.jpg

450 ms

banar_facebook.jpg

banar_facebook.jpg

684 ms

banner03b.jpg

banner03b.jpg

628 ms

tenkoi.jpg

tenkoi.jpg

661 ms

footer.gif

footer.gif

711 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

143 ms

pad.css

pad.css

675 ms

uso.jpg

uso.jpg

665 ms

settings

settings

97 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

21 ms

Rina_indigo

Rina_indigo

76 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

22 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

45 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

70 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

85 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

98 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

101 ms

_buildManifest.js

_buildManifest.js

110 ms

_ssgManifest.js

_ssgManifest.js

110 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

22 ms

7651.a95a6a76dc7859214377.js

7651.a95a6a76dc7859214377.js

22 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

23 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

49 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

42 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

83 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

26 ms

bgpad02.jpg

bgpad02.jpg

177 ms

Accessibility Review

indigoblue.jp accessibility score

64

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

High

<object> elements do not have alternate text

Best Practices

indigoblue.jp best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

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

High

Document uses plugins

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

indigoblue.jp

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