Tools & Wizards About Us
angeloweb.jp screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

angeloweb.jp

Angelo

Page Load Speed

4.2 sec in total

First Response

669 ms

Resources Loaded

3.4 sec

Page Rendered

119 ms

angeloweb.jp screenshot

About Website

Visit angeloweb.jp now to see the best up-to-date Angelo Web content for Japan and also check out these interesting facts you probably never knew about angeloweb.jp

キリト、Angeloの公式サイト。ライブ情報、プロフィール、ファンクラブの案内等

Visit angeloweb.jp

Key Findings

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

Performance Metrics

angeloweb.jp performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value11.4 s

0/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value12.5 s

14/100

10%

Network Requests Diagram

angeloweb.jp

669 ms

index.php

505 ms

common.css

461 ms

AC_RunActiveContent.js

493 ms

top.js

332 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 73% of them (30 requests) were addressed to the original Angeloweb.jp, 7% (3 requests) were made to 0 and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Angeloweb.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.8 kB (22%)

Content Size

496.6 kB

After Optimization

388.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-76%

Potential reduce by 8.7 kB

  • Original 11.5 kB
  • After minification 9.1 kB
  • After compression 2.8 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 2.4 kB, which is 21% 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 8.7 kB or 76% of the original size.

Image Optimization

-1%

Potential reduce by 4.6 kB

  • Original 309.2 kB
  • After minification 304.6 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. Angelo Web images are well optimized though.

JavaScript Optimization

-53%

Potential reduce by 88.7 kB

  • Original 168.8 kB
  • After minification 158.9 kB
  • After compression 80.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 88.7 kB or 53% of the original size.

CSS Optimization

-81%

Potential reduce by 5.8 kB

  • Original 7.2 kB
  • After minification 6.0 kB
  • After compression 1.4 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. Angeloweb.jp needs all CSS files to be minified and compressed as it can save up to 5.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (42%)

Requests Now

36

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Angelo Web. 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.

Network Requests Diagram

angeloweb.jp

angeloweb.jp

669 ms

index.php

index.php

505 ms

common.css

common.css

461 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

493 ms

top.js

top.js

332 ms

jquery.js

jquery.js

1385 ms

jquery.innerfade.js

jquery.innerfade.js

519 ms

swfobject.js

swfobject.js

653 ms

ga.js

ga.js

339 ms

s_retargeting.js

s_retargeting.js

540 ms

conversion.js

conversion.js

20 ms

movie14.html

movie14.html

369 ms

logo.gif

logo.gif

169 ms

menu_media.gif

menu_media.gif

156 ms

menu_live.gif

menu_live.gif

168 ms

menu_profile.gif

menu_profile.gif

166 ms

menu_discography.gif

menu_discography.gif

175 ms

menu_onlieshop.gif

menu_onlieshop.gif

177 ms

menu_fanclub.gif

menu_fanclub.gif

307 ms

menu_link.gif

menu_link.gif

328 ms

p1.jpg

p1.jpg

990 ms

p2.jpg

p2.jpg

1159 ms

p3.jpg

p3.jpg

697 ms

topttl_movie.gif

topttl_movie.gif

349 ms

topttl_information.gif

topttl_information.gif

460 ms

bnr_cause.jpg

bnr_cause.jpg

655 ms

bnr_facebook.jpg

bnr_facebook.jpg

696 ms

bnr_youtube.jpg

bnr_youtube.jpg

768 ms

bnr_twitter.jpg

bnr_twitter.jpg

982 ms

bnr_ipm.jpg

bnr_ipm.jpg

869 ms

bnr_officialblog.jpg

bnr_officialblog.jpg

1041 ms

qr_code.gif

qr_code.gif

918 ms

bnr_mobile.jpg

bnr_mobile.jpg

1042 ms

ga.js

ga.js

28 ms

47 ms

35 ms

66 ms

90 ms

contents.css

contents.css

183 ms

swfobject.js

swfobject.js

589 ms

__utm.gif

__utm.gif

11 ms

Accessibility Review

angeloweb.jp accessibility score

84

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

Links do not have a discernible name

Best Practices

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

SEO Factors

angeloweb.jp SEO score

75

Search Engine Optimization Advices

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

angeloweb.jp

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