Tools & Wizards About Us
buddy-complex.jp screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

buddy-complex.jp

バディ・コンプレックス アニメ公式サイト

Page Load Speed

5.7 sec in total

First Response

599 ms

Resources Loaded

4.5 sec

Page Rendered

628 ms

buddy-complex.jp screenshot

About Website

Click here to check amazing Buddy Complex content for Japan. Otherwise, check out these important facts you probably never knew about buddy-complex.jp

TVアニメ「バディ・コンプレックス」公式サイト。サンライズが贈るオリジナルバディロボットドラマ、堂々開幕！2014年1月よりTV放送＆配信開始！！2013年12月29日（日）23:00先行放送＆配信決定！！！

Visit buddy-complex.jp

Key Findings

We analyzed Buddy-complex.jp page load time and found that the first response time was 599 ms and then it took 5.1 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

buddy-complex.jp performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.065

97/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

buddy-complex.jp

599 ms

reset.css

203 ms

common.css

349 ms

top.css

372 ms

jquery-3.6.0.min.js

36 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 93% of them (80 requests) were addressed to the original Buddy-complex.jp, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Buddy-complex.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 260.3 kB (8%)

Content Size

3.3 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Buddy-complex.jp main page is 3.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 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 47.3 kB

  • Original 56.4 kB
  • After minification 55.7 kB
  • After compression 9.1 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 47.3 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 82.7 kB

  • Original 3.0 MB
  • After minification 2.9 MB

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. Buddy Complex images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 121.9 kB

  • Original 203.4 kB
  • After minification 178.6 kB
  • After compression 81.5 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 121.9 kB or 60% of the original size.

CSS Optimization

-72%

Potential reduce by 8.5 kB

  • Original 11.9 kB
  • After minification 9.4 kB
  • After compression 3.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. Buddy-complex.jp needs all CSS files to be minified and compressed as it can save up to 8.5 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (27%)

Requests Now

84

After Optimization

61

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

buddy-complex.jp

buddy-complex.jp

599 ms

reset.css

reset.css

203 ms

common.css

common.css

349 ms

top.css

top.css

372 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

36 ms

jquery.fancybox.js

jquery.fancybox.js

737 ms

jquery.mousewheel-3.0.6.pack.js

jquery.mousewheel-3.0.6.pack.js

387 ms

jquery.fancybox-media.js

jquery.fancybox-media.js

399 ms

jquery.fancybox.css

jquery.fancybox.css

411 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

520 ms

jquery.fancybox-buttons.js

jquery.fancybox-buttons.js

555 ms

import.js

import.js

559 ms

header_hype_generated_script.js

header_hype_generated_script.js

609 ms

movielist_hype_generated_script.js

movielist_hype_generated_script.js

813 ms

loader.js

loader.js

34 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

198 ms

footerFixed.js

footerFixed.js

186 ms

smartRollover.js

smartRollover.js

186 ms

ga.js

ga.js

74 ms

bg.jpg

bg.jpg

1362 ms

header_bg.png

header_bg.png

192 ms

news_b.png

news_b.png

209 ms

twitter_b.png

twitter_b.png

193 ms

nasu_twitter.png

nasu_twitter.png

345 ms

topbanner08.png

topbanner08.png

553 ms

footer_twitter.png

footer_twitter.png

377 ms

footer_facebook.png

footer_facebook.png

376 ms

footer_mixi.png

footer_mixi.png

412 ms

footer_google.png

footer_google.png

517 ms

HYPE-596.thin.min.js

HYPE-596.thin.min.js

738 ms

news_bg.png

news_bg.png

557 ms

__utm.gif

__utm.gif

18 ms

rotator.php

rotator.php

1284 ms

footer_bg.png

footer_bg.png

1095 ms

css

css

41 ms

base_left.png

base_left.png

549 ms

base_right.png

base_right.png

187 ms

menu01%2B_off.png

menu01%2B_off.png

188 ms

menu01_off.png

menu01_off.png

375 ms

menu02%2B_off.png

menu02%2B_off.png

374 ms

menu02_off.png

menu02_off.png

558 ms

menu03%2B_off.png

menu03%2B_off.png

558 ms

menu03_off.png

menu03_off.png

626 ms

menu04%2B_off.png

menu04%2B_off.png

731 ms

menu04_off.png

menu04_off.png

740 ms

menu05%2B_off.png

menu05%2B_off.png

741 ms

menu05_off.png

menu05_off.png

763 ms

menu06%2B_off.png

menu06%2B_off.png

799 ms

menu06_off.png

menu06_off.png

844 ms

menu07%2B_off.png

menu07%2B_off.png

915 ms

menu07_off.png

menu07_off.png

923 ms

menu08%2B_off.png

menu08%2B_off.png

924 ms

menu08_off.png

menu08_off.png

958 ms

shadow2.png

shadow2.png

985 ms

normal.png

normal.png

1047 ms

movielist_spacer.png

movielist_spacer.png

1097 ms

nextbackbase.png

nextbackbase.png

1109 ms

back.png

back.png

1109 ms

next.png

next.png

1154 ms

movie02.png

movie02.png

1156 ms

movie03.png

movie03.png

1251 ms

movie11.png

movie11.png

1281 ms

movie16.png

movie16.png

1291 ms

movie20.png

movie20.png

1292 ms

movie05.png

movie05.png

1348 ms

movie07.png

movie07.png

1327 ms

movie06.png

movie06.png

1455 ms

movie09.png

movie09.png

1463 ms

movie12.png

movie12.png

1298 ms

movie14.png

movie14.png

1298 ms

movie17.png

movie17.png

1139 ms

movie18.png

movie18.png

1180 ms

movie21.png

movie21.png

1231 ms

movie22.png

movie22.png

1111 ms

movie25.png

movie25.png

1126 ms

movie24.png

movie24.png

1126 ms

movie26.png

movie26.png

1119 ms

movie04.png

movie04.png

1126 ms

offline.png

offline.png

1203 ms

movie01.png

movie01.png

1151 ms

movie10.png

movie10.png

1122 ms

movie15.png

movie15.png

1121 ms

movie19.png

movie19.png

1096 ms

movie23.png

movie23.png

1148 ms

movie08.png

movie08.png

1182 ms

FwZY7-Q-xVAi_l-6Le6H6Mw.ttf

FwZY7-Q-xVAi_l-6Le6H6Mw.ttf

12 ms

Accessibility Review

buddy-complex.jp accessibility score

77

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

buddy-complex.jp best practices score

75

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

buddy-complex.jp SEO score

75

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

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

buddy-complex.jp

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