Tools & Wizards About Us
yahoo.sennenyusya.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

yahoo.sennenyusya.jp

「千年勇者～時渡りのトモシビト～」 公式サイト - クリックでスクエニRPG

Page Load Speed

8.2 sec in total

First Response

830 ms

Resources Loaded

6.8 sec

Page Rendered

497 ms

yahoo.sennenyusya.jp screenshot

About Website

Click here to check amazing Yahoo Sennenyusya content for Japan. Otherwise, check out these important facts you probably never knew about yahoo.sennenyusya.jp

ブラウザゲーム史上初の技術でイラストがなめらかに動き出す！スクウェア・エニックス新作ブラウザRPG「千年勇者～時渡りのトモシビト～」ついに正式サービス開始！

Visit yahoo.sennenyusya.jp

Key Findings

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

Performance Metrics

yahoo.sennenyusya.jp performance score

0

Network Requests Diagram

yahoo.sennenyusya.jp

830 ms

style.css

199 ms

jquery.min.js

28 ms

jquery-ui.min.js

63 ms

bridge_titlelist.js

276 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yahoo.sennenyusya.jp, 23% (30 requests) were made to Cache.sennenyusya.jp and 7% (9 requests) were made to Plugins.mixi.jp. The less responsive or slowest element that took the longest time to load (2.7 sec) relates to the external source Cache.sennenyusya.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 689.3 kB (26%)

Content Size

2.7 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yahoo.sennenyusya.jp main page is 2.7 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 25.4 kB

  • Original 35.5 kB
  • After minification 34.0 kB
  • After compression 10.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 25.4 kB or 71% of the original size.

Image Optimization

-8%

Potential reduce by 151.2 kB

  • Original 1.9 MB
  • After minification 1.8 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. Yahoo Sennenyusya images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 462.9 kB

  • Original 673.1 kB
  • After minification 641.8 kB
  • After compression 210.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 462.9 kB or 69% of the original size.

CSS Optimization

-81%

Potential reduce by 49.8 kB

  • Original 61.2 kB
  • After minification 51.2 kB
  • After compression 11.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. Yahoo.sennenyusya.jp needs all CSS files to be minified and compressed as it can save up to 49.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 70 (59%)

Requests Now

119

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yahoo.sennenyusya.jp

yahoo.sennenyusya.jp

830 ms

style.css

style.css

199 ms

jquery.min.js

jquery.min.js

28 ms

jquery-ui.min.js

jquery-ui.min.js

63 ms

bridge_titlelist.js

bridge_titlelist.js

276 ms

bg.jpg

bg.jpg

45 ms

logo_sqex.png

logo_sqex.png

25 ms

logo_yahoo.png

logo_yahoo.png

21 ms

pXkNodz6

pXkNodz6

307 ms

conversion.js

conversion.js

37 ms

s_retargeting.js

s_retargeting.js

631 ms

bridge_titlelist.css

bridge_titlelist.css

73 ms

like.php

like.php

163 ms

btn_mark.png

btn_mark.png

110 ms

widgets.js

widgets.js

40 ms

pageTitle.png

pageTitle.png

108 ms

button_BgShadow.png

button_BgShadow.png

130 ms

button_Entry_hover.png

button_Entry_hover.png

108 ms

button_Entry.png

button_Entry.png

132 ms

mainVisualBg.jpg

mainVisualBg.jpg

131 ms

mainVisual.png

mainVisual.png

443 ms

belt_btn.png

belt_btn.png

130 ms

socialButtonsBg.png

socialButtonsBg.png

128 ms

btn_share.png

btn_share.png

137 ms

plugins.js

plugins.js

301 ms

plusone.js

plusone.js

138 ms

story_bg.png

story_bg.png

2718 ms

story_bg_text.png

story_bg_text.png

108 ms

gamePoint_title.png

gamePoint_title.png

111 ms

gamePoint_point1_title.png

gamePoint_point1_title.png

118 ms

gamePoint_point1_image.png

gamePoint_point1_image.png

127 ms

gamePoint_point1_text.png

gamePoint_point1_text.png

153 ms

gamePoint_point2_title.png

gamePoint_point2_title.png

207 ms

gamePoint_point2_image.png

gamePoint_point2_image.png

153 ms

gamePoint_point2_text.png

gamePoint_point2_text.png

207 ms

gamePoint_point3_title.png

gamePoint_point3_title.png

210 ms

gamePoint_point3_image.png

gamePoint_point3_image.png

336 ms

gamePoint_point3_text.png

gamePoint_point3_text.png

540 ms

footerButton_shadow.png

footerButton_shadow.png

238 ms

footerButton_active.png

footerButton_active.png

225 ms

footerButton_normal.png

footerButton_normal.png

238 ms

line_globalFooter.png

line_globalFooter.png

245 ms

rand=0.8381572691723704

rand=0.8381572691723704

1594 ms

n

n

1119 ms

TY3MhkXpWJ-.js

TY3MhkXpWJ-.js

201 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

218 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

17 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

16 ms

fastbutton

fastbutton

72 ms

postmessageRelay

postmessageRelay

56 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

20 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

19 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

48 ms

rpc:shindig_random.js

rpc:shindig_random.js

34 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

b

b

592 ms

gtm.js

gtm.js

37 ms

79 ms

89 ms

c7fa75350a4dace7_30.js

c7fa75350a4dace7_30.js

509 ms

54 ms

analytics.js

analytics.js

9 ms

36 ms

collect

collect

10 ms

collect

collect

53 ms

collect

collect

6 ms

collect

collect

58 ms

tag.js

tag.js

36 ms

38 ms

aone_dc_general.js

aone_dc_general.js

236 ms

mone3.js

mone3.js

152 ms

titlelist_btn.png

titlelist_btn.png

17 ms

data.js

data.js

16 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

42 ms

favorite.pl

favorite.pl

328 ms

26 ms

tag

tag

19 ms

ytc.js

ytc.js

28 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.ja.html

22 ms

mone2.html

mone2.html

156 ms

jot

jot

89 ms

createCookieSegument.js

createCookieSegument.js

161 ms

mixi_check_entry.css

mixi_check_entry.css

18 ms

errorreport.production.js

errorreport.production.js

293 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

296 ms

namespace-brook-compress.js

namespace-brook-compress.js

301 ms

prototype-effects-1.6.1-1.8.3-compress.js

prototype-effects-1.6.1-1.8.3-compress.js

445 ms

mixi.js

mixi.js

304 ms

favorite.production.js

favorite.production.js

584 ms

jquery-1.7.1.min-noconflict-compress.js

jquery-1.7.1.min-noconflict-compress.js

733 ms

TIMESTAMP=1458492313-1461099599

TIMESTAMP=1458492313-1461099599

419 ms

jstag2

jstag2

30 ms

blade_track_jp.js

blade_track_jp.js

339 ms

pixel.js

pixel.js

309 ms

pix

pix

155 ms

303 ms

cookie_enabled_get.html

cookie_enabled_get.html

346 ms

comment001.gif

comment001.gif

6 ms

pixel

pixel

18 ms

pixel

pixel

151 ms

150 ms

favorite_button004.png

favorite_button004.png

13 ms

comment_content_top001.gif

comment_content_top001.gif

8 ms

bl_track.cgi

bl_track.cgi

329 ms

bl_track.cgi

bl_track.cgi

357 ms

pixel

pixel

13 ms

sd

sd

8 ms

Pug

Pug

23 ms

sync.ad-stir.com

sync.ad-stir.com

296 ms

sync

sync

5 ms

sync

sync

355 ms

is

is

386 ms

google

google

151 ms

mapuser

mapuser

148 ms

adfunnel

adfunnel

151 ms

xrost

xrost

150 ms

rep

rep

308 ms

16 ms

adv.js

adv.js

207 ms

23 ms

19 ms

20 ms

39 ms

16 ms

22 ms

22 ms

dg_gateway.js

dg_gateway.js

8 ms

adv_inner.js

adv_inner.js

7 ms

adv.aspx

adv.aspx

508 ms

adv.aspx

adv.aspx

540 ms

dgcore.js

dgcore.js

4 ms

adSiteVisit.js

adSiteVisit.js

9 ms

SEO Factors

yahoo.sennenyusya.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 Yahoo.sennenyusya.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 Yahoo.sennenyusya.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

yahoo.sennenyusya.jp

Open Graph data is detected on the main page of Yahoo Sennenyusya. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: