Tools & Wizards About Us
bravelyarchive.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

bravelyarchive.jp

【重要】「結晶石」払戻しに関するお知らせ(10/24) | スクウェア・エニックス | SQUARE ENIX

Page Load Speed

4.2 sec in total

First Response

519 ms

Resources Loaded

3.4 sec

Page Rendered

237 ms

bravelyarchive.jp screenshot

About Website

Click here to check amazing Bravelyarchive content for Japan. Otherwise, check out these important facts you probably never knew about bravelyarchive.jp

スクウェア・エニックスのブレイブリーシリーズが初めてスマートフォンに登場！「BRAVELY ARCHIVE」の公式サイト

Visit bravelyarchive.jp

Key Findings

We analyzed Bravelyarchive.jp page load time and found that the first response time was 519 ms and then it took 3.7 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

bravelyarchive.jp performance score

0

Network Requests Diagram

bravelyarchive.jp

519 ms

square-enix.css

540 ms

jquery-ui-1.9.2.custom.css

550 ms

common.css

322 ms

index.css

495 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 8% of them (8 requests) were addressed to the original Bravelyarchive.jp, 31% (29 requests) were made to Cache.bravelyarchive.jp and 24% (23 requests) were made to Jp.square-enix.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Jp.square-enix.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 967.3 kB (28%)

Content Size

3.4 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bravelyarchive.jp main page is 3.4 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 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 18.2 kB

  • Original 24.5 kB
  • After minification 23.7 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. 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 18.2 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 74.8 kB

  • Original 2.2 MB
  • After minification 2.2 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. Bravelyarchive images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 790.5 kB

  • Original 1.1 MB
  • After minification 770.8 kB
  • After compression 262.3 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 790.5 kB or 75% of the original size.

CSS Optimization

-85%

Potential reduce by 83.9 kB

  • Original 98.8 kB
  • After minification 74.4 kB
  • After compression 14.9 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. Bravelyarchive.jp needs all CSS files to be minified and compressed as it can save up to 83.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (45%)

Requests Now

89

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bravelyarchive.jp

bravelyarchive.jp

519 ms

square-enix.css

square-enix.css

540 ms

jquery-ui-1.9.2.custom.css

jquery-ui-1.9.2.custom.css

550 ms

common.css

common.css

322 ms

index.css

index.css

495 ms

lightbox.css

lightbox.css

357 ms

jquery1-9-0.js

jquery1-9-0.js

627 ms

jquery-ui1-9.js

jquery-ui1-9.js

688 ms

sqexHeader-black.js

sqexHeader-black.js

536 ms

sp_bravelyarchive.js

sp_bravelyarchive.js

481 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

904 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

363 ms

lightbox.js

lightbox.js

377 ms

common.js

common.js

666 ms

gtm.js

gtm.js

25 ms

close.png

close.png

740 ms

logo-black.gif

logo-black.gif

560 ms

loading.gif

loading.gif

698 ms

prev.png

prev.png

726 ms

next.png

next.png

699 ms

btn_close.png

btn_close.png

727 ms

bg.jpg

bg.jpg

235 ms

btn_model.png

btn_model.png

254 ms

text.png

text.png

311 ms

logo.png

logo.png

533 ms

btn_1staniv.png

btn_1staniv.png

558 ms

pv01.png

pv01.png

619 ms

pv02.png

pv02.png

635 ms

btn_app.png

btn_app.png

659 ms

btn_gp.png

btn_gp.png

672 ms

btn_tw.png

btn_tw.png

695 ms

menu01.jpg

menu01.jpg

719 ms

menu02.jpg

menu02.jpg

719 ms

banner_bds.jpg

banner_bds.jpg

721 ms

banner_bdpb.jpg

banner_bdpb.jpg

736 ms

widgets.js

widgets.js

99 ms

foot_line.gif

foot_line.gif

477 ms

bg_menu.jpg

bg_menu.jpg

717 ms

bg_under02.jpg

bg_under02.jpg

720 ms

menu.png

menu.png

756 ms

analytics.js

analytics.js

23 ms

conversion_async.js

conversion_async.js

22 ms

collect

collect

25 ms

collect

collect

74 ms

61 ms

35 ms

gcsearch_css_black.js

gcsearch_css_black.js

540 ms

transparent.js

transparent.js

428 ms

gcsearch.js

gcsearch.js

434 ms

share

share

353 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

117 ms

share_k.gif

share_k.gif

514 ms

share_fb_k.gif

share_fb_k.gif

639 ms

share_tw_k.gif

share_tw_k.gif

652 ms

share_mx_k2.gif

share_mx_k2.gif

943 ms

share_gp.png

share_gp.png

1872 ms

share_line.png

share_line.png

911 ms

iphone_02k.gif

iphone_02k.gif

921 ms

android_k.gif

android_k.gif

1042 ms

jasrac_bravelyarchive.png

jasrac_bravelyarchive.png

1099 ms

btn_model_over.png

btn_model_over.png

331 ms

btn_1staniv_over.png

btn_1staniv_over.png

1341 ms

pv01_over.png

pv01_over.png

369 ms

pv02_over.png

pv02_over.png

370 ms

btn_tw_over.png

btn_tw_over.png

372 ms

menu01_over.jpg

menu01_over.jpg

372 ms

menu02_over.jpg

menu02_over.jpg

370 ms

syndication

syndication

104 ms

552787874588815360

552787874588815360

252 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

17 ms

btn_logo_22.png

btn_logo_22.png

404 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

28 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

124 ms

cse.js

cse.js

98 ms

hW1EojFO_normal.jpg

hW1EojFO_normal.jpg

221 ms

CdvZLBHW8AEhi3n.png:small

CdvZLBHW8AEhi3n.png:small

403 ms

Cdp7IH9W8AETnF4.jpg:small

Cdp7IH9W8AETnF4.jpg:small

383 ms

CdfoHnmWEAAJSKZ.png:small

CdfoHnmWEAAJSKZ.png:small

455 ms

CdLL8KIW8AAmu0O.png:small

CdLL8KIW8AAmu0O.png:small

437 ms

Cc76UQNXIAAbZm-.png:small

Cc76UQNXIAAbZm-.png:small

462 ms

CcXowXBWwAALaHA.png:small

CcXowXBWwAALaHA.png:small

460 ms

cse.js

cse.js

147 ms

gcsearch_black.css

gcsearch_black.css

855 ms

jsapi

jsapi

23 ms

default+ja.css

default+ja.css

4 ms

default+ja.I.js

default+ja.I.js

24 ms

minimalist.css

minimalist.css

26 ms

async-ads.js

async-ads.js

70 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

45 ms

small-logo.png

small-logo.png

19 ms

clear.gif

clear.gif

24 ms

nav_logo114.png

nav_logo114.png

12 ms

jot

jot

25 ms

gcse.gif

gcse.gif

495 ms

gcse_icon_k.png

gcse_icon_k.png

478 ms

SEO Factors

bravelyarchive.jp SEO score

0

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

bravelyarchive.jp

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