Tools & Wizards About Us
paperman.hangame.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

paperman.hangame.co.jp

ただいまメンテナンス中です - ハンゲ

Page Load Speed

6.8 sec in total

First Response

856 ms

Resources Loaded

5.6 sec

Page Rendered

368 ms

paperman.hangame.co.jp screenshot

About Website

Welcome to paperman.hangame.co.jp homepage info - get ready to check Paperman Hangame best content for Japan right away, or after learning these important things about paperman.hangame.co.jp

オンラインゲームで遊ぶなら「ハンゲ」。MMORPG・FPS・ブラウザゲーム・無料ゲーム・初心者向けから最新ゲームアプリまで高品質なゲームが満載！人気ランキング・新作情報・ジャンル別検索・おすすめ・イベントなど最新情報も充実。

Visit paperman.hangame.co.jp

Key Findings

We analyzed Paperman.hangame.co.jp page load time and found that the first response time was 856 ms and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

paperman.hangame.co.jp performance score

0

Network Requests Diagram

paperman.hangame.co.jp

856 ms

def_import2.css

325 ms

mod_footer.css

350 ms

mod_userarea.css

508 ms

mod_srvclstsarea.css

349 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Paperman.hangame.co.jp, 48% (60 requests) were made to Images.hangame.co.jp and 26% (33 requests) were made to Static.hangame.co.jp. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Images.hangame.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 624.0 kB (23%)

Content Size

2.7 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Paperman.hangame.co.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. 50% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 33.3 kB

  • Original 44.6 kB
  • After minification 43.5 kB
  • After compression 11.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 33.3 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 86.6 kB

  • Original 2.0 MB
  • After minification 1.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. Paperman Hangame images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 419.8 kB

  • Original 573.2 kB
  • After minification 498.3 kB
  • After compression 153.4 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 419.8 kB or 73% of the original size.

CSS Optimization

-83%

Potential reduce by 84.3 kB

  • Original 101.2 kB
  • After minification 78.6 kB
  • After compression 16.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. Paperman.hangame.co.jp needs all CSS files to be minified and compressed as it can save up to 84.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 64 (53%)

Requests Now

121

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

paperman.hangame.co.jp

paperman.hangame.co.jp

856 ms

def_import2.css

def_import2.css

325 ms

mod_footer.css

mod_footer.css

350 ms

mod_userarea.css

mod_userarea.css

508 ms

mod_srvclstsarea.css

mod_srvclstsarea.css

349 ms

common.js

common.js

520 ms

jindo2.all.js

jindo2.all.js

377 ms

avatarViewer.js

avatarViewer.js

807 ms

loginform_ssl.js

loginform_ssl.js

514 ms

scouter.js

scouter.js

515 ms

plugin.js

plugin.js

566 ms

swfPutter.js

swfPutter.js

675 ms

coreCommon.js

coreCommon.js

680 ms

gamecommon.js

gamecommon.js

683 ms

header.v04.css

header.v04.css

541 ms

plugin.1.1.js

plugin.1.1.js

602 ms

c62f3744f4f86b304516a2aef2192bf5.js

c62f3744f4f86b304516a2aef2192bf5.js

684 ms

require_sjis.js

require_sjis.js

858 ms

mod_globalheader.css

mod_globalheader.css

528 ms

mod_spotdeck.css

mod_spotdeck.css

532 ms

mod_base.css

mod_base.css

543 ms

mod_subtemplate2.css

mod_subtemplate2.css

622 ms

mod_home.css

mod_home.css

645 ms

mod_playguide.css

mod_playguide.css

693 ms

mod_shop.css

mod_shop.css

699 ms

mod_support.css

mod_support.css

716 ms

mod_community.css

mod_community.css

809 ms

mod_etc.css

mod_etc.css

806 ms

onetag

onetag

492 ms

logo_hangame_b_152x32.png

logo_hangame_b_152x32.png

387 ms

logo_paperman.jpg

logo_paperman.jpg

713 ms

copy.jpg

copy.jpg

568 ms

gn_gameintro.jpg

gn_gameintro.jpg

402 ms

gn_playguide.jpg

gn_playguide.jpg

582 ms

gn_community.jpg

gn_community.jpg

420 ms

gn_shop.jpg

gn_shop.jpg

543 ms

gn_support.jpg

gn_support.jpg

569 ms

btn_login.png

btn_login.png

597 ms

btn_memberentry.png

btn_memberentry.png

700 ms

movie_title.gif

movie_title.gif

734 ms

charintro_title.gif

charintro_title.gif

736 ms

chara_01.jpg

chara_01.jpg

1102 ms

chara_02.jpg

chara_02.jpg

951 ms

chara_03.jpg

chara_03.jpg

1016 ms

chara_04.jpg

chara_04.jpg

1033 ms

chara_05.jpg

chara_05.jpg

900 ms

chara_06.jpg

chara_06.jpg

1068 ms

chara_07.jpg

chara_07.jpg

1066 ms

chara_08.v02.jpg

chara_08.v02.jpg

1300 ms

chara_09.jpg

chara_09.jpg

1370 ms

chara_10.jpg

chara_10.jpg

1517 ms

chara_11.jpg

chara_11.jpg

1399 ms

chara_12.jpg

chara_12.jpg

1400 ms

chara_13.jpg

chara_13.jpg

1609 ms

chara_14.jpg

chara_14.jpg

1652 ms

charintro_btn_prev.gif

charintro_btn_prev.gif

1527 ms

charintro_btn_next.gif

charintro_btn_next.gif

1566 ms

more.gif

more.gif

1567 ms

ss_title.gif

ss_title.gif

1677 ms

ss01.jpg

ss01.jpg

2477 ms

ss02.jpg

ss02.jpg

2233 ms

ss03.jpg

ss03.jpg

2237 ms

ss04.jpg

ss04.jpg

2467 ms

diary_title.gif

diary_title.gif

1827 ms

btn_diary2.gif

btn_diary2.gif

1836 ms

lpinfoproxy.nhn

lpinfoproxy.nhn

591 ms

top_notice.aspx

top_notice.aspx

694 ms

pixel.js

pixel.js

2250 ms

btn_gamestart_java.jpg

btn_gamestart_java.jpg

1628 ms

btn_gamestart.jpg

btn_gamestart.jpg

1607 ms

gamedownload.jpg

gamedownload.jpg

1750 ms

btn_specail.jpg

btn_specail.jpg

1648 ms

btn_ready.jpg

btn_ready.jpg

1764 ms

btn_faq.jpg

btn_faq.jpg

1798 ms

paperman_tushin.jpg

paperman_tushin.jpg

1829 ms

mod_base.css

mod_base.css

335 ms

mod_information.css

mod_information.css

339 ms

plugin.js

plugin.js

503 ms

action.jpg

action.jpg

1816 ms

jquery-1.4.2.js

jquery-1.4.2.js

646 ms

core.1.0.js

core.1.0.js

379 ms

logo_nhn_hg_bgw.png

logo_nhn_hg_bgw.png

1792 ms

srvclstsarea_arrow_on.gif

srvclstsarea_arrow_on.gif

1831 ms

sp_navbtn04.png

sp_navbtn04.png

1841 ms

sp_btn01.png

sp_btn01.png

1844 ms

bg_home.jpg

bg_home.jpg

2433 ms

bg_home_btm.gif

bg_home_btm.gif

1691 ms

bg_home_repert.gif

bg_home_repert.gif

1638 ms

bg_home_contents.gif

bg_home_contents.gif

1685 ms

bg_userpanel.gif

bg_userpanel.gif

1674 ms

bg_userpanel_unlogin.gif

bg_userpanel_unlogin.gif

1678 ms

title.gif

title.gif

173 ms

tab_hotnews.gif

tab_hotnews.gif

173 ms

icon_update.gif

icon_update.gif

172 ms

icon_osirase.gif

icon_osirase.gif

170 ms

tab_oshirase.gif

tab_oshirase.gif

320 ms

tab_ibent.gif

tab_ibent.gif

342 ms

icon_ibent.gif

icon_ibent.gif

343 ms

tab_update.gif

tab_update.gif

347 ms

more.gif

more.gif

340 ms

ico_key.gif

ico_key.gif

1682 ms

tab_hotnews_on.gif

tab_hotnews_on.gif

315 ms

ico_search.gif

ico_search.gif

1513 ms

icn_dot.gif

icn_dot.gif

1543 ms

btn_diary_bk.gif

btn_diary_bk.gif

1518 ms

pixel

pixel

153 ms

pixel

pixel

40 ms

Pug

Pug

36 ms

sync.ad-stir.com

sync.ad-stir.com

296 ms

sync

sync

8 ms

sync

sync

673 ms

is

is

736 ms

app.js

app.js

164 ms

srvclstsarea_title.gif

srvclstsarea_title.gif

163 ms

srvclstsarea_li.gif

srvclstsarea_li.gif

178 ms

pixel

pixel

25 ms

google

google

295 ms

sd

sd

88 ms

main.js

main.js

163 ms

mapuser

mapuser

149 ms

adfunnel

adfunnel

151 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

648 ms

setChainBannerMain.js

setChainBannerMain.js

190 ms

xrost

xrost

153 ms

jquery.float-element-1.0.js

jquery.float-element-1.0.js

191 ms

SEO Factors

paperman.hangame.co.jp SEO score

0

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    SHIFT_JIS

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

paperman.hangame.co.jp

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