Tools & Wizards About Us
pokkentournament.jp screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% 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

  • 100

    SEO

    Google-friendlier than
    94% of websites

pokkentournament.jp

「ポッ拳 POKKÉN TOURNAMENT」 アーケードゲーム公式サイト

Page Load Speed

4.4 sec in total

First Response

941 ms

Resources Loaded

3.3 sec

Page Rendered

126 ms

pokkentournament.jp screenshot

About Website

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

今度のバトルはアクションだ！対戦格闘アクションゲーム『ポッ拳』の公式サイト。

Visit pokkentournament.jp

Key Findings

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

pokkentournament.jp performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

49/100

10%

LCP (Largest Contentful Paint)

Value21.8 s

0/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value1,330 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.6 s

11/100

10%

Network Requests Diagram

pokkentournament.jp

941 ms

common.css

98 ms

main.css

94 ms

respond.css

96 ms

jquery.colorbox.css

112 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 56% of them (54 requests) were addressed to the original Pokkentournament.jp, 21% (20 requests) were made to Platform.twitter.com and 9% (9 requests) were made to Bandainamco-am.co.jp. The less responsive or slowest element that took the longest time to load (941 ms) belongs to the original domain Pokkentournament.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.0 kB (5%)

Content Size

2.3 MB

After Optimization

2.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pokkentournament.jp main page is 2.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. 70% 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 22.0 kB

  • Original 29.6 kB
  • After minification 28.7 kB
  • After compression 7.6 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 22.0 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 46.9 kB

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

JavaScript Optimization

-42%

Potential reduce by 44.9 kB

  • Original 106.5 kB
  • After minification 106.5 kB
  • After compression 61.6 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 44.9 kB or 42% of the original size.

CSS Optimization

-31%

Potential reduce by 8.2 kB

  • Original 26.7 kB
  • After minification 25.7 kB
  • After compression 18.5 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. Pokkentournament.jp needs all CSS files to be minified and compressed as it can save up to 8.2 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (38%)

Requests Now

89

After Optimization

55

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pokkentournament.jp

pokkentournament.jp

941 ms

common.css

common.css

98 ms

main.css

main.css

94 ms

respond.css

respond.css

96 ms

jquery.colorbox.css

jquery.colorbox.css

112 ms

font-awesome.min.css

font-awesome.min.css

116 ms

jquery.min.js

jquery.min.js

163 ms

LoadManager.js

LoadManager.js

186 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

219 ms

jquery.top.js

jquery.top.js

203 ms

widgets.js

widgets.js

11 ms

commonFooter.js

commonFooter.js

297 ms

conversion.js

conversion.js

81 ms

s_retargeting.js

s_retargeting.js

509 ms

js

js

59 ms

bg_wrap.png

bg_wrap.png

89 ms

bg_wrap-inner.png

bg_wrap-inner.png

131 ms

logo_title.png

logo_title.png

123 ms

gmenu_0_off.png

gmenu_0_off.png

120 ms

menu_emblm.png

menu_emblm.png

61 ms

gmenu_1_off.png

gmenu_1_off.png

98 ms

gmenu_2_off.png

gmenu_2_off.png

188 ms

gmenu_3_off.png

gmenu_3_off.png

131 ms

gmenu_4_off.png

gmenu_4_off.png

251 ms

gmenu_5_off.png

gmenu_5_off.png

234 ms

gmenu_6_off.png

gmenu_6_off.png

221 ms

gmenu_7_off.png

gmenu_7_off.png

218 ms

gmenu_8_off.png

gmenu_8_off.png

257 ms

title_promotion_off.png

title_promotion_off.png

237 ms

loading_background.png

loading_background.png

316 ms

loading.gif

loading.gif

329 ms

main-imgl.jpg

main-imgl.jpg

525 ms

main-img.jpg

main-img.jpg

642 ms

btn_service_off.png

btn_service_off.png

408 ms

main-img.png

main-img.png

356 ms

bn_001.png

bn_001.png

469 ms

bn_002.png

bn_002.png

503 ms

bg_topics.png

bg_topics.png

446 ms

title_topics.png

title_topics.png

505 ms

pastinfo.png

pastinfo.png

574 ms

title_twitter.png

title_twitter.png

551 ms

copy.png

copy.png

631 ms

bg_btn-pagetop.png

bg_btn-pagetop.png

661 ms

all.js

all.js

32 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

680 ms

all.js

all.js

5 ms

53 ms

commonFooter.js

commonFooter.js

345 ms

s_retargeting.js

s_retargeting.js

720 ms

commonFooter.js

commonFooter.js

582 ms

commonFooter.css

commonFooter.css

142 ms

tracklist.js

tracklist.js

282 ms

logo_am_sp.png

logo_am_sp.png

283 ms

commonFooter.css

commonFooter.css

146 ms

tracklist.js

tracklist.js

149 ms

logo_am_sp.png

logo_am_sp.png

291 ms

logo_am_pc.png

logo_am_pc.png

449 ms

49 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

33 ms

settings

settings

97 ms

bg_pageheader-main.jpg

bg_pageheader-main.jpg

173 ms

title_promotion_on.png

title_promotion_on.png

382 ms

35 ms

gmenu_0_on.png

gmenu_0_on.png

117 ms

gmenu_1_on.png

gmenu_1_on.png

152 ms

gmenu_2_on.png

gmenu_2_on.png

99 ms

gmenu_3_on.png

gmenu_3_on.png

120 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

3 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

6 ms

pokken_official

pokken_official

82 ms

embeds

embeds

114 ms

embeds

embeds

115 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

tweet_button.2f70fb173b9000da126c79afe2098f02.ja.html

31 ms

gmenu_4n_off.png

gmenu_4n_off.png

132 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

11 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

5 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

28 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

42 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

57 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

60 ms

_buildManifest.js

_buildManifest.js

70 ms

_ssgManifest.js

_ssgManifest.js

69 ms

gmenu_4_on.png

gmenu_4_on.png

159 ms

gmenu_5n_off.png

gmenu_5n_off.png

150 ms

gmenu_5_on.png

gmenu_5_on.png

150 ms

gmenu_6_on.png

gmenu_6_on.png

109 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

10 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

10 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

3 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

14 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

6 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

13 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

5 ms

gmenu_7_on.png

gmenu_7_on.png

342 ms

gmenu_8_on.png

gmenu_8_on.png

91 ms

main-catch.png

main-catch.png

191 ms

instorenow.png

instorenow.png

174 ms

Accessibility Review

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pokkentournament.jp best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

pokkentournament.jp SEO score

100

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pokkentournament.jp can be misinterpreted by Google and other search engines. Our service has detected that English 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 Pokkentournament.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

pokkentournament.jp

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