Tools & Wizards About Us
cannon-king.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

cannon-king.jp

キャノンキング 公式サイト

Page Load Speed

7.4 sec in total

First Response

660 ms

Resources Loaded

6 sec

Page Rendered

671 ms

cannon-king.jp screenshot

About Website

Click here to check amazing Cannon King content. Otherwise, check out these important facts you probably never knew about cannon-king.jp

単純爽快クラッシュバトルゲーム『キャノンキング』配信スタート！早速新感覚のディフェンス＆シューティングゲームを体験しよう！！

Visit cannon-king.jp

Key Findings

We analyzed Cannon-king.jp page load time and found that the first response time was 660 ms and then it took 6.7 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

cannon-king.jp performance score

0

Network Requests Diagram

cannon-king.jp

660 ms

analytics.js

9 ms

normalize.css

355 ms

common.css

357 ms

index.css

550 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 40% of them (34 requests) were addressed to the original Cannon-king.jp, 22% (19 requests) were made to Pbs.twimg.com and 9% (8 requests) were made to O.twimg.com. The less responsive or slowest element that took the longest time to load (4.2 sec) belongs to the original domain Cannon-king.jp.

Page Optimization Overview & Recommendations

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

Content Size

9.9 MB

After Optimization

9.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Cannon-king.jp main page is 9.9 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 9.2 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 10.0 kB

  • Original 14.4 kB
  • After minification 13.3 kB
  • After compression 4.4 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 10.0 kB or 69% of the original size.

Image Optimization

-3%

Potential reduce by 304.6 kB

  • Original 9.2 MB
  • After minification 8.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. Cannon King images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 212.6 kB

  • Original 343.6 kB
  • After minification 334.9 kB
  • After compression 131.0 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 212.6 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 244.4 kB

  • Original 293.3 kB
  • After minification 283.3 kB
  • After compression 48.8 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. Cannon-king.jp needs all CSS files to be minified and compressed as it can save up to 244.4 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (24%)

Requests Now

82

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cannon King. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

cannon-king.jp

cannon-king.jp

660 ms

analytics.js

analytics.js

9 ms

normalize.css

normalize.css

355 ms

common.css

common.css

357 ms

index.css

index.css

550 ms

detectmobile.js

detectmobile.js

389 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

1358 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

585 ms

jquery.plusanchor.js

jquery.plusanchor.js

597 ms

collect

collect

41 ms

collect

collect

71 ms

index.js

index.js

486 ms

logo.png

logo.png

215 ms

btn-line@2x.png

btn-line@2x.png

214 ms

top-main.jpg

top-main.jpg

1336 ms

specON.png

specON.png

1004 ms

btn-spec-androidON.png

btn-spec-androidON.png

366 ms

btn-spec-iosON.png

btn-spec-iosON.png

223 ms

navi-01-off.png

navi-01-off.png

383 ms

navi-01-on.png

navi-01-on.png

414 ms

navi-02-off.png

navi-02-off.png

414 ms

navi-02-on.png

navi-02-on.png

582 ms

navi-03-off.png

navi-03-off.png

583 ms

navi-03-on.png

navi-03-on.png

625 ms

navi-04-off.png

navi-04-off.png

621 ms

navi-04-on.png

navi-04-on.png

728 ms

notice-bg.png

notice-bg.png

732 ms

princess.png

princess.png

1406 ms

game-intro-bg.png

game-intro-bg.png

4157 ms

game-intro-01.png

game-intro-01.png

1988 ms

game-intro-02.png

game-intro-02.png

1757 ms

game-intro-03.png

game-intro-03.png

1685 ms

video-bg.png

video-bg.png

3275 ms

video-bg02.png

video-bg02.png

3665 ms

btn-tw.png

btn-tw.png

1860 ms

btn-fb.png

btn-fb.png

1926 ms

widgets.js

widgets.js

6 ms

C74uNfYHwo8

C74uNfYHwo8

78 ms

goYan5FJleY

goYan5FJleY

167 ms

footer.html

footer.html

2018 ms

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

timeline.d11f7a3b3287fb94220e8ee6d03cc772.js

28 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

43 ms

like.php

like.php

168 ms

syndication

syndication

135 ms

661432078462943232

661432078462943232

358 ms

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

12 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

30 ms

www-embed-player.js

www-embed-player.js

58 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

62 ms

ad_status.js

ad_status.js

119 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

35 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

37 ms

qeKvIRsJabD.js

qeKvIRsJabD.js

516 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

568 ms

proxy.jpg

proxy.jpg

141 ms

proxy.jpg

proxy.jpg

139 ms

proxy.jpg

proxy.jpg

139 ms

proxy.jpg

proxy.jpg

140 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

19 ms

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css

24 ms

4RIeRrDK_normal.jpg

4RIeRrDK_normal.jpg

199 ms

Em2O60Vj_normal.png

Em2O60Vj_normal.png

241 ms

Im-HQsTQ_normal.jpeg

Im-HQsTQ_normal.jpeg

311 ms

6f152aa775f825e10696fbeb5373b184_normal.png

6f152aa775f825e10696fbeb5373b184_normal.png

306 ms

YjN2cccL_normal.jpeg

YjN2cccL_normal.jpeg

315 ms

favicon_normal.jpg

favicon_normal.jpg

312 ms

CdqUjNWW8AAEg8m.jpg

CdqUjNWW8AAEg8m.jpg

372 ms

CdGRPb3WAAUyQcx.jpg

CdGRPb3WAAUyQcx.jpg

386 ms

CciOPBkW8AA8KbR.jpg

CciOPBkW8AA8KbR.jpg

398 ms

Cb-K_-4XIAAwzc_.jpg:small

Cb-K_-4XIAAwzc_.jpg:small

449 ms

CbaH3KeWcAAZ4In.jpg

CbaH3KeWcAAZ4In.jpg

470 ms

CbQMogtWwAA85QO.jpg

CbQMogtWwAA85QO.jpg

479 ms

Ca2EsMcWAAEQ2tR.jpg

Ca2EsMcWAAEQ2tR.jpg

802 ms

CavU6XDUMAAyckW.jpg

CavU6XDUMAAyckW.jpg

714 ms

CaW4NFYUcAAOK_W.jpg

CaW4NFYUcAAOK_W.jpg

572 ms

CaXA3RFUEAAfbkd.png

CaXA3RFUEAAfbkd.png

857 ms

CaXTYSjUkAAuC4m.jpg

CaXTYSjUkAAuC4m.jpg

724 ms

CaW6rm-UsAAhMbX.jpg

CaW6rm-UsAAhMbX.jpg

732 ms

CaSBmOvWkAEJdz8.jpg

CaSBmOvWkAEJdz8.jpg

827 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

29 ms

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

syndication_bundle_v1_64fcb3dd2f6da5b5f976d91a319ef73e329c1a5d.css

91 ms

proxy.jpg

proxy.jpg

37 ms

proxy.jpg

proxy.jpg

66 ms

proxy.jpg

proxy.jpg

62 ms

proxy.jpg

proxy.jpg

51 ms

jot.html

jot.html

2 ms

SEO Factors

cannon-king.jp SEO score

0

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 Cannon-king.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 Cannon-king.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

cannon-king.jp

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