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

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gdf.hangame.co.jp

ガンダムジオラマフロント - ハンゲーム

Page Load Speed

7.3 sec in total

First Response

886 ms

Resources Loaded

6 sec

Page Rendered

458 ms

gdf.hangame.co.jp screenshot

About Website

Click here to check amazing Gdf Hangame content for Japan. Otherwise, check out these important facts you probably never knew about gdf.hangame.co.jp

基本無料オンラインゲーム『ガンダムジオラマフロント(ガンジオ)』“こだわり”の配置で最強のガンダム基地を作れ！1日10分から遊べるジオラマシミュレーショバトル！

Visit gdf.hangame.co.jp

Key Findings

We analyzed Gdf.hangame.co.jp page load time and found that the first response time was 886 ms and then it took 6.4 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

gdf.hangame.co.jp performance score

0

Network Requests Diagram

gdf.hangame.co.jp

886 ms

mod_header.css

648 ms

mod_userarea.css

675 ms

common.css

530 ms

mod_footer.css

538 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Gdf.hangame.co.jp, 39% (37 requests) were made to Images.hangame.co.jp and 36% (34 requests) were made to Bridge.gdf.bandainamco-ol.jp. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Images.hangame.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 590.5 kB (24%)

Content Size

2.5 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gdf.hangame.co.jp main page is 2.5 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. 45% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 31.3 kB

  • Original 42.0 kB
  • After minification 40.3 kB
  • After compression 10.7 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 31.3 kB or 75% of the original size.

Image Optimization

-3%

Potential reduce by 49.6 kB

  • Original 1.8 MB
  • After minification 1.7 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. Gdf Hangame images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 398.2 kB

  • Original 517.8 kB
  • After minification 416.5 kB
  • After compression 119.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 398.2 kB or 77% of the original size.

CSS Optimization

-85%

Potential reduce by 111.4 kB

  • Original 130.4 kB
  • After minification 104.0 kB
  • After compression 19.0 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. Gdf.hangame.co.jp needs all CSS files to be minified and compressed as it can save up to 111.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (44%)

Requests Now

94

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gdf.hangame.co.jp

gdf.hangame.co.jp

886 ms

mod_header.css

mod_header.css

648 ms

mod_userarea.css

mod_userarea.css

675 ms

common.css

common.css

530 ms

mod_footer.css

mod_footer.css

538 ms

mod_srvclstsarea.css

mod_srvclstsarea.css

549 ms

coreCommon.js

coreCommon.js

573 ms

common.js

common.js

1202 ms

jindo2.1.3.2.js

jindo2.1.3.2.js

881 ms

core.js

core.js

1085 ms

avatarViewer.js

avatarViewer.js

1143 ms

jquery-1.4.2.js

jquery-1.4.2.js

1250 ms

core_noconflict.js

core_noconflict.js

833 ms

plugin.js

plugin.js

994 ms

mod_popup.css

mod_popup.css

1053 ms

spotDeckEL.js

spotDeckEL.js

1155 ms

header.v04.css

header.v04.css

1080 ms

plugin.1.1.js

plugin.1.1.js

1116 ms

gamecommon.js

gamecommon.js

1186 ms

loginform_ssl.js

loginform_ssl.js

1169 ms

scouter.js

scouter.js

170 ms

logo_hangame_w_152x32.png

logo_hangame_w_152x32.png

683 ms

logo.png

logo.png

1526 ms

catchcopy.png

catchcopy.png

684 ms

navi_new.jpg

navi_new.jpg

688 ms

navi_info.jpg

navi_info.jpg

693 ms

navi_playguide.jpg

navi_playguide.jpg

539 ms

navi_community.jpg

navi_community.jpg

720 ms

navi_shop.jpg

navi_shop.jpg

1018 ms

navi_support.jpg

navi_support.jpg

854 ms

btn_login.png

btn_login.png

858 ms

btn_memberentry.png

btn_memberentry.png

865 ms

blog.jpg

blog.jpg

901 ms

free.jpg

free.jpg

1022 ms

nojs_gamestart.gif

nojs_gamestart.gif

1198 ms

gamestart.jpg

gamestart.jpg

1553 ms

download.jpg

download.jpg

1082 ms

shop.jpg

shop.jpg

1354 ms

support.jpg

support.jpg

1191 ms

footer.v02.png

footer.v02.png

1443 ms

srvclstsarea_arrow_on.gif

srvclstsarea_arrow_on.gif

1360 ms

lpinfoproxy.nhn

lpinfoproxy.nhn

526 ms

sp_navbtn04.png

sp_navbtn04.png

1745 ms

sp_btn01.png

sp_btn01.png

1687 ms

bg_body.jpg

bg_body.jpg

1518 ms

bg_home.jpg

bg_home.jpg

3975 ms

navi_bg.jpg

navi_bg.jpg

1675 ms

bg_cont_btm.gif

bg_cont_btm.gif

1682 ms

bg_cont_mdl.gif

bg_cont_mdl.gif

1708 ms

bg_userpanel.gif

bg_userpanel.gif

1826 ms

bg_userpanel_unlogin.gif

bg_userpanel_unlogin.gif

1828 ms

top.php

top.php

553 ms

ico_key.gif

ico_key.gif

1831 ms

ico_search.gif

ico_search.gif

1862 ms

bg_community_line.gif

bg_community_line.gif

1880 ms

icon_more.gif

icon_more.gif

1992 ms

shop_bg.jpg

shop_bg.jpg

1981 ms

shop_ar.jpg

shop_ar.jpg

1987 ms

srvclstsarea_title.gif

srvclstsarea_title.gif

2014 ms

core.1.0.js

core.1.0.js

347 ms

srvclstsarea_li.gif

srvclstsarea_li.gif

1554 ms

mod_base.css

mod_base.css

168 ms

mod_information.css

mod_information.css

336 ms

jindo2.1.2.2.js

jindo2.1.2.2.js

717 ms

plugin.js

plugin.js

351 ms

jquery.dotdotdot.min.js

jquery.dotdotdot.min.js

357 ms

bg_rotationbnr.png

bg_rotationbnr.png

168 ms

20160315140517.jpg

20160315140517.jpg

697 ms

20160315123038.jpg

20160315123038.jpg

916 ms

20160315122748.jpg

20160315122748.jpg

531 ms

20160308142700.jpg

20160308142700.jpg

662 ms

20160216124111.jpg

20160216124111.jpg

850 ms

20151208141856.jpg

20151208141856.jpg

875 ms

20151109125943.jpg

20151109125943.jpg

1063 ms

20160106183241.jpg

20160106183241.jpg

994 ms

btn_01.png

btn_01.png

870 ms

btn_02.png

btn_02.png

1019 ms

btn_03.png

btn_03.png

1045 ms

btn_04.png

btn_04.png

1051 ms

btn_05.png

btn_05.png

1098 ms

btn_06.png

btn_06.png

1160 ms

btn_07.png

btn_07.png

1189 ms

btn_08.png

btn_08.png

1219 ms

tab_all.jpg

tab_all.jpg

1225 ms

icon_etc.png

icon_etc.png

1238 ms

icon_maintenance.png

icon_maintenance.png

1281 ms

icon_update.png

icon_update.png

1326 ms

icon_event.png

icon_event.png

1357 ms

icon_trouble.png

icon_trouble.png

1395 ms

tab_event.jpg

tab_event.jpg

1400 ms

tab_update.jpg

tab_update.jpg

1415 ms

tab_maintenance.jpg

tab_maintenance.jpg

1463 ms

icon_more.gif

icon_more.gif

1491 ms

tab_all_on.jpg

tab_all_on.jpg

1504 ms

btn_01_on.png

btn_01_on.png

1547 ms

SEO Factors

gdf.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 Gdf.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 Gdf.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

gdf.hangame.co.jp

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