Tools & Wizards About Us
blazblue.jp screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

blazblue.jp

BLAZBLUE OFFICIAL PORTAL SITE｜ブレイブルー オフィシャルポータルサイト

Page Load Speed

8.1 sec in total

First Response

373 ms

Resources Loaded

7.5 sec

Page Rendered

223 ms

blazblue.jp screenshot

About Website

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

「BLAZBLUE / ブレイブルー」シリーズ公式サイト

Visit blazblue.jp

Key Findings

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

Performance Metrics

blazblue.jp performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value16.1 s

0/100

25%

SI (Speed Index)

Value8.8 s

16/100

10%

TBT (Total Blocking Time)

Value1,130 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

blazblue.jp

373 ms

www.blazblue.jp

691 ms

import.css

348 ms

top.css

350 ms

lightbox.css

351 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 60% of them (58 requests) were addressed to the original Blazblue.jp, 8% (8 requests) were made to Plugins.mixi.jp and 7% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.5 sec) belongs to the original domain Blazblue.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (41%)

Content Size

3.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blazblue.jp main page is 3.0 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. 60% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.3 kB

  • Original 71.5 kB
  • After minification 70.7 kB
  • After compression 15.2 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 56.3 kB or 79% of the original size.

Image Optimization

-26%

Potential reduce by 537.3 kB

  • Original 2.1 MB
  • After minification 1.5 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. Obviously, BLAZBLUE needs image optimization as it can save up to 537.3 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 607.8 kB

  • Original 857.6 kB
  • After minification 767.4 kB
  • After compression 249.9 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 607.8 kB or 71% of the original size.

CSS Optimization

-82%

Potential reduce by 34.6 kB

  • Original 42.2 kB
  • After minification 32.9 kB
  • After compression 7.6 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. Blazblue.jp needs all CSS files to be minified and compressed as it can save up to 34.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (39%)

Requests Now

89

After Optimization

54

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blazblue.jp

blazblue.jp

373 ms

www.blazblue.jp

www.blazblue.jp

691 ms

import.css

import.css

348 ms

top.css

top.css

350 ms

lightbox.css

lightbox.css

351 ms

jquery.js

jquery.js

713 ms

rollover.js

rollover.js

396 ms

bg.js

bg.js

642 ms

prototype.js

prototype.js

1430 ms

scriptaculous.js

scriptaculous.js

692 ms

lightbox.js

lightbox.js

706 ms

conversion.js

conversion.js

16 ms

fix.css

fix.css

356 ms

class.css

class.css

603 ms

print.css

print.css

705 ms

effects.js

effects.js

347 ms

builder.js

builder.js

361 ms

ragna.jpg

ragna.jpg

1181 ms

close.png

close.png

319 ms

loading.gif

loading.gif

382 ms

prev.png

prev.png

387 ms

next.png

next.png

386 ms

bg.png

bg.png

2350 ms

title.png

title.png

833 ms

header_title.png

header_title.png

822 ms

img_01.gif

img_01.gif

725 ms

img_02.gif

img_02.gif

744 ms

img_03.gif

img_03.gif

1038 ms

img_04.gif

img_04.gif

1069 ms

img_05.gif

img_05.gif

1116 ms

img_06.gif

img_06.gif

1140 ms

main_image.jpg

main_image.jpg

2872 ms

main_visual06.png

main_visual06.png

1805 ms

bn_event.jpg

bn_event.jpg

1726 ms

bn_mobile.jpg

bn_mobile.jpg

1653 ms

bn_bbcpex.jpg

bn_bbcpex.jpg

1618 ms

bn_lost_memories.jpg

bn_lost_memories.jpg

2170 ms

bn_event_tw.jpg

bn_event_tw.jpg

2000 ms

bn_morip.jpg

bn_morip.jpg

2124 ms

bn_link.jpg

bn_link.jpg

2099 ms

bt_webshop.jpg

bt_webshop.jpg

2294 ms

bn_ch.jpg

bn_ch.jpg

2445 ms

footer_1.gif

footer_1.gif

2487 ms

arc.gif

arc.gif

2515 ms

all.js

all.js

55 ms

widgets.js

widgets.js

12 ms

plugins.js

plugins.js

462 ms

plusone.js

plusone.js

161 ms

117 ms

img_01_on.gif

img_01_on.gif

2808 ms

img_02_on.gif

img_02_on.gif

2705 ms

img_03_on.gif

img_03_on.gif

2959 ms

img_04_on.gif

img_04_on.gif

2924 ms

img_05_on.gif

img_05_on.gif

2952 ms

img_06_on.gif

img_06_on.gif

3240 ms

bn_event_on.jpg

bn_event_on.jpg

3504 ms

bn_mobile_on.jpg

bn_mobile_on.jpg

3344 ms

bn_bbcpex_on.jpg

bn_bbcpex_on.jpg

3218 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

60 ms

103 ms

xd_arbiter.php

xd_arbiter.php

97 ms

xd_arbiter.php

xd_arbiter.php

141 ms

tweet_button.6a78875565a912489e9aef879c881358.ja.html

tweet_button.6a78875565a912489e9aef879c881358.ja.html

38 ms

108 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

27 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

51 ms

fastbutton

fastbutton

123 ms

postmessageRelay

postmessageRelay

72 ms

bn_lost_memories_on.jpg

bn_lost_memories_on.jpg

3163 ms

jot

jot

103 ms

api.js

api.js

62 ms

core:rpc:shindig.random:shindig.sha1.js

core:rpc:shindig.random:shindig.sha1.js

87 ms

2536007149-postmessagerelay.js

2536007149-postmessagerelay.js

70 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

35 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

21 ms

bn_event_tw_on.jpg

bn_event_tw_on.jpg

3018 ms

bn_morip_on.jpg

bn_morip_on.jpg

3276 ms

bn_link_on.jpg

bn_link_on.jpg

3283 ms

bt_webshop_on.jpg

bt_webshop_on.jpg

3021 ms

bn_ch_on.jpg

bn_ch_on.jpg

3047 ms

favorite.pl

favorite.pl

319 ms

like.php

like.php

62 ms

vpc6VNjRPXV.js

vpc6VNjRPXV.js

59 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

59 ms

mixi_check_entry.css

mixi_check_entry.css

9 ms

json.js

json.js

295 ms

underscore-string-1.3.3-2.0.0-compress.js

underscore-string-1.3.3-2.0.0-compress.js

297 ms

namespace-brook-compress.js

namespace-brook-compress.js

296 ms

prototype-effects-1.6.1-1.8.3-compress.js

prototype-effects-1.6.1-1.8.3-compress.js

449 ms

mixi.js

mixi.js

305 ms

favorite.production.js

favorite.production.js

304 ms

jquery-1.7.1.min-noconflict-compress.js

jquery-1.7.1.min-noconflict-compress.js

747 ms

analytics.js

analytics.js

18 ms

comment001.gif

comment001.gif

7 ms

favorite_button004.png

favorite_button004.png

4 ms

comment_content_top001.gif

comment_content_top001.gif

5 ms

Accessibility Review

blazblue.jp accessibility score

78

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

blazblue.jp best practices score

58

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

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

blazblue.jp SEO score

92

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

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    SHIFT_JIS

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

blazblue.jp

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