Tools & Wizards About Us
commodity.co.jp screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

commodity.co.jp

楽天証券の商品先物取引

Page Load Speed

10.6 sec in total

First Response

552 ms

Resources Loaded

9.5 sec

Page Rendered

622 ms

commodity.co.jp screenshot

About Website

Click here to check amazing Commodity content for Japan. Otherwise, check out these important facts you probably never knew about commodity.co.jp

商品先物取引の「ドットコモディティ」は楽天証券の商品先物取引専用サイトです。金、原油、穀物のコモディティ取引、金・プラチナ地金の現物取引がオンラインで取引できます。マーケット情報、セミナー情報なども紹介しています。

Visit commodity.co.jp

Key Findings

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

Performance Metrics

commodity.co.jp performance score

0

Network Requests Diagram

commodity.co.jp

552 ms

www.commodity.co.jp

1182 ms

cmn-structure.css

634 ms

cmn-lang-ja.css

321 ms

import_dot_01.css

1439 ms

Our browser made a total of 119 requests to load all elements on the main page. We found that 71% of them (85 requests) were addressed to the original Commodity.co.jp, 5% (6 requests) were made to Rakuten-sec.co.jp and 3% (3 requests) were made to Jp.rakuten-static.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Commodity.co.jp.

Page Optimization Overview & Recommendations

Page size can be reduced by 733.1 kB (46%)

Content Size

1.6 MB

After Optimization

874.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Commodity.co.jp main page is 1.6 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. 35% of websites need less resources to load. Images take 682.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 43.4 kB

  • Original 56.2 kB
  • After minification 47.7 kB
  • After compression 12.8 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. This page needs HTML code to be minified as it can gain 8.5 kB, which is 15% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 43.4 kB or 77% of the original size.

Image Optimization

-6%

Potential reduce by 37.9 kB

  • Original 682.2 kB
  • After minification 644.2 kB

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. Commodity images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 395.7 kB

  • Original 580.5 kB
  • After minification 496.4 kB
  • After compression 184.8 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 395.7 kB or 68% of the original size.

CSS Optimization

-89%

Potential reduce by 256.1 kB

  • Original 289.0 kB
  • After minification 270.3 kB
  • After compression 32.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. Commodity.co.jp needs all CSS files to be minified and compressed as it can save up to 256.1 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (49%)

Requests Now

114

After Optimization

58

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

commodity.co.jp

commodity.co.jp

552 ms

www.commodity.co.jp

www.commodity.co.jp

1182 ms

cmn-structure.css

cmn-structure.css

634 ms

cmn-lang-ja.css

cmn-lang-ja.css

321 ms

import_dot_01.css

import_dot_01.css

1439 ms

slidebars.css

slidebars.css

487 ms

jquery-1.9.0.min.js

jquery-1.9.0.min.js

1089 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

864 ms

jquery.tile.js

jquery.tile.js

820 ms

base.js

base.js

821 ms

gaDownloadTracker.js

gaDownloadTracker.js

942 ms

newslist.css

newslist.css

1113 ms

home.css

home.css

1559 ms

jquery.main-visual.js

jquery.main-visual.js

1150 ms

newsbox.js

newsbox.js

1126 ms

fxrate.js

fxrate.js

1823 ms

slidebars.js

slidebars.js

1609 ms

parm_selector_footer.js

parm_selector_footer.js

237 ms

suggest_ext.js

suggest_ext.js

1267 ms

suggest_extra.js

suggest_extra.js

219 ms

s_code.js

s_code.js

2133 ms

125x125_rounded_blue_t

125x125_rounded_blue_t

957 ms

sp_menu.png

sp_menu.png

319 ms

logo.png

logo.png

491 ms

sp_login.png

sp_login.png

435 ms

bnr_qa.png

bnr_qa.png

540 ms

btn_account_03_02.png

btn_account_03_02.png

543 ms

btn_formula_03.png

btn_formula_03.png

800 ms

header_download_sp.png

header_download_sp.png

679 ms

header_android.png

header_android.png

858 ms

download_googleplay.png

download_googleplay.png

863 ms

header_iphone.png

header_iphone.png

869 ms

download_appstore.png

download_appstore.png

961 ms

btn_search.png

btn_search.png

985 ms

main-visual_img40.png

main-visual_img40.png

1314 ms

main-visual_img26.png

main-visual_img26.png

1343 ms

main-visual_img27.jpg

main-visual_img27.jpg

1829 ms

main-visual_img39.png

main-visual_img39.png

1644 ms

main-visual_thumb34.png

main-visual_thumb34.png

1292 ms

main-visual_thumb26.png

main-visual_thumb26.png

1344 ms

main-visual_thumb27.png

main-visual_thumb27.png

1597 ms

main-visual_thumb39.png

main-visual_thumb39.png

1603 ms

photo_emori_thumb.jpg

photo_emori_thumb.jpg

1639 ms

photo_yoshida_thumb.png

photo_yoshida_thumb.png

1664 ms

photo_ikemizu_thumb.png

photo_ikemizu_thumb.png

2081 ms

icon_movies_thumb.gif

icon_movies_thumb.gif

1954 ms

pickup_10.png

pickup_10.png

1962 ms

pickup_01.png

pickup_01.png

2129 ms

pickup_03.png

pickup_03.png

2311 ms

pickup_08.png

pickup_08.png

2484 ms

service_01.png

service_01.png

2260 ms

service_06.png

service_06.png

2287 ms

tool_01.png

tool_01.png

2403 ms

tool_02.png

tool_02.png

2483 ms

icon_iFormula.png

icon_iFormula.png

2622 ms

Get_Silverlight.png

Get_Silverlight.png

2827 ms

gtm.js

gtm.js

56 ms

bnr_gold.png

bnr_gold.png

2743 ms

jqueryg.min.js

jqueryg.min.js

904 ms

yahoo-min.js

yahoo-min.js

264 ms

dom-min.js

dom-min.js

923 ms

initJSONPSuggest_extra.js

initJSONPSuggest_extra.js

577 ms

view.js

view.js

570 ms

analytics.js

analytics.js

22 ms

conversion_async.js

conversion_async.js

59 ms

dc.js

dc.js

47 ms

bnr_oil.png

bnr_oil.png

2823 ms

collect

collect

92 ms

108 ms

__utm.gif

__utm.gif

21 ms

side_banner2.gif

side_banner2.gif

2380 ms

40 ms

qr_googleplay_jp.gif

qr_googleplay_jp.gif

2329 ms

qr_itunes_jp.gif

qr_itunes_jp.gif

2419 ms

btn_peagetop_02.png

btn_peagetop_02.png

2586 ms

icon-mb.png

icon-mb.png

2495 ms

h_bg01.png

h_bg01.png

2452 ms

bg_header.png

bg_header.png

2376 ms

icon-win_01.png

icon-win_01.png

2407 ms

icon-win_02.png

icon-win_02.png

2572 ms

bg_hx_05.png

bg_hx_05.png

2583 ms

icon_01.gif

icon_01.gif

2494 ms

icon05.gif

icon05.gif

2462 ms

tag.js

tag.js

76 ms

id

id

41 ms

tag

tag

7 ms

id

id

11 ms

index.php

index.php

2824 ms

FuturesMarketFile.json

FuturesMarketFile.json

2218 ms

s9845971829257

s9845971829257

10 ms

event

event

27 ms

SpotMarketPrice.json

SpotMarketPrice.json

2421 ms

fxRateFile.json

fxRateFile.json

2454 ms

icon14.png

icon14.png

2185 ms

icon_market.png

icon_market.png

2236 ms

icon01.gif

icon01.gif

2227 ms

icon11.png

icon11.png

2435 ms

icon13.png

icon13.png

2437 ms

bg_hx_04.png

bg_hx_04.png

2291 ms

line02.png

line02.png

2211 ms

bg_market.png

bg_market.png

2211 ms

icon12.png

icon12.png

2319 ms

icon_03.gif

icon_03.gif

2289 ms

main-visual_thumb34_on.png

main-visual_thumb34_on.png

2182 ms

newslist_bg01.png

newslist_bg01.png

332 ms

newslist_icon.png

newslist_icon.png

335 ms

newslist_bg02.png

newslist_bg02.png

402 ms

newslist_bg03.png

newslist_bg03.png

629 ms

footer_prm_list.jsonp

footer_prm_list.jsonp

395 ms

footer_prm_list.jsonp

footer_prm_list.jsonp

335 ms

dest4.html

dest4.html

31 ms

303 ms

ya.js

ya.js

355 ms

pixel

pixel

49 ms

ibs:dpid=771&dpuuid=CAESEIhoxScZp3__aq03MSPVNP0&google_cver=1

ibs:dpid=771&dpuuid=CAESEIhoxScZp3__aq03MSPVNP0&google_cver=1

37 ms

3176

3176

152 ms

pb.js

pb.js

1064 ms

360 ms

img

img

635 ms

SEO Factors

commodity.co.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 Commodity.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 Commodity.co.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

commodity.co.jp

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